COOL IDEA: generate post-release retrospective scaffolds

[flyingrobots]

Idea

Generate a post-release retrospective draft from the release profile and public release evidence.

Why this matters

The new process requires a retrospective immediately after release. The evidence is mostly machine-readable: tag, commit, release URL, workflow run, changelog entry, registry package versions, and diff since previous tag. A scaffold command would make the process faster and less likely to omit evidence.

Shape

A future command such as continuum release retro vX.Y.Z or a repo-local script could:

• read .continuum/release.yml;
• locate the previous public tag;
• collect diff stat, merged PRs, release run URL, and registry visibility;
• create or update the release retrospective issue with standard sections;
• list candidate fallout issues for human approval.

Done when

• A maintainer can generate a complete retrospective scaffold from a tag.
• Generated content is clearly marked as evidence scaffold, not final judgment.
• The command does not mutate GitHub Issues without explicit maintainer approval.