omk-docs-release

Release documentation is generated as a structured set covering summary, usage, configuration, test results, migration notes, and known limitations to explain changes and rationale for a new software version.

Creating a changelog and migration guide is handled by generating standardized developer handoff content that explains what changed, why it changed, and how to adopt it safely.

Documenting test results in release notes requires following quality rules that enforce concise technical writing and truthful reporting, including any test failures or skips within the test summary section.

Developer handoff documentation after a release should include a structured output of summary, usage instructions, configuration updates, migration notes, known limitations, and the test result summary.

Yes, updating a README for post-implementation changes is supported by producing release documentation that explains the applied changes, usage, and configuration for the latest software version.

Automated release documentation generation requires a structured output covering summary, usage, configuration, test results, migration notes, and known limitations, enforcing strict accuracy and test-reporting rules to reduce upgrade friction.