I3238 — A pull request runs the cases its change can affect, chosen from what each case declares it reads, and a change of unknown impact runs them all

✕BLOCKED wave 6 · p1 · deep-work profile · parallel safe

Part of a-change-is-judged-in-minutes — A change is derived in under a second and judged in minutes, and nothing that could have changed is skipped.

Objective

Extend the existing `# majordomus-covers:` header with the paths a case reads (or derive them from the commands it covers and the feature-to-module map), and make scripts/ci-plan select suite cases from the changed paths' closure. A case that declares nothing runs on every pull request. The full suite runs on the combined top, on release and on demand.

Why

c228#3 (2026-10-11) named impact selection the largest order-of-magnitude gain. The rescued ci-critical-path milestone (2026-10-08 measurement) found 0 of 409 cases declaring the paths they read. Gates are already selected by path class, cases are not. It extends milestone ci-critical-path. Proposed in ADR 0187 (Tests are selected by the impact of a change, derived from what each case declares it reads, and a change of unknown impact runs every case) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c130#3, chatgpt-majordomus:c195#2, chatgpt-majordomus:c228#3, chatgpt-majordomus:c017#3, chatgpt-majordomus:c017#12, chatgpt-majordomus:c037#10, chatgpt-majordomus:c087#1, chatgpt-majordomus:c089#1.

Current state

Measured on master 707a04c, 2026-10-18: 431 of 527 cases carry `# majordomus-covers:` and 282 of those say 'none' (grep over test/cases/*.sh). test/run.sh shards by suite-durations.tsv; scripts/ci-plan has no case selection. The pre-push hook already runs scripts/ci/run-plan --before-push, which calls scripts/ci-plan, prints each gate it leaves out and why, and times itself against MJ_PUSH_BOUND (default 180 s), but picks its cases by recorded duration, not by impact.

Desired state

plan.json lists the selected cases with the reason for each. A mutation that drops a dependency from a case's declaration is caught by a case.

Scope

• scripts/ci-plan
• test/run.sh
• test/lib.sh
• .ai/repo/ci/suite.yaml
• .github/workflows/validate.yml
• scripts/ci/run-plan
• scripts/ci/verdict
• test/cases/1021_a_push_runs_what_ci_would_find_first.sh
• .ai/repo/project/intents

Out of scope

• Dropping the full suite from the proof of a combined top or a release

Dependencies

• I2350○READY One gate model names what a local check, a pull request, an integration and a release must run, and no second inventory exists
• I2348✕BLOCKED A gate's result is reused only for the exact inputs it judged, and a skipped gate carries the proof that nothing it reads changed
• I2527✕BLOCKED An incremental derive equals a full derive byte for byte, and an omitted dependency turns a gate red
• I3242✕BLOCKED The pull-request critical path has a committed GitHub baseline and a budget per required job, and a run's summary names its critical path and every cache state

Acceptance criteria

• A documentation-only change selects only the cases that read documentation
• A path no case declares selects every case
• A case whose declared input changed is never skipped (mutation case)
• The selection and its reasons appear in the run summary
• Every gate or case the plan does not run has a verdict row naming the unchanged digest of what it reads (I2348's gate_result_reuse_case passes in this issue's validation)
• I2527's omitted_edge_turns_the_gate_red passes, and removing one declared input from a case's declaration turns a gate red (mutation case)
• scripts/ci/run-plan --before-push uses the same case selection as CI for the same diff (case 1021)
• Case inputs are derived from the commands each case covers through the feature-to-module map; the cases left undeclared and their case-seconds are counted in the plan, and no hand declaration of every case is required
• Criterion no-required-check-is-dropped of intent a-change-is-judged-in-minutes becomes evidence: test with a ref to impact_selection_never_skips_an_affected_case, and the intent lists milestone ci-critical-path
• With this selection, a leaf edit's scripts/ci/run-plan --before-push completes within 60 s on the shared development machine, by the step's own time report (folded from I3243)

Validation

• bash test/run.sh 94_ci_plan 1021_a_push_runs_what_ci_would_find_first
• scripts/ci-plan --check

Evidence required

• impact_selection_never_skips_an_affected_case
• doc_only_pr_suite_time
• local_plan_equals_ci_plan_case

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