context-review

You can synchronize architecture documentation by scanning the current codebase and updating the `.context/` directory to align architecture, domain decisions, and standards docs with the actual code state without modifying source files.

You need to update codebase context documentation at the start of an architect or design task, especially when the context cache is stale or missing for more than five days, or when targeting a full project or specific modules.

The best way to keep domain decisions and standards docs accurate is to run an automated context synchronization process that reads the codebase and updates `.context/` files, preserving hand-authored narratives while reflecting code changes.

Context synchronization does not modify source code during execution. It strictly reads the codebase to update documentation files like `overview.md`, `architecture.md`, and domain standards, then writes a cache record.

The context cache determines documentation freshness by reading `.context/cache/context_update.md` during pre-flight checks to verify if the existing context baseline is valid or if a resynchronization is required.

Yes, you can target a specific module for documentation synchronization. The process operates on either a full project or specific modules, updating the corresponding `.context/` files to match the targeted code areas.