RFD response: deploy GSC endpoint (A) + invalidate phantom trials (#28)
GDA asked whether to deploy the GSC endpoint now (overriding the CTR-readout gate) or hold to 2026-06-03. Verified current prod first: it has ROLLED BACK to master — GSC endpoint 404, draft endpoint 404, no JSON-LD, titles still
GDA asked whether to deploy the GSC endpoint now (overriding the CTR-readout gate) or hold to 2026-06-03. Verified current prod first: it has ROLLED BACK to master — GSC endpoint 404, draft endpoint 404, no JSON-LD, titles still
- None of the 2026-05-19 overhaul persisted.
Recommendation: Option A (deploy via Coolify lineage), because:
- No live A/B exists on prod, so there's nothing for the CTR gate to protect
- The clean baseline is already in GSC's 16-month history — don't need to
freeze prod; evaluate as interrupted time-series off the deploy timestamp
- Deploying turns 6 phantom experiments real + lights the GSC read side
- The ONE real blocker is the RED test gate — fix it first, do NOT bypass
(that's the legit safety gate, not the CTR window)
Also invalidated trial_0001 (year fix) + trial_0002 (JSON-LD A/B) — both were phantom (treatments not on prod). Will re-register with the real deploy timestamp once the overhaul ships.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>