Task: Scaffold story: Stop ores.shell menus from silently shadowing each other
Table of Contents
This page documents a task in the Stop ores.shell menus from silently shadowing each other story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
(Describe what user-visible-or-internal change this task produces.)
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Stop ores.shell menus from silently shadowing each other |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-09-27 |
3. 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 |
|---|---|
| #2247 | [shell] Scaffold the shell menu collision story |
8. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
9. Result
The story is scaffolded and its two tasks are open. The defect it carries is recorded from the replay that found it: five shell menus are registered twice and the CLI resolves a duplicate by registration order, so where both sides define a verb the loser's implementation is dead. The dq half of the same class is fixed in the generator, which no longer renders a command unit for a staging shim whose plural another component models.