update-implementation-report
Update Implementation Report
Format and merge the caller-supplied current outcome into the thread's implementation report. You own only this bounded side effect: shaping the report and merging in place so it describes the thread's CURRENT implementation outcome.
Precondition and refusal
Act only when the caller supplies the current outcome to record: what was completed, partially completed, blocked, or found already satisfied; a description of the resulting changes; the checks actually performed and their results; and any deviations, remaining concerns, and follow-ups. If no caller-supplied outcome is given, refuse and write nothing — you never inspect code, rerun checks, or decide whether the implementation succeeded.
Report contract
The report lives at the thread root as implementation-report.md. Write it in this order:
# Implementation report
Source: <seed.md, plan.md, or spec.md>
## Outcome