fix: preflight runs on CI's toolchain, and the audit and intent-lock chain

.abcd/config/reading-presets.json

@@ -60,10 +60,10 @@
         "test"
       ],
       "window": {
-        "tokens_est": 1300000,
-        "measured_tokens_est": 1280867,
-        "measured_bytes": 4931339,
-        "measured_at": "35483ff77ca726d81633625eaa816cae14b38d73"
+        "tokens_est": 1340000,
+        "measured_tokens_est": 1322032,
+        "measured_bytes": 5089824,
+        "measured_at": "b727b969a992532a9e67adb23734914a4f331513"
       }
     },
     "entailment": {
@@ -133,9 +133,9 @@
       ],
       "window": {
         "tokens_est": 390000,
-        "measured_tokens_est": 382072,
-        "measured_bytes": 1470980,
-        "measured_at": "35483ff77ca726d81633625eaa816cae14b38d73"
+        "measured_tokens_est": 382812,
+        "measured_bytes": 1473830,
+        "measured_at": "b727b969a992532a9e67adb23734914a4f331513"
       }
     },
     "comparative": {
@@ -216,10 +216,10 @@
         "test"
       ],
       "window": {
-        "tokens_est": 1310000,
-        "measured_tokens_est": 1289903,
-        "measured_bytes": 4966127,
-        "measured_at": "35483ff77ca726d81633625eaa816cae14b38d73"
+        "tokens_est": 1350000,
+        "measured_tokens_est": 1331068,
+        "measured_bytes": 5124612,
+        "measured_at": "b727b969a992532a9e67adb23734914a4f331513"
       }
     }
   }

.abcd/development/brief/04-surfaces/03-embark.md

@@ -71,6 +71,13 @@ non-directory parent. On any such conflict the core **writes nothing**: it
 returns the conflict set it found, and the surface renders it. A refusal that
 writes a file would be a transport-agnostic-core violation.
 
+The write runs under the target's issue-ledger lock (when it writes an issue)
+and then its intent store's lock, the order every writer holding both takes,
+and every planned write is judged again under them. A record created at a
+planned target between the plan and the write — a capture, an intent minted in
+the target meanwhile — is a conflict like any other, so it refuses the whole
+write rather than being replaced.
+
 ## 3. Scaffold steps
 
 Embark is a deterministic Go run: it reads the lifeboat, plans, refuses on any

.abcd/development/brief/04-surfaces/23-reading.md

@@ -239,6 +239,18 @@ before that point and leave no refusal record at all. That is deliberate: a refu
 record is a record about a run, and a payload that has not yet shown which run it
 belongs to has nothing to be recorded against.
 
+One refusal after that point is deliberately unrecorded. An item whose pattern or
+body field cites a record id that names no record — wherever the repository's
+record-lint gates prose citations in the reading-record store, which reads every
+record the ingest would write — refuses the whole run, naming the item, the field
+and the id, before the orphan sweep and before anything is staged. It is the gate
+the verdict ingest asks, reached through the same registration. Recording it would
+give the run an outcome, and the same run re-worded would then be refused as a
+rerun; left parked, it is ingested again once its prose describes the record
+rather than citing an id that does not exist. Like every recorded refusal, it
+rolls back what an earlier, interrupted attempt at the same run left in the
+ledger, so a refused run leaves no reading records.
+
 Writes are staged. Nothing durable is written or deleted until the whole payload
 validates; the reading records land as one batch; and the run metadata is written
 **last**, as the commit marker, so a run without one never happened. An interrupted

.abcd/development/intents/shipped/itd-100-alice-reads-one-page-and-knows-exactly-where-abcd-stands-in.md

@@ -92,4 +92,4 @@ Gap audit:
 - missing:
   - spc-15's conditional promise that deferring the structural docs-lint rule ("every table row carries at least one footnote") would be "recorded, not silent" — no such rule ships in the diff and no implement-time deferral record appears in the delivered DECISIONS.md line or ledger captures
     evidence: .abcd/development/specs/closed/spc-15-alice-reads-one-page-and-knows-exactly-where-abcd-stands-in.md:46 — "If deferred, that is recorded, not silent"
-    evidence: .abcd/work/DECISIONS.md (delivered grill line, 2026-07-26) — "no mention of the structural lint-rule deferral"
+    evidence: .abcd/work/DECISIONS.md (delivered grill line, 2026-07-26) — "no mention of the structural lint-rule deferral"

.abcd/development/intents/shipped/itd-101-every-citation-abcd-publishes-is-provably-alive-and-honestly.md

@@ -109,4 +109,4 @@ Gap audit:
 - missing:
   - the generated, disposable checklist page that hands back a receipt file
     evidence: .abcd/development/specs/closed/spc-17-every-citation-abcd-publishes-is-provably-alive-and-honestly.md:105 — "The generated checklist page itself may land as the later rung"
-    evidence: internal/surface/cli/cite.go:165 — "the format the generated checklist page emits"
+    evidence: internal/surface/cli/cite.go:165 — "the format the generated checklist page emits"

.abcd/development/intents/shipped/itd-102-your-repo-says-the-same-thing-about-itself-everywhere-becaus.md

@@ -86,4 +86,4 @@ Gap audit:
 - diverged:
   - Onboarding is described as an install-or-prepare interview, but abcd currently onboards only via the prepare-this-repo bridge (host asks the questions); there is no separate install-time interview beyond the CLI `identity init` it drives — a narrower-than-worded but functionally complete path
     evidence: internal/core/positioning/init.go:35 — "InitRequest is the onboarding interview's outcome. The host asks the questions (the prepare surface carries the wording); this is what it hands over."
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-103-abcd-teaches-repo-agents-the-shell-commands-they-must-never.md

@@ -90,4 +90,4 @@ Gap audit:
 - missing:
   - Press-release 'two planes': the teaching plane — the rules loader injecting the matched safety rules before shell-heavy work — is not wired in this delivery; only the execution-time guard plane ships (a guard/safety rules domain does not exist in internal/core/rules/)
     evidence: .abcd/development/intents/shipped/itd-103-abcd-teaches-repo-agents-the-shell-commands-they-must-never.md:13 — "The rules loader injects the matched safety rules before shell-heavy work"
-    evidence: internal/core/rules/rules.go:401 — "no guard/safety/hazard domain is registered — the only `guard` here is the stemming short-token guard"
+    evidence: internal/core/rules/rules.go:401 — "no guard/safety/hazard domain is registered — the only `guard` here is the stemming short-token guard"

.abcd/development/intents/shipped/itd-104-abcd-gates-a-new-idea-before-it-becomes-a-record-entry-resea.md

@@ -86,4 +86,4 @@ Gap audit:
   - The adversarial leg's fresh-context/off-policy/unknown-authorship conduct is codified in the orchestrating prompt but not enforceable by the binary at ingest — the recorded artefact cannot prove the evaluator was a fresh, off-policy session
     evidence: internal/core/ideate/record.go:367 — "the binary cannot observe how an agent was run, and pretending to check it would be theatre"
     evidence: commands/abcd/ideate.md:66 — "The evaluator must not be the session that ran legs 1 and 2. Dispatch it as a separate agent with its own context."
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-114-abcd-mints-collision-proof-record-ids-across-parallel-agents.md

@@ -283,4 +283,4 @@ Gap audit:
 - missing:
   - In-Scope bullet 3: the optional forge-backed allocator — and with it the offline-under-forge loud-fallback behaviour ruled at the interview — is not in the delivery; spc-33 defers it by ruling to a later adapter behind the same seam, so the press release's forge-registry promise remains owed
     evidence: .abcd/development/specs/closed/spc-33-abcd-mints-collision-proof-record-ids-across-parallel-agents.md:18 — "adapter behind the same seam and is **out of this spec's delivery**"
-    evidence: .abcd/development/decisions/adrs/0045-record-ids-are-timestamp-numeric-and-capture-stable.md:43 — "4. **The optional forge allocator allocates and never stores**"
+    evidence: .abcd/development/decisions/adrs/0045-record-ids-are-timestamp-numeric-and-capture-stable.md:43 — "4. **The optional forge allocator allocates and never stores**"

.abcd/development/intents/shipped/itd-130-abcd-update-completes-a-chosen-update-in-one-verb-it-fetches.md

@@ -376,4 +376,4 @@ Gap audit:
     evidence: $GOMODCACHE/github.com/minio/selfupdate@v0.6.0/apply.go:78 — "_, err = io.Copy(fp, bytes.NewReader(newBytes))"
   - The CA-canary assertion spc-32 promised ('asserted via a canary file whose read would be observable') — the tests assert the env is unset, not that a planted CA file is never read
     evidence: .abcd/development/specs/closed/spc-32-abcd-update-completes-a-chosen-update-in-one-verb-it-fetches.md:78 — "asserted via a canary file whose read would be observable"
-    evidence: internal/core/update/update_test.go:396 — "fetcher := envRecordingFetcher{onCall: func() {"
+    evidence: internal/core/update/update_test.go:396 — "fetcher := envRecordingFetcher{onCall: func() {"

.abcd/development/intents/shipped/itd-132-hook-binary-to-persistent-data-dir.md

@@ -292,4 +292,4 @@ Gap audit:
     evidence: internal/surface/cli/bootstrap_cache_test.go:330 — "func TestBootstrapNewReleaseSkipsAbsentPathCopy"
   - A test pinning the cache-mode steady state for a cache-provisioned root (data dir set, binary present, no .binary-meta) at zero network; the no-network fast-path test runs without a data dir and the migration test's second run has a .binary-meta root
     evidence: hooks/bootstrap.sh:205 — "[ -f \"$root_meta\" ] || exit 0"
-    evidence: internal/surface/cli/bootstrap_test.go:369 — "func TestBootstrapFastPathTouchesNoNetwork"
+    evidence: internal/surface/cli/bootstrap_test.go:369 — "func TestBootstrapFastPathTouchesNoNetwork"

.abcd/development/intents/shipped/itd-133-abcd-has-a-face-a-block-pixel-duckling-is-the-mascot-the-off.md

@@ -172,4 +172,4 @@ Gap audit:
 - diverged:
   - the decision is linked from this intent — referenced in prose, not linked
     evidence: .abcd/development/intents/shipped/itd-133-abcd-has-a-face-a-block-pixel-duckling-is-the-mascot-the-off.md:55 — "recorded in the decision log"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-150-agent-worktrees-commit-without-the-private-name-guard-abcd-w.md

@@ -84,4 +84,4 @@ Gap audit:
   - spc-43 said a duplicate key from the local store overrides the primary entry; the delivered hook merges the two stores as a union with no override, so both patterns are enforced (strictly more refusals, never fewer)
     evidence: internal/core/ahoy/defaults/pre-commit:453 — "The two stores are a UNION, never an override."
     evidence: .abcd/development/specs/closed/spc-43-agent-worktrees-commit-without-the-private-name-guard-abcd-w.md:60 — "a duplicate key from the local store overrides the primary entry"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-151-five-agent-prompts-read-attacker-influenceable-input-without.md

@@ -88,4 +88,4 @@ Gap audit:
   - the per-agent changelog check was promised as diff-driven ('added or changed in a diff'); delivered as a tree-shaped entry-per-prompt_version check plus a diff-armed unbumped-edit check, so the diff half fires only where CI arms a range
     evidence: internal/core/lint/agentcontract.go:238 — "The DIFF-shaped part runs only when a range is armed"
     evidence: cmd/record-lint/main.go:27 — "agentDiff := flag.String("agent-diff""
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-153-abcd-s-remote-config-apply-verb-should-enable-github-native.md

@@ -82,4 +82,4 @@ Gap audit:
   - the intent title promises enabling 'by default on every managed repo'; delivered as an explicit, confirmed verb that `ahoy install` never runs — the spec's Decisions record this as the adr-44 ruling
     evidence: internal/core/ahoy/remote.go:242 — "a remote write happens only through a dedicated verb the user invokes AND CONFIRMS"
     evidence: .abcd/development/specs/closed/spc-46-abcd-s-remote-config-apply-verb-should-enable-github-native.md:96 — "the verb acts only on explicit invocation against a managed repo"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-154-s4-gate-failed-bootstrap-provisioned-no-binary.md

@@ -87,4 +87,4 @@ Gap audit:
     evidence: hooks/bootstrap.sh:527 — "announcement is therefore held and spent only where it is the only thing a"
   - the 'answers in about a second' timing is not asserted by the gate
     evidence: internal/surface/cli/bootstrap_freshinstall_test.go:150 — "the five-second budget that once stood here, widened for"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-155-scanner-adjacency-galloping-probe-structural-fix.md

@@ -82,4 +82,4 @@ Gap audit:
   - the promise 'a match end is never a truncation artefact' holds under a per-line growth budget; when it is exhausted the probe reverts to the fixed 512-byte window, so on an adversarial many-junction line the old truncation shape can recur (a deliberate resource-exhaustion trade-off recorded in code, not in the intent)
     evidence: internal/adapter/scanner/scanner.go:606 — "reverts to exactly the fixed-window behaviour, which is bounded and was never"
     evidence: internal/adapter/scanner/scanner.go:583 — "if *budget < hi-at {"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-156-the-guard-tokenizer-does-not-perform-brace-expansion-so-a-fl.md

@@ -76,4 +76,4 @@ Gap audit:
     evidence: internal/core/guard/brace_test.go:26 — "`rm -rf dir{1..9}`,"
     evidence: internal/core/guard/brace_test.go:44 — "`git push \${--force,} origin main`,"
 - diverged: (none)
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-157-by-links-layout-publishes-overlapping-positions.md

@@ -85,4 +85,4 @@ Gap audit:
   - the overlap gate flags a by-links overlap as a red result — delivered as a non-zero printed count and a test-suite assertion; site build and site check both stay green on a non-zero count
     evidence: internal/surface/cli/site.go:201 — "layout: %d overlapping bubbles across both arrangements"
     evidence: internal/core/site/check.go:264 — "func Check(req CheckRequest) (CheckResult, error)"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-158-provenance-lacks-pass-b-exemption-marker.md

@@ -81,4 +81,4 @@ Gap audit:
   - the consumer reclassifies the Pass-B section as exempt rather than listing it among the coverage blanks — delivered as one record-level declaration line; the blanks listing is unchanged
     evidence: internal/core/lifeboat/embark_render.go:85 — "if ex := cov.PassBExemption; ex != nil {"
     evidence: internal/core/lifeboat/embark_test.go:1167 — "func TestEmbarkUnmarkedProvenanceReadsAsBefore"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-160-dangling-supersedes-and-spec-targets-nothing-checks-them.md

@@ -79,4 +79,4 @@ Gap audit:
     evidence: internal/core/site/check_test.go:708 — "func TestSupersedesToAPrunedRecordStillCounts"
     evidence: internal/core/site/check_test.go:773 — "func TestCheckPassesWhenABaselinedTargetArrives"
 - diverged: (none)
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-161-record-lint-cannot-see-a-decision-shaped-document-filed-outs.md

@@ -81,4 +81,4 @@ Gap audit:
     evidence: internal/core/lint/crossstore_test.go:207 — "func TestCrossStoreIDClaimSkipsUntrackedFiles"
     evidence: internal/core/lint/crossstore_test.go:167 — "func TestCrossStoreIDClaimIgnoresFencedStatus"
 - diverged: (none)
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-162-adoption-templates-outside-record.md

@@ -73,4 +73,4 @@ Gap audit:
   - the pre-commit config (secrets + absolute-path gate) resolves from the record or the binary — delivered as a substitution: step 5 scaffolds the private name guard instead, and the embedded hook carries no secrets or absolute-path gate
     evidence: commands/prepare-this-repo.md:171 — "5. **Commit gates.** Scaffold them from the binary"
     evidence: internal/core/ahoy/defaults/pre-commit:159 — "# --- itd-74 private name guard"
-- missing: (none)
+- missing: (none)

.abcd/development/intents/shipped/itd-179-the-reasoning-behind-what-was-pursued-no-longer-evaporates-a.md

@@ -128,4 +128,4 @@ Gap audit:
     evidence: .abcd/development/specs/closed/spc-57-the-reasoning-behind-what-was-pursued-no-longer-evaporates-a.md:178 — "- Any semantic judgement of whether a grounds text really names a conjecture."
     evidence: .abcd/development/intents/disciplines/itd-192-an-acceptance-criterion-whose-producer-does-not-exist-is-jud.md:27 — "- **Wired in this phase** — the criterion is `MET_WITH_CONCERNS`, and the"
   - The docs still spell the closed vocabulary by hand even though the behavioural copy is now derived — deliberately, and recorded. The behavioural half is genuinely closed (the six user-facing spellings render from `grounds.UsageSpelling()`/`ProseList()`), so what is missing is the executable enumeration the record itself prescribes as the remedy and declines to apply.
-    evidence: .abcd/work/issues/open/iss-2608301918362294-a-prose-enumeration-of-where-a-value-is-copied-cannot-be-mai.md:46 — "Remedy, deliberately NOT applied tonight: make the enumeration executable."
+    evidence: .abcd/work/issues/open/iss-2608301918362294-a-prose-enumeration-of-where-a-value-is-copied-cannot-be-mai.md:46 — "Remedy, deliberately NOT applied tonight: make the enumeration executable."

.abcd/development/intents/shipped/itd-184-four-cold-reading-definitions-one-blindness-core-each-positi.md

@@ -221,4 +221,4 @@ Gap audit:
     evidence: .abcd/work/issues/open/iss-2608311039586922-commands-reading-md-describes-the-bare-verb-s-definitions-fi.md:14 — "The plugin surface should say resolved rather than present, and say that a malformed definition is a refusal. The itd-184 builder's lane did not include commands/, so the correction was captured rather than taken. — OPEN"
   - Nothing dispatches a reading. The four definitions ship unrun for the whole cycle by spc-62's own declaration, and the regime a definition states is never rendered to an operator: Describe reports only the definition NAMES, not the regime or the file hash the locator computes. Not a criterion gap — every criterion is about the definitions and the surfaces, not about a run — but it is the bound on what any of this has been measured against, and the instruments sit at prompt_version 0.1.0, declared shipped and honestly unmeasured.
     evidence: internal/core/reading/status.go:31 — "Definitions []string `json:\"definitions\"`  — names only; Regime and SHA256 resolved at status.go:56 are discarded"
-    evidence: .abcd/development/specs/closed/spc-62-four-cold-reading-definitions-one-blindness-core-each-positi.md:246 — "**Running a reading.** The instrument ships unrun for the whole cycle: the definitions are written, linted and tested, and none is dispatched."
+    evidence: .abcd/development/specs/closed/spc-62-four-cold-reading-definitions-one-blindness-core-each-positi.md:246 — "**Running a reading.** The instrument ships unrun for the whole cycle: the definitions are written, linted and tested, and none is dispatched."

.abcd/development/intents/shipped/itd-185-one-ingest-verb-validates-every-cold-reading-output-includin.md

@@ -361,4 +361,4 @@ Gap audit:
     evidence: .abcd/development/intents/shipped/itd-185-one-ingest-verb-validates-every-cold-reading-output-includin.md:102 — "Whether the regime signatures lint cleanly — untested; the degradation path exists precisely because of it. — still untested at 1d84ce26"
   - A run refused inside the write phase leaves an empty directory standing in the COMMITTED tier. rollbackRun removes the ledger run directory only from inside the closure it runs when there were entries to remove, so a run that reached capture.IngestReading, had its directory created, and was then refused by the size invariant leaves `.abcd/work/issues/readings/<run>/` empty and permanent — the next invocation's sweep clears the stage and walks past it. Harmless in git, which does not track empty directories, but it is a durable artefact of a run the design says never happened, and it is the visible half of the same gap as the missing refusal record in ac-10.
     evidence: internal/core/reading/ingest.go:764 — "_ = root.Remove(ledgerRel) — inside unlink, which is only called when len(entries) > 0"
-    evidence: internal/core/reading/ingest.go:767 — "if len(entries) > 0 { if err := underLedgerLock(root.Name(), unlink); err != nil { — measured: after the size-refused run and a subsequent sweep, the empty committed directory survives"
+    evidence: internal/core/reading/ingest.go:767 — "if len(entries) > 0 { if err := underLedgerLock(root.Name(), unlink); err != nil { — measured: after the size-refused run and a subsequent sweep, the empty committed directory survives"