update-codebase-map

Codebase documentation updates work by detecting diff-driven source changes, selectively editing affected map documents, and re-recording the final state with current hashes to keep everything synchronized.

Architecture docs stay in sync by applying targeted updates that detect what changed in dependency manifests and project conventions, then pruning or adding map documents to reflect the current repository structure accurately.

You need to refresh a codebase map when a feature branch changes modules, CLI commands, configuration, dependency manifests, entry points, or directory layout, making the existing project documentation potentially stale.

Updating a codebase map does not rewrite entire documentation; it applies precise diff-driven updates to edit only affected map documents, adding new docs for new project areas and pruning docs when areas disappear.

Synchronizing codebase map state involves rewriting the map state with current hashes, commit info, and document inventory after applying selective document edits to reflect the updated repository structure.