batch/ont-10: every remaining ONT-10 row for 0.70.0 (one PR, one quorum, one CI)

.claude/skills/apr-dogfood/SKILL.md

@@ -1591,7 +1591,7 @@ The nine clusters at zero, largest first: `http-orchestrate-banco` (95),
 `test-harness` (49), `rag-eval` (44), `qa-cgp` (37), `simulation` (18),
 `orchestrate-pacha-secrets` (17).
 
-**Report both numbers or neither (T2).** "5 of 14 clusters gated (35.7%)" without "144 of 864 features gated (16.7%)" beside it is a proxy masquerading as coverage, and the gate refuses to emit it — *on this line too*.
+**Report both numbers or neither (T2).** "5 of 14 clusters gated (35.7%)" without "144 of 894 features gated (16.1%)" beside it is a proxy masquerading as coverage, and the gate refuses to emit it — *on this line too*.
 
 The rule is about the NUMBER, not about a phrasing, and it is enforced on every
 surface that can emit one: the gate's own report, the receipt, the output of

.claude/skills/pr-review/SKILL.md

@@ -22,7 +22,7 @@ difference is a defect in this file.
 **Contract**: `contracts/pr-review-skill-v2.yaml` (§1 grounding, §7 blocking, §8 metrics)
 **Guard**: `scripts/check_pr_review_receipt.sh` — it validates what you emit here, it has
 its own positive controls, and its mutation set (`scripts/mutate-guard.sh`) reports
-233/233. **Run it on your own receipt before you post anything.**
+237/237. **Run it on your own receipt before you post anything.**
 
 ## Context
 
@@ -438,7 +438,7 @@ Bash guards are exercised with `bats-core` fixtures. For the receipt guard itsel
 mutation set already exists and is a derivation, not a list:
 
 ```bash
-bash scripts/mutate-guard.sh          # 233/233 on scripts/check_pr_review_receipt.sh
+bash scripts/mutate-guard.sh          # 237/237 on scripts/check_pr_review_receipt.sh
 ```
 
 **`attempted: 0` with `status: consulted` is rejected** (fixture row 2). A mutation set
@@ -1192,7 +1192,7 @@ the real merged commits, not from the spec's reasoning about them.
 ## §13 Autonomous merge on quorum (DESIGNED AND BUILT, **NOT ARMED**)
 
 Spec §13. Operator instruction, 2026-08-31: PRs auto-merge once the review quorum passes.
-The mechanism exists — `scripts/pr_review_quorum_arm.sh`, a table of 83 rows, a 134-mutant
+The mechanism exists — `scripts/pr_review_quorum_arm.sh`, a table of 90 rows, a 134-mutant
 set at 100% — and **it is reachable from no workflow that can merge anything.** §13.11 is
 the arming ladder; rung 0 is where this file is written.
 
@@ -1345,7 +1345,7 @@ That is the first falsifiable property of the section, and `q-44` plus the
 ### §13.9 Verifying the mechanism
 
 ```bash
-bats tests/pr-review-quorum.bats            # 83 rows: one per refusal path, four that PERMIT
+bats tests/pr-review-quorum.bats            # 90 rows: one per refusal path, four that PERMIT
 bash scripts/mutate_quorum_arm.sh           # 134/134 — §13.10 fixes this at one, no ratchet
 bash scripts/mutate_quorum_arm.sh --list    # the catalogue, no mutants run
 ```

.claude/skills/pre-release/SKILL.md

@@ -326,6 +326,11 @@ regression this repo has on record, and its power *falls* as data accumulates
 Richer fields (surface counts, findings, notable, verdict) are encouraged — the receipts
 already under `evidence/dogfood/` are the worked examples.
 
+**The tracked implementation of this step** is `scripts/release/host_receipt.sh`, which
+`scripts/release/autopilot.sh` ships to each host after publish (#3731). Never hand-roll
+the sweep; `scripts/check_dogfood_shim.sh` row 1b allows those two scripts only while
+this paragraph names them.
+
 **The sweep must `cargo install` the PUBLISHED crate**, not build the local tree.
 Building the tree tests what you have; installing tests what a user gets. On a box with a
 pre-existing `apr` the install correctly fails closed (rc=101) *before* compiling — use

.gitattributes

@@ -23,3 +23,8 @@
 #
 # scripts/check_append_only_ledgers.sh holds that distinction as a case table.
 docs/audits/*.jsonl merge=union
+# Append-only ledgers one level down. `docs/audits/*.jsonl` does not cross a `/`,
+# so these two resolved no merge driver (check_append_only_ledgers, after the
+# main merge into #4431). Named file by file: the scope rule above still holds.
+docs/audits/review-corpus/corpus-v1.jsonl merge=union
+docs/audits/rex-001/rex-04-admission.jsonl merge=union

.githooks/pre-push

@@ -19,4 +19,14 @@ cargo doc --no-deps -q 2>/dev/null || echo "WARN: cargo doc failed"
 echo "── ComputeBrick Compliance ──"
 pmat comply check --failures-only 2>/dev/null || true
 
+echo "── #4415/#4416: CI guard steps (scripts/ci_guards.sh, the script CI runs) ──"
+# The drift check is a YAML parse, so it always runs. The full guard run takes
+# many minutes; opt in with APR_PREPUSH_GUARDS=1 (or run `make guards-local`).
+rc=0; bash scripts/ci_guards.sh --check-coverage || rc=$?
+[ "$rc" -eq 1 ] && exit 1
+[ "$rc" -eq 0 ] || echo "WARN: guard drift check could not run (rc=$rc)"
+if [ "${APR_PREPUSH_GUARDS:-0}" = 1 ]; then
+    bash scripts/ci_guards.sh || exit 1
+fi
+
 echo "✅ Pre-push passed"

.github/actionlint.yaml

@@ -24,3 +24,5 @@ self-hosted-runner:
     - apple-silicon
     - m4
     - mini
+    # #4292 / infra#1042: the mini's dedicated repo-level release runner
+    - mini-builder