I2749 — A commit that only plans an issue is not its delivery

○READY wave 2 · p0 · implementation profile · parallel safe

Part of truthful-plan-surfaces — The plan's surfaces are inferred from delivery, and nothing they show is typed beside the repository.

Objective

plan.delivery stops counting as a merge of an issue a commit or pull request that names it while changing only the plan's own records and what is derived from them, so that plan.drift's merged_not_recorded holds only work that was delivered.

Why

I2748 read plan drift on the trunk (origin/master d1162668036, forge read) on 2026-10-16: of 16 merged_not_recorded findings, six name an issue only because a planning or record commit mentioned it. I1302 (012fed644a0, docs(plan): I1301 is done, and I1302 may not land its schema alone), I1305 (d52f433348b, a merge whose subject says I1305 was restored to its own milestone), I1900 (#1128, fix(plan): I1900 is ready again until the intent it serves has a critique), I1962 (42a5715eec2, fix(project): issue I1962 no longer scopes the deleted script), I1980 (1aaf9f86d58, chore(plan): an adopter's upgrade is a planned outcome, I1980-I1991) and I2484 (#1031, docs(ui): the UI is the accepted primary surface, and its plan says what landed). None of them delivers its issue, and no stamp can settle them honestly: a blocking gate would stay red on them for ever (ADR 0166, decision 2).

Current state

delivery.rs takes the newest commit or merge in the trunk's history whose subject, title or branch names the issue as its merge, whatever that commit changed.

Desired state

A commit or pull request whose changes lie only under .ai/repo/project/ and the projections derived from them (docs/PLAN_STATUS.md, docs/PAGES_STATUS.md, docs/generated, site/data/generated, site/data/registry, site/content) is planning, not delivery: it does not make an issue merged, and plan delivery says so in the proof it reports for a merge it passed over.

Scope

• apps/majordomus-cli/src/plan/delivery.rs
• apps/majordomus-cli/src/plan/drift.rs
• apps/majordomus-cli/tests/plan_delivery.rs
• test/cases/3100_an_issue_delivery_is_inferred.sh
• docs/PLANNING.md

Out of scope

• Writing a stamp from inference: a merge is not acceptance (ADR 0166, alternatives).
• Reading prose in commit bodies to decide what a commit meant.

Dependencies

• I2741✓DONE Merged work the plan has not recorded is drift, and on the trunk past a window it is red

What waits on this

• I2748✕BLOCKED The drift already on the trunk is settled before the gate is made blocking

Acceptance criteria

• A commit naming an issue that changes only its record and derived projections leaves the issue at the stage it had without that commit
• A commit naming an issue that changes any other path still makes it merged
• plan drift on the trunk no longer reports I1302, I1305, I1900, I1962, I1980 or I2484 as merged_not_recorded

Validation

• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test plan_delivery
• bash test/run.sh 3100_an_issue_delivery_is_inferred 3101_merged_work_unrecorded_is_drift
• bin/majordomus plan drift --json

Evidence required

• planning_commit_is_not_delivery

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