document

To keep codebase documentation in sync after code changes, you update docs.md files across folders and modules to reflect recent architecture, usage, and implementation details, ensuring Noridocs stay accurate.

Automatic documentation update works by leveraging the nori-change-documenter subagent to refresh docs.md files. When available, it coordinates with code changes and architectural notes to apply updates without manual intervention.

Yes, you can manually update docs.md files if the nori-change-documenter subagent is unavailable. The dual workflow supports manual edits to refresh documentation sections and capture change context when automatic processing is not an option.

The best way to verify documentation updates across PRs and commits is to perform a post-change review. This process checks that docs.md sections accurately capture change rationale and maintain architectural coherence after updates are applied.

You need to update docs.md files for Noridocs after PRs, commits, and feature updates. This ensures documentation remains aligned with the current codebase by reflecting changes to architecture, usage, and implementation details.