docs(adr): correct ADR-0082 addendum 2's carrier census for the sdui:manifest reminder (#10718)

The 2026-08-07 addendum's "Where the line lives" list named two carriers in
docs/releases-maintenance.md: the pin-bump procedure and the pin-freshness
"fix when it fires" step. The Console Pin Freshness gate is gone -- workflow,
script, package.json entry and the release.yml publish-path step -- and with it
that second carrier, so the enumeration pointed a reader at a step that no
longer exists.

The substance is unchanged: docs/releases-maintenance.md still carries the
reminder as prose in the pin-bump procedure. Only the enumeration is corrected;
the addendum's structure, Decision 4's mechanism and the on-demand-gate verdict
all stand exactly as ruled.


Claude-Session: https://claude.ai/code/session_01DdCnBGcHeufjrq7drTD3wt

Co-authored-by: Claude <noreply@anthropic.com>

Author: claude[bot]

docs/adr/0082-react-component-contract-governance.md

@@ -164,6 +164,6 @@ This is Prime Directive #10 (declared ≠ enforced) landing on a gate — the sa
 
 - `scripts/bump-objectui.sh` prints it as a NEXT STEP on every successful bump, including `--no-commit`. A **reminder, not a hard gate** — a machine without Playwright must still be able to move the pin, and hard-failing there would be CI-side cost wearing a local disguise.
 - `scripts/build-console.sh` closes with it too, because `pnpm objectui:refresh` runs bump-then-build and that output is the last thing an operator sees.
-- `docs/releases-maintenance.md` carries it as prose, in the pin-bump procedure and in the pin-freshness "fix when it fires" step.
+- `docs/releases-maintenance.md` carries it as prose, in the pin-bump procedure — the pin-freshness "fix when it fires" step that used to carry it too went with the `Console Pin Freshness` gate itself (#10134).
 
 **What is unchanged.** Decision 4's mechanism and its "not every PR" verdict both stand, and this addendum records no reversal — it names the producer correctly and supplies the trigger the decision left blank.