itd-2609231434459890 says the pre-push hook runs make preflight; itd-2609091034175565 has the pre-push hook gate on a preflight receipt

itd-2609231434459890 says the pre-push hook runs make preflight; itd-2609091034175565 has the pre-push hook gate on a preflight receipt

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/shipped/itd-2609231434459890-abcd-s-own-test-lanes-check-the-machine.md:67 — "A check that runs once at the start of make preflight (so the pre-push hook"
• End B: .abcd/development/intents/shipped/itd-2609091034175565-nothing-tells-an-agent-that-a-record-it.md:85 — "passes an update to refs/heads/abcd-reserved/* without a preflight receipt"

itd-2609231434459890 relies on the pre-push hook inheriting the load check because the hook runs make preflight. itd-2609091034175565 describes .githooks/pre-push as checking for a preflight receipt, exempting empty-tree reservation chains from needing one. A hook that only checks for a receipt does not run the preflight, so it does not inherit the check.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1293.

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. The hook itself never runs the preflight (its header says so), but A only says the check lives in the preflight and is not duplicated in the hook, and the receipt ties every push to a preflight that ran it; at worst the word inherits is loose.