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

skills/implement/agents/ailang-implementer.md

@@ -29,7 +29,7 @@ of every dispatch:
 1. `CLAUDE.md` — orchestrator framing, agent role boundaries.
 2. `docs/DESIGN.md` — the canonical specification. Architectural decisions
    here are binding.
-3. `docs/JOURNAL.md` — the most recent milestone-relevant entries. The latest
+3. `docs/journals/INDEX.md` + the latest 1–3 milestone-relevant per-iter files. The latest
    entry is the current state of the project.
 
 You do **not** open `docs/plans/<iteration>.md` or `docs/specs/<milestone>.md`
@@ -99,7 +99,7 @@ the test.
 
 ## The Process
 
-1. Read the standing list (CLAUDE.md, DESIGN.md, JOURNAL.md tail).
+1. Read the standing list (CLAUDE.md, DESIGN.md, latest per-iter journals).
 2. Read the carrier in full. Confirm `task_text` is concrete (no TBD, no
    "similar to Task N"). If it contains placeholders, return `BLOCKED` with
    "plan placeholder" — the plan failed self-review and must be fixed

skills/implement/agents/ailang-tester.md

@@ -24,7 +24,7 @@ invariant in the doc comment, and you stop.
 ## Standing reading list
 
 1. `CLAUDE.md`, `docs/DESIGN.md` — invariants the tests must protect.
-2. `docs/JOURNAL.md` — most recent iteration entries; they tell you what
+2. `docs/journals/INDEX.md` + the latest 1–3 referenced files — most recent iteration entries; they tell you what
    shipped and is therefore worth protecting.
 3. `examples/*.ail.json` — the canonical fixture style. The schema is
    `ailang/v0`; existing examples are authoritative.
@@ -75,7 +75,7 @@ DETERMINISTIC: SAME INPUT, SAME OUTPUT, EVERY RUN.
    - Add the corresponding test in `crates/ail/tests/e2e.rs`.
    - Doc comment names the property.
 4. Run `cargo test --workspace`. Must be green.
-5. Commit per existing JOURNAL style (`iter <X>.<n>: e2e for <feature>`).
+5. Commit per existing journal style (`iter <X>.<n>: e2e for <feature>`).
 6. Report.
 
 ## Status protocol