document-release

Automatically update project documentation after a ship by reading code diffs to cross-reference changes and apply consistent updates across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files.

The best way to sync README and ARCHITECTURE docs is to cross-reference the code diff against existing documentation and apply consistent updates to ensure all project files match what shipped.

Polish changelog wording by adjusting the text voice to improve readability without altering the historical record, ensuring release notes remain accurate and clear.

Yes, updating post-ship documentation requires read and write access to the repository because the workflow uses shell utilities to directly modify files like README and CLAUDE.md.

Yes, you can automatically bump the VERSION file when syncing documentation, as the workflow tidies TODOS and optionally increments the version when appropriate to reflect the shipped changes.