v0.4.1 — Streamlined release closeout

Release v0.4.1

Summary

Patch release that makes release closeout safer and easier to verify. Maintainers now have explicit guidance and tooling to publish GitHub Releases after a release PR merges, and release notes are checked for user-facing capability wording instead of issue-list bookkeeping.

What maintainers can do

• Follow a deterministic post-merge release checklist from planning through gh release create, gh release view, and gh release list verification.
• Validate that a tag and GitHub Release point at the expected merge commit.
• Check release notes for capability-oriented wording that explains value to adopting projects and maintainers.
• Capture release closeout evidence in PR manifests with target commit, title, notes source, and verification commands.

Upgrade guidance

Projects that adopted the framework should update with the assisted update flow:

node bin/cli.mjs update-prompt --target /path/to/your-project
node bin/cli.mjs doctor --target /path/to/your-project

Then run sync only after reviewing the generated update plan.

Compatibility

This is a backwards-compatible patch release. It adds documentation, template fields, a release closeout validator, and tests. Existing release planning commands remain preview-first.

Validation

• pnpm test
• pnpm test:workflow
• pnpm format:check
• node scripts/verify-hooks.mjs
• node scripts/validate-role-routing.mjs
• node scripts/validate-release-versioning.mjs
• node scripts/validate-release-closeout.mjs --tag v0.4.0 --target 8281f0d9e70bb25a7cd0cfd1abc87b2e5084aee6 --notes .agent-runs/scratch/github-release-v0.4.0.md

References

• #60 — release closeout workflow and user-facing release-note guidance.