Handoff report

A report is what an attempt returns to the session that dispatched it. It is the other half of a handoff: the handoff carried what the receiving agent could not recover from the repository, and the report carries what the dispatching session cannot recover from this one.

That session has no transcript of this one, no tool output, no diff. It has the boundary it drew and the repository. Everything else, it learns here.

The work is over. Writing the report changes no code: read what landed, verify it, print the report.

1. Fix the verdict first

One of these, chosen before anything else is written, because a verdict picked last gets written to match the narrative:

• COMPLETE: everything the unit owned is delivered and verified.
• COMPLETE WITH DEVIATIONS: delivered, but something differs from what the handoff specified. Every deviation is named, with what forced it.
• PARTIAL: some requirements landed and others did not. The split is named requirement by requirement.
• BLOCKED: the work cannot proceed without a decision, a fact, or an access this session does not have. What would unblock it is named exactly.
• ABANDONED: work was started and undone. What was reverted, and what state the branch is left in, are both named.

A batch gets one report per item, each with its own verdict. The handoff granted several units together to pay for its preamble once; the reports stay separate so the board still shows each unit's outcome, and so a blocked item does not drag a delivered one into its verdict.