docs(ci): rest the direct-node invocation on precedent, not on an over-broad #9465 fence

The `Step-collector gate` step comment and the script docblock both claimed
root `package.json` is "declared territory of the @changesets/cli v3 migration
lane (#9465)". That reading is over-broad. The fence's own text scopes it to
that file's `@changesets/cli` range and its `version` script -- the
parenthetical in the issue body is scoping, not illustrative -- so the file
itself is not fenced and a `check:step-collectors` key would have been allowed.

The decision is unchanged and still correct: lint.yml already invokes several
gates as `node scripts/...` directly, and dispatch-gates.mjs derives gate
families from either spelling, so the direct form loses no discovery and adds
no key to the root manifest. Only the stated REASON was wrong.

Worth more than a silent reword, because it is this PR's own defect class one
level up: a comment asserting a constraint nobody verified reads exactly like
a verified one, and propagates to the next agent who reads it -- the same way
a stale knownGap turns into a stale permission. So the accurate scope is now
stated positively next to the decision rather than merely deleted.

Only the two comments I authored are touched; the seven pre-existing instances
of the same phrasing elsewhere in lint.yml are left alone as out of scope.

Part of #10814

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DdCnBGcHeufjrq7drTD3wt

Author: claude

.github/workflows/lint.yml

@@ -653,11 +653,20 @@ jobs:
       # commands executing when the first fails, 3 of 3 when none does. A harness
       # that cannot reproduce the defect cannot certify the fix.
       #
-      # Invoked as `node` rather than through a `pnpm check:*` alias: that alias
-      # belongs in root package.json, declared territory of the @changesets/cli
-      # v3 migration lane (#9465) while it runs — same shape as the other
-      # `node scripts/…` steps in this lane. dispatch-gates.mjs derives gate
-      # families from either spelling. Temp-dir fixtures, no network, ~1 s.
+      # Invoked as `node scripts/…` rather than through a `pnpm check:*` alias,
+      # on the precedent this job already sets: several gate steps here are
+      # invoked directly, and dispatch-gates.mjs derives gate families from
+      # either spelling, so the direct form loses no discovery and adds no key
+      # to the root manifest.
+      #
+      # ⚠️ NOT because root package.json is off limits. The #9465 changeset lane
+      # fences that file's `@changesets/cli` range and its `version` script — the
+      # parenthetical in the issue body is scoping, not illustrative — and not
+      # the file, so a `check:step-collectors` key would have been allowed. Said
+      # plainly because the over-broad reading is easy to acquire and then
+      # propagates as a constraint nobody actually has, which is this step's own
+      # defect class wearing a different hat: a claim that reads as verified.
+      # Temp-dir fixtures, no network, ~1 s.
       - name: Step-collector gate (self-tests that mask each other)
         run: |
           node scripts/check-step-collectors.mjs --self-test

scripts/check-step-collectors.mjs

@@ -85,11 +85,16 @@
  * when none does. A harness that cannot reproduce the defect cannot certify the
  * fix.
  *
- * Invoked as `node` rather than through a `pnpm check:*` alias: that alias
- * belongs in root package.json, which is declared territory of the
- * @changesets/cli v3 migration lane (#9465) while it runs -- the same shape as
- * the other `node scripts/...` steps in that lane. dispatch-gates.mjs derives
- * gate families from either spelling.
+ * Invoked as `node scripts/...` rather than through a `pnpm check:*` alias, on
+ * the precedent lint.yml already sets: several gate steps in that job are
+ * invoked directly, and dispatch-gates.mjs derives gate families from either
+ * spelling, so the direct form loses no discovery and adds no key to the root
+ * manifest.
+ *
+ * NOT because root package.json is off limits: the #9465 changeset lane fences
+ * that file's `@changesets/cli` range and its `version` script, not the file,
+ * so a `check:step-collectors` key would have been allowed. Recorded because
+ * the over-broad reading of that fence propagates as a constraint nobody has.
  */
 
 import { existsSync, mkdirSync, mkdtempSync, readFileSync, readdirSync, rmSync, writeFileSync } from 'node:fs';