I2907 — The workspace's headline numbers are the chosen intent's

Replace the hero's global counts with the chosen intent's: criteria met of all, its milestones done of all, its issues by status, each derived from intents.explain and the issues the screen already filters; the global counts stay on /ui/roadmap.

DONE wave 5 · 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: \"Milestones 41\" counts the whole plan, not the intent on the screen.

Current state

The hero counts every intent and milestone in the repository.

Desired state

The hero counts what the chosen intent holds.

Scope

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

Dependencies

I2812DONE The IDD loop is accepted end to end in a real browser on one commit

Acceptance criteria

The hero's numbers change when another intent is chosen
No hero number counts outside the chosen intent

Validation

majordomus plan validate
cargo test --test ui_idd
bash test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh

Evidence required

headline_numbers_test

Evidence

covers	type	command	result	at commit
headline_numbers_test	ci	gh run view --job 117890228077 --log	ui::idd::tests::the_headline_numbers_are_the_chosen_intents ok, in rust (2) of validate run 39192952944 on dd4c0a87cba, the v0.30.2 top carrying a762f7456f6	eb72106

Timeline

started: 2026-10-19T10:01:16Z
verified: 2026-10-19T10:01:30Z
completed: 2026-10-19T10:01:38Z

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