[HARDENING] PENDING-126 + PENDING-122 Amendment 2 — what inducing red revealed, and REVIEWED-102..105 placed

All three findings came from contact while building a red fixture for the
REVIEWED-103 acceptance. None was sought; the search for a control that worked is
what exposed them.

The fleet already violates the condition REVIEWED-104 attached to the NEW
live-binding assertion, on a dependency the ruling did not consider. Three suites
crash on a gitignored corpus/index.db with a raw sqlite traceback, and run-fleet
reports FLEET RED indistinguishably from a code defect — while store.py rebuilds
that file in 0.628 seconds and the clone then runs 7/7 green. So the condition is
retroactive, not prospective. And test_retrieve.py already detects the absence and
skips with a named reason, which makes PENDING-124 recommendation (d) concrete: the
honest third state exists in this fleet, in one suite, and three others lack it.

R0's section_end bound is unguarded. Removing it leaves 31/31 passing. That is the
rule R0 was created to establish after two consumers disagreed on 3 of 253 patterns
with neither right — asserted in prose, correct-but-inert on the live corpus, and
therefore invisible to every test.

test_navigate crashes with StopIteration rather than naming a failure. The exit code
was always right; the legibility is missing — REVIEWED-100's own distinction,
recurring where its fix does not reach.

Also commits REVIEWED-102 through -105, placed by the steward and left uncommitted.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A35wiD55yRHj5U1ECZAX4t

claude/memory/session-ledger-2026-08-08.md

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: feedback
   originSessionId: 7d08dad4-626a-484c-870b-8f1a9674db7a
-  modified: 2026-08-08T13:30:54.198Z
+  modified: 2026-08-08T14:45:17.679Z
 ---
 
 # Session Ledger — 2026-08-08
@@ -180,6 +180,37 @@ the omission is itself the finding above.*
   work; it is that I reach for a check whose vocabulary I have not verified against the thing
   it must match** — the substrate-vs-description class, pointed at my own instruments.
 
+### ⎯ SESSION 3 authorization moves ⎯
+
+- **REVIEWED-101 (e) — engine half BUILT** (`eecc8bb`), wiring deliberately **NOT** placed.
+  Built as a **delegation** to `ingest_gate.py`, which already enforced §1.1 on both
+  named surfaces. Suite 24 → **41**; fleet **221/221, 7/7 exit 0**.
+- **PENDING-119** filed `[PROPOSAL]` — condition 6 vs the ruling's own "(e) needs no
+  cross-repo enumeration". **Steward directed: file, do not wire.**
+- **PENDING-120** filed `[HARDENING]` — the trigger's pathspec misses `engine/`+`tests/`.
+  **Steward directed: file separately.**
+- **PENDING-117 AMENDMENT 2** appended — pointer only, nothing above altered.
+- Commits: engine `eecc8bb`, `f1bb227`; dotfiles `02c6875`. **Neither repo pushed** —
+  engine `ahead 2`, dotfiles `ahead 1`; the push belongs to the wrap.
+
+- **T~15:5x — the day's error class has a mechanical root, found at last.** `ls` is
+  **aliased** in this profile (eza-like; it rejects a bare path as an `--icons` value).
+  Instance (7) above was never a missing file — the alias ate the argument and returned
+  exit 2. Switched to `command ls`. Worth keeping: **an exit code from an aliased command
+  is evidence about the alias, not about the world.** Two of the day's seven check-errors
+  reduce to this one shell fact.
+- **T~16:0x — an eighth, caught and not narrated:** read `${PIPESTATUS[0]}` after an
+  intervening `echo` had already clobbered it, printing `exit=` empty. Re-ran clean.
+  Same family: **a check whose vocabulary I had not verified against its own mechanics.**
+
+- **What held, this session.** Every claim that entered a commit message or a governance
+  filing was substrate-checked first: the fixture-only census by enumerating all six
+  invocations rather than grepping; the delegation argument by reading L128–131/L150–153;
+  the write hazard by reasoning about index-vs-worktree and then *not* asserting it
+  untested; byte-identity of the refactored write by an empty `git diff`; the red
+  direction on the **real** manifest with a `cmp`-verified restoration. **The errors
+  stayed in throwaway checks; nothing false reached a durable surface.**
+
 ## Sub-agent dialogues
 
 ## Bypasses