Post-Release Follow-up

Purpose

After PR creation in the auto-dev release workflow, collect unaddressed findings and present actionable follow-up recommendations. The user chooses: execute now, register as issues, or skip.

Workflow

1. Collect Follow-up Candidates

Gather unfinished work from multiple sources:

Source A — Remaining open issues:

• Run: gh issue list --label verify-done --state open --json number,title,labels
• These are triaged issues NOT included in the current release

Source B — Deep-verify findings:

• Read the latest deep-verify output from .claude/outputs/sessions/{today}/