I3269 — Accepting several issues at once is previewed on the original graph, with shared unlocks counted once

plan.impact accepts a set; the result reports unique new unlocks, overlap and remaining blockers, labelled hypothetical.

BLOCKED wave 1 · p3 · implementation profile · parallel safe

Part of the-plan-says-what-a-fix-unblocks — The plan says what finishing an issue unblocks, and why each blocked issue is blocked.

Blocked. This issue cannot start until I3267 is done. The status is derived from that, not declared.

Objective

plan.impact accepts a set; the result reports unique new unlocks, overlap and remaining blockers, labelled hypothetical.

Why

Owner order 2026-10-17 (scenario mode). Proposed in ADR 0195 (What accepting an issue unblocks is answered by one counterfactual evaluator over the plan graph) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c284#5.

Current state

No evaluator exists.

Desired state

Set evaluation is the same function over a set.

Scope

apps/majordomus-cli/src/plan.rs

Dependencies

I3267READY One read-only evaluator says what accepting an issue would unblock, from plan.next's own readiness rules

Acceptance criteria

Two issues sharing a dependent count it once
Nothing is written

Validation

majordomus plan validate
majordomus intent validate

Evidence required

test_a_set_of_fixes_is_previewed

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