I3257 — intent explain follows each served issue past its merge to the release and the observed deployment that carry it

✕BLOCKED wave 2 · p2 · implementation profile · parallel safe

Part of command-and-deployment-criteria-are-judged — A command or deployment criterion is met by a recorded run of exactly that command, or an observation of exactly that deployment, current at the presented revision.

Objective

Revive I2507 from origin/chore/seven-owner-packs-are-tracked-and-planned (689021d6ce2, 2026-10-15, never landed): intent explain and the realization join continue from each served issue's merge to the release record and the deployment observation that carry it, with a gap named where one is missing.

Why

2026-10-02 and 2026-10-16: the chain from intent to runtime observation and from a commit to its criterion should be one query. Sources: chatgpt-majordomus:c176#2, chatgpt-majordomus:c270#4.

Current state

intent_realization.rs joins episodes, providers and handovers; delivery inference (I2740) is on its own branch.

Desired state

One explain answer carries intent -> criterion -> issue -> merge -> release -> deployment.

Scope

• apps/majordomus-cli/src/intent_realization.rs
• apps/majordomus-cli/src/intent.rs
• apps/majordomus-cli/tests/intent_realization.rs

Dependencies

• I3256✕BLOCKED A deployment criterion is met only by a recorded observation of that deployment serving a build that contains the criterion's newest change
• I2740✓DONE An issue's delivery is inferred from branches, pull requests, merges, tags and the published site

Acceptance criteria

• A served issue merged and released shows both; one merged and not released names the missing release

Validation

• majordomus plan validate
• majordomus intent validate

Evidence required

• test_explain_follows_work_to_its_deployment

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