#1009 Sweep ticket and plan for missed decisions before saving

[williamthorsen]

What

Fixes a gap where tickets and plans could be saved without what the design conversation settled (rejected alternatives, agreed constraints and scope boundaries, edge cases, success criteria), leaving users to ask for a completeness pass by hand after the artifacts were already presented as done. Agents running design-and-plan or plan are now instructed to check both artifacts against the conversation before saving and to fold in whatever is missing, reporting the amendments without reopening approval. design-and-plan is also instructed to offer the remote-issue update after this check rather than before it, and only when the refined ticket differs from what the issue already carries.

Why

Tickets and plans are increasingly authored by one agent, or one harness, and handed to another — or to a developer who was never in the design conversation. Recipients kept receiving artifacts that had dropped decisions the conversation had settled, and the only thing catching it was a manual audit prompt after the fact, which found gaps most of the time and cost a round trip to repair. The remote issue could not be complete even in principle: it was written at ticket approval, before the plan phase existed, so any decision that settled while the plan was drafted had no path back to it.

Details

🐛 Bug fixes

• A shared partial, _partials/ticket-and-plan-completeness.md, defines the completeness sweep once and is inlined by design-and-plan (Phase 6) and plan (before saving), so the two cannot drift. It states the handoff test the artifacts must pass, what to sweep for, how to route each gap by kind, and that gaps are folded in and reported while a clean sweep proceeds silently.
• The sweep is specified to run at the last pre-save moment, after the revise-until-approved rounds, so decisions settled during plan revision are covered by the same pass as decisions settled during design. It runs in the main session and never a subagent, since only the session holds the conversation.
• design-and-plan's remote-issue update moved from the end of Phase 4 to Phase 6, after the sweep and the artifact save, so the issue is written once from final content. Phase 1's cross-reference was repointed to match.
• The offer now renders as its own labelled sub-block above the next-steps options under a shared Next steps: header, each sub-block numbered from 1. Previously it was told to join a menu of four mutually-exclusive options, where it could only improvise a fifth option or displace the menu's numbering — and a user answering with a number could not say both which next step they wanted and whether to touch the issue. The hard gate governing that menu now names the sub-block labels as sanctioned, so the gate and the rendering cannot be read as competing.
• The offer is made only when the refined ticket differs from the remote body. A good source ticket may be adopted unchanged and the sweep may find nothing to fold in, in which case the issue is already current and the ask would push an identical body.
• The sweep's no-new-approval-gate rationale is grounded in the decisions the conversation settled, rather than in an approval step that only design-and-plan performs. A reader of plan, which drafts and saves with no present-and-approve step, previously met a premise that is false there.

Closes #1009

[github-actions]

Dependency audit

Production dependency audit passed.