Story: Clean ores.cli 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.cli meets the Component Clean Standard: the items marked All pass, each item that does not apply is recorded with its reason, and ores.cli joins COMPONENTS_UNDER_TEST. Order 34 of 35 in the sprint 26 component clean-up, tier 4 (client or test support).
2. Status
| Field | Value |
|---|---|
| State | ABANDONED |
| Parent sprint | Sprint 26 |
| Now | Closed unstarted. The component retires instead. |
| 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.cli is listed in
COMPONENTS_UNDER_TEST, andcheck_component_drift.py --allpasses.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Bring ores.cli to the clean standard | ABANDONED | Work ores.cli through the Component Clean Standard in order and record each item. |
5. Notes
- Survey on 2026-09-23: 0 entity, junction or operation models; 113 C++ files outside tests, 0 of them generated (0%); 0 messaging headers, 0 of them hand-written.
- A client: it follows the protocols of the components it calls (P05). Retire any command the shell now generates.
6. Decisions
- Retire the component instead of cleaning it. A review on 2026-09-23 found the standard's automated half already passes and the component has no capability the shell or the service layer does not provide. The Notes below already said to retire any command the shell generates; that covers the whole command surface. The work moves to Decommission ores.cli. Evidence: 95% of the component's 125 test cases are argument parsing; the shell carries 73 command units over the service layer against the CLI's direct-repository calls; compute host registration auto-registers from the wrapper heartbeat; the only unreplaced capability is bulk file import and export, which no automated path calls.