I2904 — An intent whose criteria are met while its milestones hold open issues says so

When an intent's criteria are all met but its milestones still hold issues that are not DONE, every surface (/ui, /cockpit/intents, the snapshot) says \"criteria met; N issue(s) still open\", derived from plan.roadmap.

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 I2904 will be accepted.

Objective

Why

The published workspace showed the-owner-directs-work-from-the-ui as satisfied while its milestone idd-workspace still had an open pull request (f6's S17, 2026-10-18).

Current state

A verdict of satisfied says nothing about open work.

Desired state

The verdict is qualified by the open issues it does not cover.

Scope

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

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

An intent with met criteria and an open issue in its milestones reads \"criteria met; 1 issue(s) still open\" on /ui/idd and /cockpit/intents

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