I3002 — A command to reproduce is a code block a reader can copy
Render each reproduce command as a code block with a keyboard-reachable copy control, in the snapshot too.
READY wave 0 · p1 · implementation profile · runs alone
Part of idd-reads-at-a-glance — The intent workspace reads at a glance and leads everywhere it names.
Ready. Every dependency is done, so majordomus plan start I3002 will be accepted.
Objective
Render each reproduce command as a code block with a keyboard-reachable copy control, in the snapshot too.
Why
On 2026-10-18 the owner read the published /ui/idd three times and found it unergonomic: commands are inline text that has to be selected by hand.
Current state
Inline commands.
Desired state
Copyable code blocks.
Scope
- apps/majordomus-cli/src/ui/idd.rs
- share/ui/ui.js
- .ai/repo/project
- docs
- site
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- Each reproduce command has a copy control that copies exactly the command
Validation
- majordomus plan validate
- cargo test --lib ui::idd::
- scripts/ui audit --only /ui/idd
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I3002.yaml. Read it back with majordomus plan show I3002.