docguard-sync

To keep API reference documentation in sync, run a preview dry-run to re-derive code-truth sections from the current repository, then apply the write phase to update the canonical docs safely.

Documentation drift occurs when code changes outpace manual updates. You identify affected human prose by running a sync preview that flags specific source=human sections no longer matching refreshed reality.

Yes, you can use git-diff context to limit documentation synchronization by passing the --since flag, restricting the re-derivation of code-truth sections to only recent codebase modifications.

Yes, you need the docguard-cli installed to execute the sync preview and write phases, which rely on the CLI to enforce section ownership markers and validate against documentation generation errors.

The best way to safely update stale architecture overviews is running a review-first dry-run mode that mechanically regenerates owned doc sections before applying the final write phase.

You should not use automated documentation synchronization for sections lacking ownership markers, as the guard validation requires these boundaries to prevent overwriting manual human prose blocks.