Mission Report — Markdown + Knowledge Graph

Emits the third and final Voltron mission document: the outcome of every assignment, recorded against the same graph nodes the plan created.

Read the format reference first: ${CLAUDE_PLUGIN_ROOT}/kb/mission-knowledge-format.md. The report's value depends entirely on reusing the plan's identifiers — a report that mints fresh @ids records nothing, because nothing links back to what was promised.

What a report contains

Procedure

1. Load the plan's graph. Read mission-plan.jsonld and reuse every @id — mission, assignments, Lions, files. The report does not create assignments; it resolves them.
2. Transition each assignment's status using the KB's actionStatus vocabulary: Lion reported done → CompletedActionStatus; Lion reported blocked → FailedActionStatus plus an error string naming the blocker; never dispatched → left at PotentialActionStatus with a result explaining the deferral.
3. Record results honestly. result carries what the Lion actually produced. If a Lion reported done but its acceptance criterion was never checked, that is not CompletedActionStatus — mark it Active and say the verification is outstanding.
4. Check success criteria against evidence, not against assignment status. An assignment can complete while its criterion still fails. Cite the evidence — a command's output, a test result, a file that now exists — for each criterion marked met.
5. Set endDate on the mission node.
6. Write mission-report.md, then mission-report.jsonld. Validate per the KB checklist and report both paths.

Writing rules

• Report what happened, not what was supposed to happen. A mission where two of five assignments blocked is a useful record; a report that rounds it to "mission complete" is not, and the graph will contradict it.
• Every FailedActionStatus needs an error a reader can act on. "Failed" alone is noise.
• Do not quietly drop an assignment that was never dispatched. Deferred work stays in the graph with its reason, or the next mission rediscovers it as new.
• Keep the Markdown short. The detail lives in the graph; the Markdown is the summary someone reads in thirty seconds.

What the accumulated graph answers

Because Lion and file identifiers are global across missions (see the KB's identifier scheme), a directory of mission reports answers questions no single report can: which files block most often, which Lion's assignments most frequently need a second pass, which success criteria keep recurring unmet. Mention this to the user once they have more than one mission on disk — it is the reason the format exists.