Story: Clean ores.shell to the component clean standard
Table of Contents
This page documents a story in Sprint 26. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
ores.shell meets the Component Clean Standard: the items marked All pass, each item that does not apply is recorded with its reason, and ores.shell joins COMPONENTS_UNDER_TEST. Order 35 of 35 in the sprint 26 component clean-up, tier 4 (client or test support).
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 26 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-09-23 |
3. Acceptance
- Every checklist item that applies to a component of kind All passes, with its evidence recorded on the task.
- Every item that does not apply is recorded as not applicable, with the reason.
- Every generator defect found is fixed at its source, with a regression test.
- ores.shell is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.shell to the clean standard | DONE | 2026-09-27 | 2026-09-27 | Work ores.shell through the Component Clean Standard in order and record each item. |
5. Notes
- Survey on 2026-09-23: 0 entity, junction or operation models; 353 C++ files outside tests, 182 of them generated (51%); 0 messaging headers, 0 of them hand-written.
- The host for every component's generated command units. Its own work is the hand-written remainder: retire every unit the components now generate (S01).
6. Decisions
7. Out of scope
8. Result
Merged as PR #2275, with every applicable item of the Component Clean Standard worked and recorded on the task. ores.shell joins COMPONENTS_UNDER_TEST and the drift check passes with it listed; the whole tree builds, the codegen suite passes and all fourteen of the component's suites pass with the fleet up.
The component is unusual in the programme in a way that shaped the whole pass. It is a component of kind All with no model of its own beyond the component model, and it is the render target of twelve other components' shell-command facets. So most of the Entity and Protocol sections do not apply, and the largest hand-written block in its tree is the shell surface of ores.trading entities, which belongs to that component's own S01.
The pass found more than it confirmed, which is what the standard predicts: two stale CMake lists, twelve stale part diagrams, six part overviews with no Diagram section, four parts with no rendered image, a namespace brief describing a shell that no longer exists, four tests asserting only a non-throw, and one red case asserting a timestamp form the platform does not write.
The task records what it did not close: the trading dependency, the two generator parser gaps, the CMake list check that no gate runs, and the V08 coverage list of 52 source files with no name-matched test.