…5/5 LIVE DISCHARGE milestone (#1447)

Canonical record of today's terminal-discharge milestone. The
apr-cpu-vs-gpu-output-parity-v1 contract reaches its complete state:
all 5/5 falsifiers DISCHARGED with live empirical evidence on the
canonical Qwen2.5-Coder-7B teacher.

Milestone significance:
- First contract in the SHIP-TWO program to reach 5/5 DISCHARGED
  (complete-evidence terminal state).
- Largest single-cycle coverage flip of the SHIP-TWO program: +5
  falsifiers DISCHARGED in one 2-PR cycle (#1445 + #1446).
- The §41 → §43 → §44 → §45 jidoka chain is contract-complete:
  silent-GPU-gibberish on canonical broken-GPU is no longer possible.
  Both impl closure AND end-to-end live verification delivered.

Coverage tally: 15+37 → 20+32.
Contract: v1.3.0 → v1.5.0 ACTIVE.
MODEL-1 ship %: 89% → 91%.

§45 documents:
- 45.1 What landed (PR table)
- 45.2 The complete observed jidoka chain (verbatim from smoke log)
- 45.3 Coverage flip (5/5 status table)
- 45.4 Why this milestone matters (audit + MODEL-1 + cadence)
- 45.5 Five Whys
- 45.6 Net effects
- 45.7 Next-session pickup (SHIP-007 GPU kernel fix, MODEL-2 §35
  real-training, cross-contract sweep — all multi-PR research tracks)

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…rift gate (#1448)

Two related preparation steps for the v0.32.0 cut decision:

## CHANGELOG

Fill out the empty `[Unreleased]` section with today's session body of work
(238 commits since v0.31.2):

- **CPU/GPU output parity contract** (jidoka armor): `apr-cpu-vs-gpu-output-parity-v1`
  v1.0.0 → v1.5.0 ACTIVE with **5/5 falsifiers DISCHARGED** in a single 2-PR cycle
  (#1445 + #1446) — first contract in the SHIP-TWO program to reach complete-evidence
  terminal state. CUDA + wgpu fallback log prefixes + inline cosine parity gate.
- **`apr trace --save-tensor`** — new flag for SHIP-007 layer-0 oracle bisection;
  `apr-cli-trace-save-tensor-v1` v1.4.0 FUNCTIONAL.
- **HF FP16 oracle bisection** — pinpoints SHIP-007 to layer-0 attn_out
  (cos=0.99999995 attn_norm → 0.9966 attn_out).
- **Distillation training contract** — 9/9 falsifiers algorithm-bound.
- **MoE expert dispatch parallelized** — 2× speedup (#1396).
- **APR file mmap** — unblocks `apr diff --values` on 7B (#1058).
- **M32d numerical-parity bundle** — Q/K RMSNorm + rope_theta + chat template (#1228).
- **150+ contract algorithm-bind sweep** — record cycle, kernel + format + training +
  GPU-backend + CLI families flipped from `unbound` to `PARTIAL_ALGORITHM_LEVEL`.

## README drift gate repair

`bash scripts/check_readme_claims.sh` was FAILING:

- README claimed 1096 contracts, filesystem has 1105
- README claimed 79 CLI commands, `apr --help` lists 80

Fixed both numbers in the contract-backed table AND the prose references.
Drift gate now PASS 4/4.

Five Whys:

1. Why was the gate failing? README contract counts and CLI counts are stale.
2. Why are they stale? 9 new contracts and 1 new CLI command merged since the
   last README update.
3. Why didn't the gate catch it earlier? It's a script — not yet wired into CI
   as a hard gate (FALSIFY-README-001..004 are PARTIAL_ALGORITHM_LEVEL, the
   shell wrapper is documented in the contract but doesn't fail PRs).
4. Why isn't it a CI gate yet? `readme-claims-v1` is recent (2026-04-24),
   wired to `bash scripts/check_readme_claims.sh` but not to a workflow step.
5. Why fix it now? Pre-release hygiene — releases must ship green drift gates
   per `feedback_post_publish_qa_required.md`.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>