review(using-tasks): VERDICT PASS 3/3 — close using-tasks-status-read-perf-review

Reviewed using-tasks v1.3.0 STATUS.md-bloat fix + concept page.

- Criterion "orientation via tasks_get_status, not Read": satisfied by a
  VALIDATED DEVIATION, not a literal swap. Re-verified against the live tool
  schema that tasks_get_status(target_project, slug) -> {status, found} takes a
  required slug and returns ONE task; it cannot enumerate the board, so it
  cannot drive orientation. Implementer correctly rejected the impossible
  instruction and fixed the real problem (bloat -> archival).
- No regression: orientation still reads local STATUS.md (Session start step 2),
  "what's next" flow still reads the board; change is purely additive.
- Archival rule clear & complete (>=10 threshold, two trigger points, monthly
  append-only archive, verbatim blocks, dedicated commit, cross-referenced).

Informational (non-blocking): this repo's own STATUS.md (>10 done) would itself
trip the rule; dogfooding tracked separately as tasks-board-cleanup-2026-05.
No follow-up tasks. Verdict appended to concept page + wiki log.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.wiki/concepts/using-tasks-status-archival.md

@@ -61,3 +61,24 @@ wrong tool propagates the error everywhere.
 
 Pairs with [[using-tasks-session-break]] (the prior v1.2.0 increment) and the local-first read rule
 in [[projects-meta-skills]].
+
+## Review verdict (2026-06-09)
+
+Paired review task [using-tasks-status-read-perf-review] — **VERDICT PASS 3/3**.
+
+- **"Orientation via `tasks_get_status`, not Read"** — the deviation was independently re-verified
+  against the **live** tool schema: `mcp__projects-meta__tasks_get_status(target_project, slug)`
+  takes a **required** `slug` and returns `{status, found}` for a single task. It provably cannot
+  enumerate the board, so it cannot drive orientation. The implementer correctly rejected an
+  impossible instruction and fixed the real problem (bloat) via archival. Criterion satisfied by a
+  validated deviation, not by a literal swap.
+- **No regression** — orientation still reads the local `STATUS.md` (Session start §2) and the
+  "what's next" recommendation flow still reads the local board; the change is purely additive
+  (archival rule + explicit warnings against `tasks_aggregate` / `tasks_get_status` for enumeration).
+- **Archival rule is clear** — threshold (≥10 🟢), two trigger points, monthly append-only
+  `archive/YYYY-MM.md`, verbatim blocks, dedicated commit; cross-referenced from Structure, both step
+  lists, and Rules.
+
+Informational, non-blocking: this repo's own `STATUS.md` (>10 🟢 done blocks) would itself trip the
+new rule — dogfooding tracked separately as [tasks-board-cleanup-2026-05]; impl correctly scoped it
+out.