Planning a patch release

The loop this supports: survey recent issues, agree a batch, record it as a tracking issue, work through it as normal PRs, then the human cuts the release. Your job is the first half. You do not tag, publish, or register anything.

Delegate the survey work. Reading and classifying issues is mechanical, so use productivity:weak-general-purpose subagents, several in parallel, one per slice of the issue list. Keep the judgement — what belongs in a patch — for yourself.