mind: dashboard refresh on batches/**; dev batch stays collected-once, reviewed-once (#341)

.github/workflows/dashboard_refresh.yml

@@ -2,8 +2,9 @@ name: Dashboard Refresh
 
 # Keeps the generated task page (`dashboard.md`, linked from the README) in
 # step with the Mind it describes. The page is rendered by PyAutoBrain's intake
-# conductor from `draft/`, `active/` and the registry files, so any push that
-# files, issues, parks or ships a task makes it stale.
+# conductor from `draft/`, `active/`, `batches/` and the registry files, so any
+# push that files, issues, parks or ships a task — or opens, collects or
+# reviews a batch, which the page's status box shows — makes it stale.
 #
 # It went stale before this workflow existed: between its first commit and
 # 2026-08-11 the page was regenerated by hand 4 times while 33 commits touched
@@ -31,6 +32,7 @@ on:
     paths:
       - "draft/**"
       - "active/**"
+      - "batches/**"
       - "active.md"
       - "parked.md"
       - "planned.md"
@@ -45,6 +47,7 @@ on:
     paths:
       - "draft/**"
       - "active/**"
+      - "batches/**"
       - "active.md"
       - "parked.md"
       - "planned.md"

batches/AGENTS.md

@@ -9,6 +9,15 @@ It auto-merges (`scripts/ledger_merge.py` — `batches/` is a ledger dir), becau
 an unattended system that cannot record its own history unattended will not
 record it.
 
+**Collected once, reviewed once.** A dev batch is dispatched as one shift and
+reviewed as one sitting: one `- review:` line, one review file. The dashboard's
+batch status box is the live view of the open slot — every member with what it
+is doing — and it offers the button to the review packet once `collected:` is
+stamped, because there is nothing to review before that. A science batch is a
+rolling board instead, ruled on more than once and closing only when nothing is
+left on the board (`PyAutoCortex/batches/AGENTS.md`, "A rolling board, not a
+dispatch"); that difference is the Cortex's, not a change here.
+
 ## Schema
 
 ```markdown