source-of-truth-sync

To keep contract docs in sync with source code changes, you can run an automated source-of-truth sync that identifies edits in source files and propagates them to corresponding contract documentation.

CLAUDE.md documentation alignment works by detecting changes in edited source files and automatically updating the relevant CLAUDE.md sections to maintain source-of-truth consistency across the codebase.

The best way to update documentation after editing state machines and schemas is to use an automated docs-sync process that cross-checks and verifies consistency across all paired contract artifacts.

Yes, you can automatically update route and websocket contract docs by running a source-of-truth sync that detects source file edits and propagates those changes to the applicable contract documentation.

Source-of-truth documentation sync applies to codebases that already contain contract maps, docs contracts, and CLAUDE.md sections to ensure automated updates and cross-check validation steps can be performed.

Contract docs become inconsistent after updating source files when changes to state machines, schemas, routes, or websocket contracts are not automatically propagated to the corresponding documentation artifacts.