doing · High priority

VRC.LOL PostgreSQL Compatibility and Migration

96% through the measured PostgreSQL compatibility gates. Live accounts and sessions, viewer presence, public chat, published podcast reads, podcast administration, recording imports and private recording-path resolution already use least-privilege loopback Go/PostgreSQL services with tested rollback boundaries. Twenty fresh vrc_roadmap imports pass exact reconciliation and typed reads across 5 columns, 186 public cards, 295 links, 202 relationships and 202 backlinks. Its anonymous GET promotion candidate is staged but inactive: session-bearing reads, POST, HEAD and every admin action remain on PHP/MariaDB. Activation requires 20 clean samples, 24 hours, fresh evidence and an explicit confirmation; a private authoritative rehearsal matched the OLS rollback origin and restored shadow mode. Events has three of seven required distinct clean run dates. The lab compares 23 tables plus all 37 event candidates, 9 categories and 4 public settings while recording only aggregate digests and latency. Observation gates now measure only the trailing clean streak and require fresh evidence. Roadmap needs twenty consecutive probes whose clean window itself spans twenty-four hours, with the newest probe no more than thirty minutes old. Events pairs import and typed-query evidence by exact UTC run timestamp; failed or unpaired runs reset its seven-run, six-day clean window, and a complete run older than thirty-six hours cannot authorize progress. The private Roadmap canary now reproduces the anonymous read API across auth policy, update metadata, columns, cards, links, relationships and backlinks. Its decoded response matches PHP after normalizing only build and storage provenance, rejects POST with HTTP 405, and restarted its clean observation window when this wider contract entered testing. A loopback-only Caddy split-route rehearsal now sends only GET /live/account directly to the least-privilege Go/PostgreSQL service while POST, unsupported methods and every other route remain on OLS/PHP. It exercises generated signup, authenticated read and logout, then proves the temporary listener, process and generated account are removed. The deployed mode-aware reader reports PostgreSQL shadow provenance explicitly and remains fail-closed and non-authoritative until its complete clean observation gate is earned and separately activated.