ci(half-state-patrol): state the measured reason the two steps stay in the caller

The two files justified keeping `actions/setup-node` and the closed-card sweep
in the CALLING workflow with a census argument -- `check-node-version` and
`check-self-test-wired` derive their population from `.github/workflows/` and
only from there, so a step moved into the composite action would drop out and
the gate would still print OK. Both censuses read `.github/actions/**` as well
now, so the sentence is false: measured on this tree they print "2 composite
action(s)", and `collectInvocations` puts the sweep's own bytes in the
population under the composite action's name when they are presented as one.

A wrong reason on a right decision invites the change it was written to
prevent, so each bullet now carries what can be measured instead:

  - setup-node: the action holds NO Node pin of its own, and the floor it
    asserts is read from the `.nvmrc` that shipped with it. A setup-node step
    inside the composite would install the very version that floor is then
    compared against -- `check-node-version` holds every pin in this repo equal
    to that same file -- so the check could never fail and would say nothing
    about the caller's runner.
  - the closed-card sweep: the true reason was already the first half of the
    sentence (it WRITES to cards under a ruling no sibling took), so the false
    half is deleted rather than rewritten.

Comment-only. The parsed YAML of both files is byte-identical to the base, and
every one of the 56 changed lines is a comment line.

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

Author: claude

.github/actions/half-state-patrol/action.yml

@@ -47,23 +47,25 @@
 #
 # ## What deliberately did NOT move into here, and why
 #
-# Two steps stay in the CALLING workflow, both because a gate in this repo
-# derives its population from `.github/workflows/` and only from there:
+# Two steps stay in the CALLING workflow, each for its OWN reason -- and ⛔ not
+# for the census reason this block used to give. `check-node-version` and
+# `check-self-test-wired` read `.github/actions/**` as well as
+# `.github/workflows/`; their scope lines say "2 composite action(s)", so a
+# step moved in here stays audited, under this file's name, in both.
 #
-#   - `actions/setup-node`. `scripts/check-node-version.mjs` scans
-#     `.github/workflows/*.yml` and reports how many setup-node steps it
-#     audited; a step moved in here would drop out of that census and the gate
-#     would still print OK. `.github/actions/setup-pnpm` records the same
-#     reasoning for the same gate, and the same answer: callers keep their own
-#     setup-node step with its literal `node-version` pin.
-#   - the closed-card sweep. `scripts/check-self-test-wired.mjs` builds its
-#     population from the scripts a WORKFLOW names, and the only CI invocation
-#     of `scripts/pm/sweep-closed-cards.mjs --self-test` in this repo is the one
-#     in that workflow. Moved in here it would leave that gate green while
-#     auditing one script fewer. It is also the one step in the old file that
-#     was never repo-agnostic -- it WRITES to cards and was gated on the
-#     repository name -- so leaving it in the objectstack caller states plainly
-#     what the `if:` used to state obliquely.
+#   - `actions/setup-node`. This action holds NO Node pin of its own -- the
+#     floor in `Locate the patrol sources` is read from the `.nvmrc` that
+#     shipped with it, and `check-node-version.mjs` holds every setup-node pin
+#     in this repo equal to that same file. A `setup-node` step in here would
+#     install the very version that floor is then compared against: equal by
+#     construction, unable to fail, and no longer a reading about the CALLER's
+#     runner. The caller picks the Node it runs on; this action only refuses
+#     one that is too old, by name. (`setup-pnpm` keeps the same separation for
+#     NO constraint -- there the census was the whole reason, and it is gone.)
+#   - the closed-card sweep. It is the one step in the old file that was never
+#     repo-agnostic -- it WRITES to cards and was gated on the repository name
+#     -- so leaving it in the objectstack caller states plainly what the `if:`
+#     used to state obliquely.
 #
 # ## Where this runs, and against which board
 #

.github/workflows/half-state-patrol.yml

@@ -248,11 +248,11 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v7
 
-      # Stays in the caller on purpose: `scripts/check-node-version.mjs` scans
-      # `.github/workflows/*.yml` only and reports how many setup-node steps it
-      # audited, so a step moved into the composite action would drop out of
-      # that census while the gate still printed OK. `.github/actions/setup-pnpm`
-      # records the same reasoning for the same gate.
+      # Stays in the caller on purpose, and ⛔ NOT for a census reason: the Node
+      # census reads `.github/actions/**` too. The patrol action holds no Node
+      # pin of its own and only asserts a floor from the `.nvmrc` it shipped
+      # with, so the runner's Node has to be the CALLER's choice for that check
+      # to be a reading about anything. The action's header carries the measure.
       - name: Setup Node.js
         uses: actions/setup-node@v7
         with:
@@ -316,15 +316,9 @@ jobs:
         # close-time hygiene rather than the backfill the 2026-08-31 maintainer
         # ruling refused.
         #
-        # ⛔ NOT in the composite action, for two reasons that both say the same
-        # thing. It is the one step of the old file that was never
-        # repo-agnostic: it WRITES to cards under a ruling this repo's board
-        # took, and no sibling has taken it. And this workflow is the only place
-        # in CI that runs `scripts/pm/sweep-closed-cards.mjs --self-test`, which
-        # is how `scripts/check-self-test-wired.mjs` knows that self-test is
-        # run at all — that gate builds its population from `.github/workflows/`
-        # and nowhere else, so moving this step would leave it green while
-        # auditing one script fewer.
+        # ⛔ NOT in the composite action. It is the one step of the old file
+        # that was never repo-agnostic: it WRITES to cards under a ruling this
+        # repo's board took, and no sibling has taken it.
         #
         # ⛔ This step never fails the job, whatever the sweep returns; the
         # alarm rides an annotation and the run summary instead. Findings are