@@ -255,7 +255,7 @@ jobs:
           restore-keys: |
             ${{ runner.os }}-pnpm-store-v3-
 
-      # Restore-only, like ci.yml's Console Pin Gate: this workflow runs a handful
+      # Restore-only, as ci.yml's retired Console Pin Gate was: this workflow runs a handful
       # of times a month so its own namespace is almost always cold, and the
       # build-core fallbacks seeded from main are the ones that actually hit.
       # Saving is lint.yml's job.
 
@@ -57,10 +57,9 @@ on:
     # snapshot owns :07 of 02, 08, 14 and 20. Of the six six-hour sets, only
     # 0/6/12/18 and 1/7/13/19 have hours with nothing scheduled after :00; the
     # first is taken because its :00 neighbours are short (release.yml's
-    # version-pr refresh, prerelease-pin-watch at 06:00, the hourly ci/lint
-    # runs), while 07:00 starts the showcase smoke. The MINUTE is off the top of
-    # the hour for the reason every patrol here gives: scheduled runs queue
-    # behind everyone else's :00 cron.
+    # version-pr refresh, the hourly ci/lint runs), while 07:00 starts the
+    # showcase smoke. The MINUTE is off the top of the hour for the reason every
+    # patrol here gives: scheduled runs queue behind everyone else's :00 cron.
     #
     # This job spends almost nothing of the per-repository GITHUB_TOKEN budget
     # (the checkout, and no API reads), so unlike the board readers it is not
 
@@ -3261,7 +3261,7 @@ jobs:
       # from git: 17.1.0 ran 5h44m (36 PRs landed), 16.1.0 ran 25 days (2712 PRs).
       # Hard-failing would have red 2748 PRs for a debt none of them created. So
       # findings are a `::warning::` + step summary with the job GREEN — the
-      # loud-but-non-blocking shape prerelease-pin-watch.yml uses — and the policy
+      # loud-but-non-blocking shape the retired prerelease-pin-watch.yml used — and the policy
       # follows half-state-patrol.yml's rule verbatim: findings never fail
       # anything, the job DOES fail when the sweep could not run. A broken
       # instrument is fatal here in every mode. `--strict` promotes findings to
@@ -4727,7 +4727,7 @@ jobs:
       # the legacy `##[...]` form is parsed ANYWHERE in a printed line (the
       # measured token sat at column 18 and was still consumed), while the
       # `::...::` form is parsed only at LINE START (two mid-sentence ones print
-      # on every PR from `check-prerelease-pin-watch` and mint nothing). So the
+      # on every PR from the since-retired `check-prerelease-pin-watch` and minted nothing). So the
       # first detector is unanchored and the second is anchored — flagging inert
       # prose would be a false positive the next author would be right to delete.
       #
 
@@ -63,7 +63,7 @@ name: Release-Coverage Patrol
 # grepping prose, while the JOB stays green whenever findings exist. A `--strict`
 # run stays red for as long as the prose is unwritten — 25 days, in the 16.1.0
 # case — and a chronically red scheduled job is how people learn to skim red,
-# which `prerelease-pin-watch.yml`'s header warns about directly. Findings land
+# which the retired `prerelease-pin-watch.yml`'s header warned about directly. Findings land
 # in the anchor issue; they never colour this job.
 #
 # ## What lands where
 
@@ -1506,8 +1506,8 @@ jobs:
   # ══════════════════════════════════════════════════════════════════════════
   full-battery:
     name: Full battery green at the version commit
-    # A PR or queue build carries ci.yml's FAST SET since #22998; the dogfood,
-    # temporal and console-pin legs run only on main's push, hourly and
+    # A PR or queue build carries ci.yml's FAST SET since #22998; the dogfood
+    # and temporal legs run only on main's push, hourly and
     # dispatch runs. So "tested before a release" is read HERE, as a gate: the
     # newest completed `schedule` or `push` runs of `CI` and `Lint & Type
     # Check` whose head is the version commit or a first-parent ancestor of it
Original file line number	Diff line number	Diff line change
`@@ -63,7 +63,7 @@ name: Release-Coverage Patrol`
`63`	`63`	# grepping prose, while the JOB stays green whenever findings exist. A `--strict`
`64`	`64`	`# run stays red for as long as the prose is unwritten — 25 days, in the 16.1.0`
`65`	`65`	`# case — and a chronically red scheduled job is how people learn to skim red,`
`66`		-# which `prerelease-pin-watch.yml`'s header warns about directly. Findings land
	`66`	+# which the retired `prerelease-pin-watch.yml`'s header warned about directly. Findings land
`67`	`67`	`# in the anchor issue; they never colour this job.`
`68`	`68`	`#`
`69`	`69`	`# ## What lands where`