docs: reconcile stale deployed-vs-verifier status + fix dead link

MINER_VALIDATOR.md

@@ -3,7 +3,7 @@
 SN39 (Cathedral) rewards **two lanes of verified work**, composed into one weight vector
 each tempo — **70% Intel-TDX compute** / **30% CyberGym vulnerability solving**, with any
 unfilled share burned. This page is the whole mental model. The deeper contracts are in
-[VALIDATOR.md](VALIDATOR.md), [deploy/MECHANISM_ROUTER_CONTRACT.md](deploy/MECHANISM_ROUTER_CONTRACT.md),
+[VALIDATOR.md](VALIDATOR.md), [BOUNDARY.md](BOUNDARY.md),
 and the reward-path docs.
 
 ## A miner

VALIDATOR.md

@@ -30,13 +30,15 @@ UID-aligned Bittensor weight decision. It supports two concurrent paths:
 | Validator thin-path checks | Implemented |
 | Concurrent shadow provenance audit | Implemented; default mode |
 | Full-provenance authority mode | Deprecated; no shipped config profile selects it (removal tracked in #40) |
-| Current deployed vector vs independent verifier | `FAIL`: public v1/GPU-allocation contract does not match the v2/fixed-burn/body-binding verifier |
+| Current deployed vector vs independent verifier | Re-derive before relying on it — this status moves with each deploy. An earlier release recorded `FAIL` (public v1/GPU-allocation shape vs the v2/fixed-burn/body-binding verifier); the 2026-07-28 redeploy converged production and `cathedral-compute`'s `BUILD_STATUS.md` reported `AGREE` (2026-08-07). Confirm against the live signed vector before broadcasting. |
 | General validator launch | Pending a scoreable corpus and final acceptance |
 
-The current public contract mismatch is a launch blocker. Shadow mode reports
-it but does not veto an otherwise valid thin vector, which is why operators
-must remain in non-writing preview modes until the supported release
-converges.
+Any residual public-contract mismatch is a launch blocker, and shadow mode
+reports it but does not veto an otherwise valid thin vector — so confirm the
+live signed vector reproduces against the pinned verifier before broadcasting,
+and stay in non-writing preview until it does. Do not rely on a static verdict
+here or in `BUILD_STATUS.md`; both are dated and must be re-derived against the
+live vector.
 
 ## What happens on each tick
 

docs/VIOLET_EXTERNAL_SCORES.md

@@ -90,7 +90,8 @@ CATHEDRAL_EXTERNAL_SCORES_TOKEN_CATHEDRAL_CONFIDENTIAL_TDX=<secret>  # Per-sourc
 **Validator policy pin (`confidential_primary_v1`):** operators who run confidential-primary can pin the thin validator so it applies ONLY this contract:
 
 ```bash
-# CLI flag or env; default is unpinned (accepts legacy, v3, and confidential_primary)
+# CLI flag or env. The default PINS validated_supply_v1 (cli.py), which rejects a
+# plain confidential_primary/v3 vector — set this explicitly to accept confidential_primary.
 cathedral-validator serve --require-policy confidential_primary_v1
 export CATHEDRAL_VALIDATOR_REQUIRE_POLICY=confidential_primary_v1
 ```