Say the page's freshness is not yet checked (issue 1222), and fix 08's leftover 'reviewed after its push' (review round 1)

00-META/process/08-small-fixes.md

@@ -99,7 +99,7 @@ reading itself and uses one subagent only for the review.
 ## How it is checked
 
 - A small fix has one pull request with one or few commits naming its issue, opened after its review: a pull
-  request with many heads is a fix reviewed after its push.
+  request with many heads is a fix reviewed after its pull request was opened.
 - Its issue moves to `resolved` within the hour its delivery plan ends.
 - A pull request with no review record at its head (the Approve's ask says so first), a fix to a module's
   running pushed with no integration test of the module whole, or a review report

00-META/process/playbooks.html

@@ -409,7 +409,7 @@ code{font:12.5px ui-monospace,monospace;background:var(--soft);padding:1px 5px;b
 <div id="filters" style="display:flex;flex-wrap:wrap;gap:8px;margin-bottom:12px"></div>
 <div class="grid" id="cards"></div>
 
-<footer>Drawn from hq main f269e83 on 2026-10-19 and kept in hq beside the playbooks. The playbooks are the authority; this page is a picture of them, and a change to a playbook's steps updates it in the same pull request.</footer>
+<footer>Drawn from hq main f269e83 on 2026-10-19 and kept in hq beside the playbooks. The playbooks are the authority; this page is a picture of them, and a change to a playbook's steps updates it in the same pull request (not yet checked: issue 1222).</footer>
 </main>
 
 <script>
@@ -476,7 +476,7 @@ const P = [
   steps:["Read the issue and the code; settle any open question.","Write the acceptance criteria.","Move the issue to fixing.","Build on fix/<issue>-<slug> in its own worktree.","A test that fails today first, on behaviour. (new)","Push and try before the review. (new)","One review of the commit and its try.","Push the reviewed head; open the pull request.","The operator's Approve; the merge; the delivery plan.","Prove the fix live and resolve the same hour."],
   prod:"One pull request, one delivery, a resolved issue.",
   next:"—",bounds:"About an hour · one try before the review, one review, one check",
-  prev:["A fix reviewed after its push","A long part run twice","A fix waiting on someone else's delivery"],
+  prev:["A fix reviewed after its pull request opened","A long part run twice","A fix waiting on someone else's delivery"],
   check:"The forge's checks; the review record; the tracker's move."},
  {n:"09",name:"Cleanup",kind:"side",c:"--side",
   trig:"The operator asks, or merged branches, stale pull requests and old worktrees pile up.",

AGENTS.md

@@ -57,7 +57,8 @@ in running prose; a quotation keeps its words.
 - **Markdown only** — but for the checks in `00-META/checks/` and `merge-check.sh` at the root, which
   runs them on every pull request as its `mesh/repo-check` (ADR 0238), and
   `00-META/process/playbooks.html`, a drawn overview of the playbooks kept for a later docs site (the operator,
-  2026-10-19); a change to a playbook's steps updates it in the same pull request.
+  2026-10-19); a change to a playbook's steps updates it in the same pull request. Nothing checks that
+  yet: issue 1222 asks for the check.
   No new top-level folders without explicit confirmation.
 - **Status lives in YAML frontmatter** — on design docs (`layer`, `status`, `code`, `updated`,
   and `decisions` as "ADR NNNN"). A decision record's and a research effort's status live in the knowledge