report-resultlisted

# Report result Your report is the only part of the work the primary sees. A claim without evidence cannot be accepted; a concern left out comes back as a review finding. A complete, honest report is what lets review start without a follow-up. This is the worker's wrapper over the shared `handoff-report` contract. Use that shape, and make the report your final output so the primary can collect it. ## When to use - The assigned work is finished and verified. - The task is blocked and cannot proceed. ## When not to use - Mid-task progress: the primary waits for the subagent to return; do not narrate. - Nothing has changed since the last report. ## Inputs - The confirmed criteria from `accept-assignment`. - The change: the diff and the files touched. - The evidence from `verify-change`, which applies `verify-evidence`. ## Procedure 1. **Verify first.** Never write the report before `verify-change`; the `Verified` section must come from real runs, not memory. 2. **Fill the `handoff-report` shape**, leaving nothing implied: - `Requested` — the goal and criteria as given. - `Implemented` — what was actually built, in scope terms. - `Changed` — the files, with additions and deletions. - `Verified` — claim + command + result, and what was not checked. Paste the raw output of a command you actually ran; never a constructed transcript. - `Issues found and fixed` — one line per finding. - `Remaining concerns` — anything unresolved, with severity; ke