Task: Scaffold the remaining ores.reporting clean-up

Table of Contents

This page documents a task in the Clean ores.reporting to the component clean standard story. It captures the goal, current status, acceptance, and any notes or results.

1. Goal

Create the units that close the seven failing items and the three unrecorded defects, each with its goal, acceptance and branch, so the work is attributable and sequenceable.

2. Status

Field Value
State DONE
Parent story Clean ores.reporting to the component clean standard
Now Nothing.
Waiting on Nothing.
Next Nothing.
Last touched 2026-09-27

3. Acceptance

  • Every failing item and every unrecorded defect has a task with a goal and a testable acceptance.

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
#2263 [reporting] Scaffold the remaining clean-up as seven tasks

8. Review

Comment summary File Decision Notes
       

9. Result

Delivered. Seven tasks now carry the remaining work, each with a goal, a testable acceptance and its own branch:

  • Correct the ores.reporting entity models, for M04 and M08.
  • Validate the instance's definition key and type the schedule, two of the three defects no checklist item names.
  • Decide and act on the report input bundle model, the third.
  • Complete the reporting diagrams and write the audit record, for H01.
  • Repair the registrar composition and generate the risk_report_config surface, for P01 and S01.
  • Make reporting's shell commands answer, for V04's reporting-owned causes.
  • Fix the three shared codegen template defects, for G04.

The work itself is not done here: this task creates the units and nothing else. The one judgement worth recording is the split. The shell menu collision is not among them, because it already has its own story with five menus to fix, and the ten report_definitions commands that fail on it are that story's, not this component's.

Emacs 29.3 (Org mode 9.6.15)