Task: Bring ores.cli to the clean standard

Table of Contents

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

1. Goal

ores.cli passes the Component Clean Standard for a component of kind All.

2. Status

Field Value
State ABANDONED
Parent story Clean ores.cli to the component clean standard
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, and check_component_drift.py --all passes.

4. Plan

Work the Component Clean Standard in its section order, one entity at a time, and record each item's result in the table below.

  1. Baseline and inventory (B01 to B05). Record the baseline before any edit.
  2. Models (M01 to M10).
  3. Protocol (P01 to P06).
  4. Generation (G01 to G06).
  5. Wiring and data (W01 to W04).
  6. Shell (S01, S02).
  7. Structure and hygiene (H01 to H03).
  8. Verification (V01 to V06), ending with the registry entry.
Item Result Evidence
     

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
       

9. Result

Closed without running the checklist. A decommission review on 2026-09-23 found no capability that the shell or the service layer does not already provide, so cleaning the component would have spent effort on code that then gets deleted. The work moves to Decommission ores.cli.

What the review established:

  • ores.cli passes the automated half of the standard today (validate_docs.py reports all 42 components clean), so the clean pass had no validator failure to fix.
  • Its 125 test cases are 95% argument parsing. The six that touch the database are covered better elsewhere: currency_repository by 12 cases in ores.refdata/core/tests, and import_currency_config by 3 cases in ores.ore/core/tests.
  • The shell covers the same entity surface through the service layer, with 73 command units against the CLI's direct-repository calls.
  • Compute host registration, the one capability that looked unique, is not: work_handler::heartbeat auto-registers a host on its first heartbeat.
  • The only capability with no replacement is bulk file import and export straight to the database, and no automated path calls it.

Emacs 29.3 (Org mode 9.6.15)