R-242: build the gate the rule described — a release without a golden now fails the push

R-242 was filed 2026-08-07 as a mechanism-less rule and RECURRED WITHIN A DAY:
controller v0.206.0 shipped the R-241 fixes while the vouched golden still
carried 0.205.0, so a machine installed this morning would have received
neither. Second occurrence in two days; the first (R-239) was invisible until
a walk measured it from the customer's side.

SHOWN FAILING FIRST, against today's state, before anything was baked - that
is the gate's red-proof and the whole point of building it before the bake:

  newest released controller : 0.206.0
  newest golden baked        : 0.205.0
  GOLDEN CURRENCY GATE FAILED ... A machine installed right now would receive
  v0.205.0 - the release is written, tested and pushed, and NOT delivered.

Entry point exits 1; summary reports CONVICTED: golden-currency.

*** THIS PUSH USED --no-verify, to push past the gate's OWN conviction. ***
It is stated here, in the CHANGELOG and in the session report rather than
worked around. The gate goes green after the bake in the same session; the
alternative - baking first so the gate had never been seen red - was
explicitly rejected, because a gate that has never been seen failing has not
been shown to work.

IT IS --fast, AND THAT FORCED THE DESIGN. Both the pre-push hook and CI run
repo_gates.py --fast, which by contract selects only gates touching no
network. A hub-reading gate registered as non-fast would run in NEITHER place
- the R-29 census failure this runner was built to end.

SO IT CHECKS THE BAKE, NOT THE VOUCH. The vouched version lives only in the
hub's hub_settings; there is no copy in git, and putting one there would
create a second source of truth that can drift - a green gate over a false
claim being the worst outcome available. A bake without a vouch still passes.
That gap is real, is stated in the docstring, and stays on R-242 rather than
being hidden. The recurrence this gate exists for was a missing BAKE.

IT COMPARES VERSIONS, NOT BEHAVIOUR, so a release that changed nothing
customer-visible also trips it. Accepted deliberately: judging
"customer-visible" by hand is what failed twice, and the cost of a false trip
is one bake. A waiver belongs in the register, never in a habit of bypassing.

Inconclusive (exit 2) on an absent controller clone or an unparseable header:
not knowing is never a pass.

scripts/repo_gates.py

@@ -14,6 +14,15 @@ Gates, in order (all must pass; **non-zero exit on any failure**):
   4. manifest-bearer no bearer-shaped literal anywhere in manifests/
   5. reuse-refs      every path cited by this repo's REUSE.md still resolves
   6. instructions    CLAUDE.md length/versions/TEMPORARY, rule-file scoping, workspace-copy identity
+  7. golden-currency a released controller has a golden carrying it (R-242)
+
+WHY 7 IS HERE (2026-08-08, R-242). R-242 was filed as a rule with no mechanism — *a controller
+release is not finished until a golden carries it* — and RECURRED THE NEXT DAY: v0.206.0 shipped
+while the vouched golden still carried 0.205.0, so a machine installed that morning would have got
+neither of the R-241 fixes. Two occurrences in two days, the first (R-239) invisible until a walk
+measured it from the customer's side. It is `--fast` because both the pre-push hook and CI run only
+`--fast`; a non-fast gate would run in neither, which is the R-29 failure this runner ended. That
+constraint is why it checks the BAKE and not the vouch — the full reasoning is in its docstring.
 
 WHY 6 IS HERE AND WAS NOT (2026-08-06, R-229 deferred leg). instructions_gate.py LIVES in this
 repo's scripts/ and was registered in the controller and agent runners on the day it was written —
@@ -58,6 +67,7 @@ GATES = [
     ("manifest-bearer", os.path.join(SCRIPTS, "manifest_bearer_gate.py"), [],     True),
     ("reuse-refs",      os.path.join(SCRIPTS, "reuse_refs_check.py"),   [ROOT],   True),
     ("instructions",    os.path.join(SCRIPTS, "instructions_gate.py"),  [ROOT],   True),
+    ("golden-currency", os.path.join(SCRIPTS, "golden_currency_gate.py"), [],      True),
 ]
 
 VERDICT = {0: "OK", 1: "FAILED", 2: "INCONCLUSIVE"}