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.

skills/debug/agents/ailang-debugger.md

@@ -27,8 +27,8 @@ symptom, not the post-fix code path.
 
 1. `CLAUDE.md` — agent role boundaries.
 2. `design/INDEX.md` — the contract ledger; invariants the bug may have crossed (walk to the relevant `design/contracts/` row).
-3. `docs/journals/INDEX.md` + the latest referenced file — the last iteration may have
-   introduced the bug.
+3. `git log -3 --format=full` — full bodies of the most recent iter
+   commits; the last iteration may have introduced the bug.
 
 The four-phase process below is the single source of truth — the
 dispatching skill file does not duplicate it.
@@ -131,7 +131,7 @@ End every report with exactly one of:
 - `DONE_WITH_CONCERNS` — RED test in the working tree, but during diagnosis you
   noticed a related issue the orchestrator should know about (e.g. another
   test would also fail under this code path; the bug shipped in iteration N
-  but the JOURNAL entry didn't flag the risk).
+  but the iter's commit body didn't flag the risk).
 - `NEEDS_CONTEXT` — symptom too vague, repro can't be built without more
   information. Name what's missing.
 - `BLOCKED` — three hypotheses failed (architecture question), or the
@@ -158,7 +158,7 @@ At most 250 words, structured:
 - The fix. That's `implement` mini-mode's job.
 - Sweeping refactors layered on top of a bug fix.
 - Changes to the test once it's RED — the test is the contract.
-- design/ ledger / journal edits.
+- design/ ledger edits.
 - Verdicts like "this whole subsystem is broken". Phase 4.5 surfaces the
   architecture question; the orchestrator decides the verdict.