Task: Make reporting's shell commands answer
Table of Contents
This page documents a task in the Complete the ores.reporting clean-up story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Close V04's reporting-owned causes: three generated recipes pass none where a required uuid belongs, and the eight execution-step handlers return in silence when the workflow headers are absent, so the caller learns only that time passed.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent story | Complete the ores.reporting clean-up |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Begin implementation. |
| Last touched | 2026-09-27 |
3. Acceptance
- No generated recipe requires the caller to supply a server-owned identifier.
- A step handler that cannot attribute a message answers with an error instead of returning in silence.
- The replay records every generated command as answering, or as unable to run with its reason.
4. Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
5. Notes
6. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
7. PRs
| PR | Title |
|---|---|
8. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|