@@ -355,7 +355,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
 
@@ -3286,7 +3286,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
@@ -4752,7 +4752,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
 
@@ -530,7 +530,7 @@ Even inside your own worktree, operate defensively:
    check-run name, so a rename detaches its gate silently — treat those five names as contract.
    **Two speeds** (ruling record 6120820653): PR and queue runs carry the fast set, 10 minutes of
    wall per queue entry; `main`'s hourly and push runs carry the full battery — dogfood, e2e,
-   `Console Pin Gate`, `Temporal Conformance (live PG + MySQL)` — read by the publish lane before
+   `Temporal Conformance (live PG + MySQL)` — read by the publish lane before
    any approval. **Main-red:** a full-battery red is its lane's first work — triage files it under
    the main-red convention, the lane's next PR fixes it, and ⛔ no lane PR arms the queue meanwhile.
 
@@ -1100,8 +1100,8 @@ Both non-handshake shapes, and how to classify and probe your own:
    (`pnpm check:adr-0087-registration` reads the arm and the kind there). ⛔ The categories are NOT copied here —
    the gate prints the full set when it fails.
 4. **A removal that breaks the pinned sibling checkout ships together with the sibling fix and the pin bump — or it
-   does not ship.** The full battery's `Console Pin Gate` builds objectui at the pinned `.objectui-sha` against
-   **current** `main`, so such a removal is a main-red the moment it merges; its ruling therefore authorizes the
+   does not ship.** `Type Check UI` compiles the Console under `ui/` against the spec of the PR that makes such a
+   removal, so the removal reds its own PR; its ruling therefore authorizes the
    objectui-side fix and the pin bump (manifest regeneration included — see the Frontend section) in the same
    landing. Before merging, `git grep` what you remove or rename in `../objectui` at the pinned SHA.
 5. **Touched `packages/spec`? Regenerate and commit its artifacts before pushing** — § *Touched `packages/spec`*
 
@@ -270,10 +270,11 @@ path. The 2026-08-20 ruling removed it (#10134): the workflow, the script and th
 *everything shipped is covered by the changeset record* — is delivered by step 3
 above, at bump time, which is where the decision is actually taken.
 
-**What still checks the pin, and what it checks.** `ci.yml`'s **Console Pin Gate**
-(#4290) clones objectui at the pin and builds the SPA, so it proves the pinned SHA
-still **builds**. It has never had an opinion about whether the pin is current, and
-that is now the only question anyone asks about the pin automatically.
+**What used to check the pin.** `ci.yml`'s **Console Pin Gate** (#4290) cloned
+objectui at the pin and built the SPA, so it proved the pinned SHA still
+**built**; it never had an opinion about whether the pin was current. It retired
+with the objectui import (#25697): `Type Check UI` and `Build & E2E UI` in
+`ci.yml` build the Console from `ui/` in the pull request that changes it.
 
 ## Rehearsing the version pass (throwaway clone)
 
@@ -472,7 +473,7 @@ is changed by where the refresh came from.
 **Then, before approving, check that no nearer `CI` run is still in flight** (#24889).
 Open the Release run's **`Full battery green at the version commit`** job, step *Read
 the full battery at or before the version commit*. It prints one line per workflow it
-reads (`CI`, `Lint & Type Check`, `Spec Shape Gate`), each naming the run it chose and
+reads (`CI`, `Lint & Type Check`), each naming the run it chose and
 how many first-parent commits before the version commit that run's head sits. The
 gate reads only *completed* runs and never waits (by design: `selectFullBatteryRun`
 in `scripts/ci/scheduled-full-run.mjs`), so a run still in progress is invisible to
 
@@ -75,11 +75,11 @@
 // whichever PR happens to run CI next". An uncovered minor is a fact about the
 // release history, not about whichever PR runs CI next. Same shape, same answer.
 //
-// Loud-but-non-blocking is `prerelease-pin-watch.yml`'s mechanism, reused here:
+// Loud-but-non-blocking was `prerelease-pin-watch.yml`'s mechanism (retired, #25697), reused here:
 // a `::warning::` annotation plus a step-summary table, job GREEN. `--strict`
 // promotes findings to exit 1 for a caller that OWNS the remedy (a standing
 // patrol, or someone editing the release pages) — the same escape hatch that
-// workflow's own `--strict` provides.
+// workflow's own `--strict` provided.
 //
 // ## What IS fatal: the instrument
 //
@@ -1184,7 +1184,7 @@ function renderOk(checked, minorCount) {
 }
 
 /**
- * Loud-but-non-blocking, the `prerelease-pin-watch.yml` mechanism: a `::warning::`
+ * Loud-but-non-blocking, the retired `prerelease-pin-watch.yml` mechanism: a `::warning::`
  * annotation plus a step-summary table, job GREEN. Silent outside Actions.
  *
  * @param {string[]} findings
 
@@ -334,6 +334,11 @@ const UNATTRIBUTED_BATTERY = '(no battery open)';
  * is right. Budgeting around it would only arm the trap for the next author
  * who legitimately names the live job.
  *
+ * `Console Pin Gate` IS dead since #25697 deleted its job with the objectui pin
+ * gates. It still takes no RETIRED_CONTEXT_NAMES row: it never sat in any
+ * reading of the required set, and the instruction files no longer name it as
+ * a live check (`docs/releases-maintenance.md` keeps it in the past tense).
+ *
  * ⚠️ The cost of the drop, stated rather than discovered later: these two
  * `name:` literals are now pinned by NOTHING, while prose elsewhere still refers
  * to the jobs by name — `docs/releases-maintenance.md`,
 
@@ -35,11 +35,11 @@
  * safe by indenting it or by burying it in prose.
  *
  * **2. The `::...::` form is parsed only at LINE START.** Measured against the
- * same population: `scripts/check-prerelease-pin-watch.mjs --self-test` prints
- * two lines carrying `::error::` and `::warning::` mid-sentence on every PR,
- * and its check run carries zero annotations. Those two lines are inert where
- * they sit and one re-indentation away from not being; this gate reddens at the
- * moment they move, which is the moment they start lying.
+ * same population: `scripts/check-prerelease-pin-watch.mjs --self-test` (since
+ * retired, #25697) printed two lines carrying `::error::` and `::warning::`
+ * mid-sentence on every PR, and its check run carried zero annotations. Such a
+ * line is inert where it sits and one re-indentation away from not being; this
+ * gate reddens at the moment one moves, which is the moment it starts lying.
  *
  * ⚠️ Neither fact is inferable from a local run — the transformation happens on
  * a runner and nowhere else. That is exactly why the property needs a gate
 
@@ -62,10 +62,11 @@
 //     written, true now, true after 1.9.0. Forcing them to the pin would
 //     fabricate that many measurements. (Those figures are a dated reading, not
 //     a live one: run `--census` for today's.)
-//   - Some sites are not attestations at all. It is SELF-TEST FIXTURE DATA
-//     inside `check-prerelease-pin-watch.mjs` — a synthetic npm registry payload
-//     whose `1.7.1` is an arbitrary input proving the watcher notices a stable
-//     release. A pin-equality sweep would corrupt a gate's own test input.
+//   - Some sites are not attestations at all. One was SELF-TEST FIXTURE DATA
+//     inside `check-prerelease-pin-watch.mjs` (since retired) — a synthetic
+//     npm registry payload whose `1.7.1` was an arbitrary input proving the
+//     watcher noticed a stable release. A pin-equality sweep would corrupt a
+//     gate's own test input.
 //
 // So the rule is about PHRASING, not about version equality:
 //
@@ -376,8 +377,8 @@ export const ANCHOR_PATTERN = /\b20\d\d-\d\d-\d\d\b|#\d{3,6}\b/;
  * Gate self-tests build fake registry payloads and fake prose to drive their own
  * assertions; those numbers are arbitrary test data, and holding them to the
  * resolved pin would corrupt another gate's fixture. #13940 measured one such
- * site inside `check-prerelease-pin-watch.mjs` — its `1.7.1` proves the watcher
- * notices a stable release and means nothing about this tree.
+ * site inside `check-prerelease-pin-watch.mjs` (since retired) — its `1.7.1`
+ * proved the watcher noticed a stable release and meant nothing about this tree.
  *
  * It is an INLINE declaration rather than a central exemption list on purpose: a
  * central list rots away from the thing it describes, while this sits on the
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`