workflow: replace per-iter journal system with git log + BLOCKED.md

The per-iter journal under docs/journals/ duplicated the iter commit
body's substance and accumulated as Verlauf-Doku with no Future-Use.
Sweep across all live control documents: CLAUDE.md, the 7 SKILL.md
files, the 11 agent files, design/INDEX.md and the contracts/models
that referenced journals, docs/roadmap.md, and the handful of source
comments + tests that pointed at journal files for rationale.

Mechanism changes:
- Standing-reading-lists in every agent now read `git log -N --format=full`
  for recent project state, never per-iter journal files. The architect
  reads `git log <prev-milestone-close>..HEAD --format=full` for audit
  scope.
- implement-orchestrator no longer writes a journal file. DONE outcomes
  emit just code + stats; the end-report is the per-task summary the
  Boss uses to write the commit body. PARTIAL/BLOCKED outcomes emit
  BLOCKED.md at the repo root — uncommitted by convention, Boss removes
  on repair or discard. New iron-law line + four-rationalisation row
  + red-flag bullet codify it.
- audit ratify mechanic: --update-baseline is now paired with an explicit
  ratify paragraph in the audit-close commit body, not a separate
  JOURNAL ratify entry.
- design/contracts/honesty-rule.md: "history and rationale lives in
  docs/journals/" → "lives in git log (iter and audit commit bodies)".
  Pinned phrase preserved verbatim.
- CLAUDE.md "Roles of …" section reframed: design/, git log,
  journal-archive.md (content-frozen), roadmap.md, specs/, plans/.
  No docs/journals/ slot anymore.
- roadmap.md context-lines that pointed at per-iter journals are
  dropped where the spec/commit already carries the rationale, or
  rephrased to "shipped in the <iter> iter commit" / "docs/journal-
  archive.md (<date> entry)" for pre-2026-05-11 references.

What stays (this commit):
- docs/journals/ directory and contents are NOT touched. Removing the
  contents is a separate follow-up.
- docs/journals/2026-05-19-design-decision-records.md still has live
  readers (docs_honesty_pin.rs Z 108 + parse.rs + duplicate_ctor_pin.rs
  + 3 roadmap mentions) — also follow-up.
- docs/journal-archive.md still exists; its self-pointer header has
  been updated to drop the "see docs/journals/INDEX.md" mention.

Workspace builds, full test suite green.

design/models/rc-uniqueness.md

@@ -133,7 +133,8 @@ is too.
 
 **The GC bench (`bench/run.sh`) showed
 Boehm contributing a substantial fraction of runtime on allocation-heavy workloads
-that hold the heap fully live (bench notes in JOURNAL). The
+that hold the heap fully live (raw numbers in `bench/orchestrator-stats/`;
+prior bench iter commit bodies record the runs). The
 mainstream "RC + inference" position is extended with mandatory
 LLM-author mode annotations (`borrow` / `own`), explicit `clone`,
 first-class `reuse-as`, and `drop-iterative` data attrs.**
@@ -165,7 +166,8 @@ env struct) and `bench_hof_pipeline` (poly-ADT + indirect
 dispatch). The closure-chain fixture measures wider than the 1.3×
 linear/tree target: each step pays two allocs and two decs against
 one bump-pointer bump, doubling the allocation tax on closure
-construction (current ratio recorded in JOURNAL bench entries).
+construction (current ratio recorded in
+`bench/orchestrator-stats/` and the bench iter commit bodies).
 This is a representational cost of the closure-pair layout,
 not a defect in the RC implementation; a future slab/pool
 allocator for fixed-shape pair cells (a Boehm-retirement follow-up)

design/models/typeclasses.md

@@ -146,8 +146,8 @@ with the visible target, not in the call instruction. The
 end-to-end gain shrinks toward zero on larger callee bodies and
 cold call sites, but the architectural claim — "mono enables
 optimisations vdisp forbids" — holds across the spectrum
-(`bench/mono_dispatch.py` and the corresponding JOURNAL bench-notes
-entry record the measured ratios).
+(`bench/mono_dispatch.py` and `bench/orchestrator-stats/`
+record the measured ratios).
 
 The separator is `__` rather than `#` or `@` because `#` and `@`
 are invalid in LLVM IR global identifiers (the IR verifier rejects