docs

To update documentation for verified work, you can use an automated approach that reads your progress file and feature plans to ensure only finished features are documented. This prevents planned or in-progress items from being published prematurely.

Mapping code changes to documentation relies on the module registry and scope globs. By consulting the module registry, the system determines the affected scope and automatically links your changed code to the corresponding docs that need updates.

Keeping documentation synced with released features requires applying progress gating to your update process. This ensures that navigation, cross-references, and module mappings are only adjusted to reflect features that are fully finished and verified.

Progress gating for documentation updates works by reading a designated progress file and feature plans to check completion status. It restricts the update process so that only code changes mapped to fully verified features trigger a documentation update.

Yes, you can automatically update navigation and cross-references in your docs. When mapping changed code to affected documentation, the system simultaneously updates navigation links and module mappings to accurately reflect the newly released features.

Documentation includes in-progress features when updates are not gated by project progress. To fix this, documentation updates should read the progress file and apply strict gating, ensuring that only completed, verified work is mapped and added to the docs.