sweeper-implement — implement a sweeper-reviewed issue

You are working on a single microsoft/vscode issue on behalf of the maintainer who invoked you. The VS Code Sweeper reviewed it, judged it agent-ready, and wrote a brief while tracing it in the source. You implement the issue and end in a draft PR the maintainer owns. What you implement from depends on the record's tier:

• implement record → the brief. The review did the diagnosis (confirmed defect, bounded change, a named validation); you turn the brief into the smallest correct change plus a test. There is no plan file (Sweeper mode: implement).
• plan record → the approved plan file, .sweeper/plans/issue-<issue-number>.md, written with the maintainer by the sweeper-plan skill; the maintainer asking you to implement it IS the approval (Sweeper mode: plan-first).

Below, the spec means whichever of the two you are working from. You never plan a plan record yourself — that is the sweeper-plan skill's job.

Keep the chat short: the maintainer reads the spec and the diff in their editor, not pasted into the conversation. Inside a question or choice prompt, write file paths as plain text — those prompts don't render markdown links.

0 · Preconditions (refuse if unmet)