Gate & ratchet audit: full-inventory report, five fail-opens armed, dead gates deleted

.claude/commands/deslop-reborn.md

@@ -1,7 +1,7 @@
 ---
 description: One iteration of the IronClaw Reborn de-slop loop — take ONE Reborn crate, fan out parallel review sub-agents (thermo-nuclear quality, paranoid architect, interface/contract/invariants, test-coverage/wiring), synthesize, apply fixes/refactors/missing tests, open a PR. Stop.
 disable-model-invocation: true
-allowed-tools: Bash(cargo fmt:*), Bash(cargo clippy:*), Bash(cargo test:*), Bash(cargo build:*), Bash(git:*), Bash(gh:*), Bash(grep:*), Bash(rg:*), Bash(ls:*), Bash(wc:*), Bash(scripts/check-boundaries.sh:*), Bash(scripts/reborn-e2e-rust.sh:*), Read, Grep, Glob, Edit, Write, Agent
+allowed-tools: Bash(cargo fmt:*), Bash(cargo clippy:*), Bash(cargo test:*), Bash(cargo build:*), Bash(git:*), Bash(gh:*), Bash(grep:*), Bash(rg:*), Bash(ls:*), Bash(wc:*), Bash(scripts/reborn-e2e-rust.sh:*), Read, Grep, Glob, Edit, Write, Agent
 argument-hint: "[crate name, e.g. ironclaw_turns]"
 ---
 

.claude/skills/ironclaw-reborn-architecture-review/SKILL.md

@@ -28,6 +28,6 @@ Layer discipline here is enforced by machines, not vibes: `cargo test -p ironcla
 
 ## Verify
 
-`cargo test -p ironclaw_architecture_tests` · `bash scripts/check-boundaries.sh` (legacy inventory; may be noisy on HEAD, don't treat as the Reborn architecture gate) · `cargo clippy -p <crate> --all-targets --all-features -- -D warnings` · if routes changed: `cargo test -p ironclaw_webui --test webui_v2_descriptors_contract`.
+`cargo test -p ironclaw_architecture_tests` · `cargo clippy -p <crate> --all-targets --all-features -- -D warnings` · if routes changed: `cargo test -p ironclaw_webui --test webui_v2_descriptors_contract`.
 
 **Worked good/bad examples** (before/after shapes, live exemplars, re-verify commands): [references/worked-examples.md](references/worked-examples.md) — the living curriculum; update it as the code evolves.

.claude/skills/ironclaw-reborn-skill-maintainer/SKILL.md

@@ -19,7 +19,7 @@ Every rule below counters a rot pattern this repo's guidance is prone to. Guidan
 2. **Verify every concrete reference at write time — and make it re-verifiable.** Branches die silently; prefer in-tree worked examples over branch/PR refs. For each cited path/symbol, keep a one-line grep a maintainer can re-run.
 3. **No universal claims without a count.** Avoid absolute docs coverage claims. Write "most; fall back to Cargo.toml + lib.rs" or generate the list.
 4. **Triggers live in frontmatter `description`, nowhere else.** The runtime surfaces only frontmatter for selection; a "when to use" buried in the body is invisible. Description = triggering conditions only — never a workflow summary (agents will follow the summary and skip the body).
-5. **Never claim enforcement that doesn't exist.** Before writing "enforced by X", run X. If you add a check to `scripts/pre-commit-safety.sh` or `scripts/check-boundaries.sh`, add its self-test — and know there are two hook install paths (`.githooks/` vs `scripts/dev-setup.sh` symlink); a check is only real if both run it.
+5. **Never claim enforcement that doesn't exist.** Before writing "enforced by X", run X. If you add a check to `scripts/pre-commit-safety.sh`, add its self-test — and know there are two hook install paths (`.githooks/` vs `scripts/dev-setup.sh` symlink); a check is only real if both run it.
 6. **After any extraction/move/rename, grep the guidance layer** for old paths in the same PR: `.claude/`, `AGENTS.md`, `CLAUDE.md`, `crates/AGENTS.md`, `docs/reborn/contracts/`, skill bodies.
 7. **Runtime-skill spec must track the parser.** `crates/domains/ironclaw_skills/src/types.rs` supports `requires.config`, `requires.skills`, `activation.setup_marker`, and silently truncates >20 keywords / >5 patterns (`enforce_limits`). If you use or change parser behavior, update `.claude/rules/skills.md` in the same PR.
 8. **Codex parity check.** Codex cannot load Claude skills; it reads AGENTS.md. When a skill carries a rule Codex must also follow, the AGENTS.md hierarchy needs the pointer *with enough inline substance* ("read `.claude/skills/<name>/SKILL.md`" works — skills are plain markdown).

.claude/skills/ironclaw-reborn-testing/SKILL.md

@@ -19,7 +19,7 @@ Pick the tier first; everything else follows. The repo's tier knowledge lives in
 
 - **Regression-per-fix is mechanically checked for conventionally marked fix/high-risk changes** (commit-msg hook + `regression-test-check.yml`). Escape hatch `[skip-regression-check]` exists — using it on a real fix will be questioned in review.
 - **Consolidate, don't proliferate**: extend the existing test that already drives the path (a case, a scripted turn, an assertion) before standing up a new file. Say why an existing test couldn't absorb a genuinely new scenario.
-- **Persistence = both backends.** PostgreSQL + libSQL parity where production-facing; the model is `ironclaw_hooks`' dual-backend shape (`crates/loop/ironclaw_hooks/src/postgres_backend/` + `crates/loop/ironclaw_hooks/src/libsql_backend/`, proved equivalent by `crates/loop/ironclaw_hooks/tests/parity_matrix.rs` and `crates/loop/ironclaw_hooks/tests/multi_host_adversarial.rs`). Feature-gate integration tests (`check-boundaries.sh` enforces the gating for root `tests/`).
+- **Persistence = both backends.** PostgreSQL + libSQL parity where production-facing; the model is `ironclaw_hooks`' dual-backend shape (`crates/loop/ironclaw_hooks/src/postgres_backend/` + `crates/loop/ironclaw_hooks/src/libsql_backend/`, proved equivalent by `crates/loop/ironclaw_hooks/tests/parity_matrix.rs` and `crates/loop/ironclaw_hooks/tests/multi_host_adversarial.rs`). Feature-gate integration tests.
 - **The backend-integration tier is NOT a PR gate unless the workflow says so** (re-verify: `grep -n integration .github/workflows/platform-and-compat.yml`): full Postgres coverage may run post-merge or nightly. A green PR does not prove the tier ran; run it locally when your change is DB/runtime-shaped — crate-level, e.g. `cargo test -p ironclaw_hooks --features integration,test-support` (the workspace-root `integration` feature is empty; a bare root `cargo test --features integration` runs nothing extra).
 - **Never add a silent self-skip to PR-gated tests.** `if docker_missing { return }` hides the suite from CI. Existing Docker sandbox canaries still need migration; new tests should skip loudly via feature gates or explicit env opt-outs.
 - **Capability results and terminal errors have their own test shape** — recoverable failures must remain model-visible outcomes, while host failures are terminal; test the caller against the capability-access contract and its real redaction/evidence validation.

.claude/skills/ironclaw-reborn-testing/references/exemplar-tests.md

@@ -38,7 +38,7 @@ When a predicate selects what goes out the wire, the test must construct the rea
 
 **BAD for PR-gated coverage**: `if docker_unavailable { return }` — the container security suite silently vanishes from CI and no gate notices. Existing Docker sandbox canaries still use soft skips; don't copy that pattern into new gate coverage.
 
-**GOOD**: make absence loud — feature-gate the test (`#![cfg(all(feature = "postgres", feature = "integration"))]`, which `scripts/check-boundaries.sh` enforces for root `tests/`), or require an explicit opt-out env var and *fail* when the dependency is missing without it. A skipped security test that doesn't announce itself is indistinguishable from coverage.
+**GOOD**: make absence loud — feature-gate the test (`#![cfg(all(feature = "postgres", feature = "integration"))]`), or require an explicit opt-out env var and *fail* when the dependency is missing without it. A skipped security test that doesn't announce itself is indistinguishable from coverage.
 
 ## 6. Naming your contract's tests
 

.coderabbit.yaml

@@ -107,7 +107,8 @@ reviews:
         keep ironclaw_hooks_postgres / ironclaw_hooks_libsql in parity via hooks_parity).
         Multi-step DB operations must be wrapped in a transaction. Driver types
         (tokio_postgres::, libsql::) must not leak outside the allowed modules
-        (scripts/check-boundaries.sh).
+        (enforced by reborn_persistence_driver_boundary in
+        crates/app/ironclaw_architecture_tests).
     - path: "**/*.wit"
       instructions: |
         Hand-written WIT contracts define the trusted/untrusted WASM ABI. Interface changes

crates/AGENTS.md

@@ -142,9 +142,8 @@ workspace gate (`cargo fmt`, workspace clippy, `cargo test`) is the root
 `AGENTS.md`'s; test tiers and the regression rules are
 `.claude/rules/testing.md`.
 
-> **Do not reach for `scripts/check-boundaries.sh`.** Measured 2026-08-05: it
-> fails on a clean tree (its check 5 grep false-positives on live test files)
-> and checks 1/2/3/6 target the deleted v1 `src/` tree, passing vacuously.
+> The legacy `check-boundaries.sh` script is deleted (measured 2026-08-05: it
+> failed on a clean tree and its v1-targeted checks passed vacuously).
 > Boundary enforcement for `crates/` is the architecture suite above.
 
 ## Cross-family change routes

crates/app/ironclaw_architecture_tests/tests/reborn_capability_dto_collapse_ratchet.rs

@@ -9,26 +9,18 @@
 //! that **"the §10 mirror-DTO ratchet's allowlist is what makes this safe: the
 //! old [shapes] are frozen entries that may only disappear."**
 //!
-//! This is that ratchet. It freezes the current set of collapse-target DTOs and
-//! fails on any change:
+//! The collapse COMPLETED (#6447 retired the last request DTOs), so this file
+//! is no longer the shrinking freeze that §9 describes — it is the permanent
+//! zero-gate that survives it: [`RETIRED_COLLAPSE_DTOS`] names the retired
+//! mirror shapes, and the test fails if any of them is ever re-declared
+//! (the exact §1.1 Mechanism 1 failure, attempted after the fact).
 //!
-//! - a **second definition** of a frozen name (a downstream crate re-declaring an
-//!   upstream request "for decoupling" — the exact §1.1 Mechanism 1 failure) —
-//!   flagged by the multiplicity check;
-//! - **deleting** one without trimming [`FROZEN_COLLAPSE_DTOS`] also fails — so
-//!   the allowlist shrinks in lock-step as the collapse lands (§10: compare set
-//!   membership, never a count), and reviewers watch it get shorter toward the
-//!   §3 end state (`Invocation` + the surviving per-lane requests + the five
-//!   result channels — zero mirrors).
-//!
-//! Definition of done for this axis: every entry below is deleted (its fields
-//! now carried by `Invocation`/`Authorized`, its result variants by
-//! `Resolution`), and this file is deleted with the last of them (enforced —
-//! the test fails on an empty allowlist).
-//!
-//! Owner: the §3 capability-path collapse slice series under the #6168
-//! umbrella (authorize → dispatch → result-channel migration) trims this list
-//! in the same PRs that delete the types; reviewers hold additions to zero.
+//! Two of the ten originally-frozen names are deliberately NOT here:
+//! `CapabilityOutcome` (deleted by #6299 before the retired-list conversion)
+//! and `CapabilityDispatchRequest` (its removal was a blessing, not a
+//! deletion — it survives as the canonical port type in
+//! `ironclaw_host_api::dispatch`). Reintroducing the former fires nothing;
+//! add it below if that ever becomes a live hazard.
 //!
 //! Scanner semantics (shared with the other §10 ratchets — see
 //! [`ratchet_support`]): comments/strings stripped before matching; covers

crates/app/ironclaw_architecture_tests/tests/reborn_composition_boundaries.rs

@@ -20,15 +20,13 @@ use ratchet_support::{crate_path, workspace_root};
 const SUBSTRATE_CRATES: &[&str] = &[
     "ironclaw_auth",
     "ironclaw_host_api",
-    "ironclaw_storage",
     "ironclaw_filesystem",
     "ironclaw_event_log",
     "ironclaw_event_projections",
     "ironclaw_event_streams",
     "ironclaw_extension_registry",
     "ironclaw_authorization",
     "ironclaw_approvals",
-    "ironclaw_approvals",
     "ironclaw_resources",
     "ironclaw_trust",
     "ironclaw_capabilities",
@@ -47,16 +45,21 @@ const SUBSTRATE_CRATES: &[&str] = &[
     "ironclaw_openai_compat",
     "ironclaw_telegram_extension",
     "ironclaw_assistant",
-    "ironclaw_assistant",
     "ironclaw_triggers",
 ];
 
 #[test]
 fn no_substrate_crate_depends_on_composition_root() {
     let dependencies = workspace_dependencies();
     for substrate in SUBSTRATE_CRATES {
+        // Fail closed on an unresolvable entry: the silent `continue` this
+        // replaces let `ironclaw_storage` sit in this list long after the
+        // crate was deleted — a row that resolves to nothing polices nothing.
         let Some(actual) = dependencies.get(*substrate) else {
-            continue;
+            panic!(
+                "{substrate} is listed in SUBSTRATE_CRATES but is not a workspace package; \
+                 remove the stale entry (or fix the name) so this list keeps matching the tree"
+            );
         };
         assert!(
             !actual.iter().any(|dep| dep == COMPOSITION_CRATE),