iter or.1.3: repoint skill + agent reading lists to docs/journals/

skills/debug/agents/ailang-debugger.md

@@ -24,7 +24,7 @@ genuinely captures the symptom, not the post-fix code path.
 
 1. `CLAUDE.md` — agent role boundaries.
 2. `docs/DESIGN.md` — invariants the bug may have crossed.
-3. `docs/JOURNAL.md` — most recent entries; the last iteration may have
+3. `docs/journals/INDEX.md` + the latest referenced file — the last iteration may have
    introduced the bug.
 
 The four-phase process below is the single source of truth — the
@@ -152,7 +152,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.md / JOURNAL.md edits.
+- DESIGN.md / journal edits.
 - Verdicts like "this whole subsystem is broken". Phase 4.5 surfaces the
   architecture question; the orchestrator decides the verdict.