I2918 — The issue list filters by status

Let the issue list be filtered by status, the statuses read from the plan and the filter kept in the URL so the snapshot can carry it.

READY wave 0 · p2 · 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 I2918 will be accepted.

Objective

Let the issue list be filtered by status, the statuses read from the plan and the filter kept in the URL so the snapshot can carry it.

Why

On 2026-10-18 the owner read the published /ui/idd three times and found it unergonomic: a long intent offers no way to narrow its issues.

Current state

No filter.

Desired state

A status filter in the URL.

Scope

apps/majordomus-cli/src/ui/idd.rs
.ai/repo/project
docs
site

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

?status=READY shows only the intent's ready issues

Validation

majordomus plan validate
cargo test --test 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/I2918.yaml. Read it back with majordomus plan show I2918.