I3000 — The workspace's record texts are drawn as prose

Draw every record text on the workspace (statement, why, criteria, standing sentences, drift) through ui::prose, so code spans, strong words and links render and an id is linked only when the plan holds it; ui/idd.rs's own id linking goes.

DONE 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.

Objective

Why

On 2026-10-18 the owner read the published /ui/idd three times and found it unergonomic: texts show raw backticks and markdown; ui::prose already renders them and only milestone.rs uses it.

Current state

Raw text and a second id linker.

Desired state

One renderer for every record text.

Scope

apps/majordomus-cli/src/ui/idd.rs
apps/majordomus-cli/src/ui/prose.rs
test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh
.ai/repo/project
docs
site

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

A backticked path in a criterion renders as code
ui/idd.rs carries no id linker of its own

Validation

majordomus plan validate
cargo test --lib ui::
bash test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh

Evidence required

prose_screen_test

Evidence

covers	type	command	result	at commit
prose_screen_test	ci	gh run view --job 117890226384 --log	tests/ui_idd_evidence.rs: 2 passed, 0 failed (the standing route's texts drawn as prose), in rust (3) of validate run 39192952944 on dd4c0a87cba, carrying d092324165f	eb72106

Timeline

started: 2026-10-19T10:02:00Z
verified: 2026-10-19T10:02:13Z
completed: 2026-10-19T10:02:21Z

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/I3000.yaml. Read it back with majordomus plan show I3000.