23 lines
897 B
Markdown
23 lines
897 B
Markdown
# Generate Evidence-Based Release Notes
|
|
|
|
Create concise release notes from verified changes, migrations, fixes, known limitations and operator actions.
|
|
|
|
## Purpose
|
|
|
|
This is a publishable P0 built-in DevRunbook package. It is designed for the `guided` work mode with default autonomy `plan` and risk tier `low`.
|
|
|
|
## Required context
|
|
|
|
- Release range: Identify the commits, tags or previous release that define the change range.
|
|
- Audience: Choose the intended reader for the release notes.
|
|
|
|
## Completion
|
|
|
|
- Notes match actual changes and validation evidence.
|
|
- Operator actions and breaking changes are prominent.
|
|
- Validation evidence and unresolved limitations are reported honestly.
|
|
|
|
## Quality status
|
|
|
|
Editorially reviewed and covered by static structure and determinism fixtures. It is not represented as execution-validated or battle-tested until the platform stores corresponding evidence.
|