# Step 25 — Implementation Detail Built on 2026-10-08. 1. `_write_outputs` takes the Execution's final status and its Ledger. `end_with_warnings` now calls it, as `finalize` does. 2. `execution.json` gains `status` (`completed` or `completed_with_warnings`), `warnings`, `phases` (each Phase's status), and a `status` on every Deliverable: `submitted`, or `draft` when something it depends on was reopened after it was written. 3. With no Deliverable at all nothing is written, and the case's history records no files, as before. 4. The solution guide is written only when it exists; an Execution that stopped before packaging has none, and the manifest says so. Not covered: an Execution whose process is killed. It never reaches either end node, so it still writes nothing. The evaluation's progress file (iteration 6 step 11) records its time and tokens, not its Deliverables. Also on 2026-10-08, outside any step: the CI workflow installs `requirements.txt` and `requirements-dev.txt` before linting and testing. It installed only ruff, mypy and pytest, so its test step could not import the application. Tests: `tests/execution/test_engine.py`, two updated.