chore(merge-driver,dispatch-gates): record gen:checklist-status's disposition and classify its battery

Two ledgers the new generator and its self-test battery owe a row in, each
found by its own gate rather than by inspection:

- `scripts/regen-artifacts.mjs`: `gen:checklist-status` writes NOTHING into
  this repository, so 'discard both sides and re-run the generator' is not a
  question that arises. Recorded as NOT_DRIVER_MANAGED with `untracked: true`
  rather than omitted, because the refused alternative — a committed STATUS.md
  paired with a check — is exactly the routed-artifact shape a reader assumes.
  Owner is the ROOT manifest: the accounting is keyed per (owner, script).

- `scripts/pm/dispatch-gates.mjs`: `selfTestPlannedStatus` is a genuine
  battery, so its fixtures SHOULD be masked away from watch-hint extraction.
  The docblock's TOTAL / GENUINE / distinct-spelling counts are pinned against
  the table and move with the row. Its two UNPINNED neighbours (the corpus
  totals) were already stale on origin/main at 253/223 against a measured
  273/243; restated to the freshly measured 275/244 so the paragraph's own
  arithmetic (244 + 31 = 275) stays true rather than being broken by this row.

Claude-Session: https://claude.ai/code/session_01AmH9bKvGoLjiY86Q4Z3og2
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

scripts/pm/dispatch-gates.mjs

@@ -5211,9 +5211,9 @@ const BARE_ENTRY_POINT_NAME = 'selfTest';
  *
  * ## The census, re-derived on this tree
  *
- * 253 code-position matches over the tracked JS/TS corpus. 223 are the bare
- * `selfTest`; the remaining 30 carry compound names over 27 distinct spellings,
- * and they are the rows below. Nineteen are genuine self-test batteries — the
+ * 275 code-position matches over the tracked JS/TS corpus. 244 are the bare
+ * `selfTest`; the remaining 31 carry compound names over 28 distinct spellings,
+ * and they are the rows below. Twenty are genuine self-test batteries — the
  * anchor firing on them is the anchor working. ELEVEN are production code:
  *
  *   scripts/check-self-test-wired.mjs             carriesSelfTest
@@ -5240,7 +5240,7 @@ const BARE_ENTRY_POINT_NAME = 'selfTest';
  * and it is exactly the kind of claim that stops being true without anything
  * going red, which is what the pin in this module's self-test exists to catch.
  *
- * The same measurement, redone over the table's current nineteen genuine rows,
+ * The same measurement, redone over the table's current twenty genuine rows,
  * is still NOT zero, and that asymmetry is what makes the classification
  * load-bearing rather than decorative: `fixtureSelfTest` drops
  * `packages/spec/spec-changes.json` and `prePushIsArmedSelfTest` drops
@@ -5269,8 +5269,8 @@ const BARE_ENTRY_POINT_NAME = 'selfTest';
  *     wider — and it would make the tool's self-scan differ from every other
  *     scan, which is a hazard of its own.
  *
- * ⇒ What ships is neither. The anchor keeps firing on all 30, the mask keeps
- * blanking all 30, and the cost of the eleven accidental ones is MEASURED on
+ * ⇒ What ships is neither. The anchor keeps firing on all 31, the mask keeps
+ * blanking all 31, and the cost of the eleven accidental ones is MEASURED on
  * every run instead of asserted in prose. Silence was the defect; the remedy is
  * noise on the day it starts costing something.
  *
@@ -5306,6 +5306,7 @@ const COMPOUND_ANCHOR_LEDGER = [
   ['scripts/check-platform-checklist.mjs', 'selfTestMetaCallSpelling', false],
   ['scripts/check-platform-checklist.mjs', 'selfTestLineCitationBinding', false],
   ['scripts/check-platform-checklist.mjs', 'selfTestSymbolAnchors', false],
+  ['scripts/check-platform-checklist.mjs', 'selfTestPlannedStatus', false],
   ['scripts/check-regen-pending.mjs', 'fixtureSelfTest', false],
   ['scripts/check-regen-pending.mjs', 'prePushIsArmedSelfTest', false],
   ['scripts/check-regen-pending.mjs', 'decisionTableSelfTest', false],

scripts/regen-artifacts.mjs

@@ -855,6 +855,33 @@ export const NOT_DRIVER_MANAGED = Object.freeze([
       + 'ledger — recorded so that "no disposition" is not confused with "not yet decided". Same '
       + 'expiry clause as the entry above: committing it turns this entry red.',
   },
+  {
+    // ⚠️ NOT a directory of this repository, and by ruling never one. The
+    // generator's `--out <dir>` is a runner tempdir whose contents are pushed
+    // to the repository WIKI — a separate git repo that this driver, this
+    // ledger and the merge queue all sit outside of.
+    path: 'wiki/**',
+    gen: 'gen:checklist-status',
+    // The ROOT manifest defines this script, not `packages/spec` — and the
+    // accounting is keyed per (owner, script), so leaving this to the default
+    // owner records the disposition against a manifest that has no such script
+    // and leaves the real one unaccounted. Both halves red at once, which is
+    // the two-way reconciliation working.
+    owner: ROOT_OWNER,
+    untracked: true,
+    why:
+      'writes NOTHING into this repository. `gen:checklist-status` prints the per-area '
+      + 'active/planned census to stdout and, with `--out <dir>`, renders the wiki page set into '
+      + 'that directory; `.github/workflows/checklist-status.yml` publishes it to the repository '
+      + 'wiki on a schedule. So "discard both sides and re-run the generator" is not a question '
+      + 'that arises — git never merges these pages, and the wiki is regenerated wholesale every '
+      + 'run. Recorded rather than omitted because the ALTERNATIVE was considered and REFUSED on '
+      + 'the card: a `STATUS.md` committed to `docs/qa/platform-checklist/` paired with a '
+      + '`check:checklist-status` gate, which is exactly the routed-artifact shape this ledger is '
+      + 'full of, and which a reader may well assume happened here. Same expiry clause as the two '
+      + 'entries above: the day any of these pages is committed to this tree, this entry turns red '
+      + 'and a real disposition is owed.',
+  },
   {
     path: 'docs/audits/**',
     why: