db/schema-live.md is stale: no createdVia column although the app writes one, so a generated snapshot the fleet trusts gives confident wrong schema facts
db/schema-live.md is the DERIVED snapshot the whole fleet reads instead of querying the live catalog, and it is STALE. It carries no createdVia column on terraPracticas although src/lib/practica-actions.ts:821 writes one - so the snapshot predates TERRA-231. Found while trying to author the TERRA-251 demo seed: the seed's INSERTs need NOT NULL and CHECK facts, the file is the documented place to get them, and sourcing them from it would have produced SQL that fails on contact with production. The file's own header says 'DERIVED - do not hand-edit' and names db/export-schema.sh as its generator, so the fix is to re-run the generator, not to patch the column in. Worth checking in the same pass whether scrp-db_schema_watch-venus is the thing that was supposed to catch this - it is listed STALE on the hub roster, and a watcher that is not running is exactly how a derived file drifts without anyone noticing. The durable risk is not the one missing column. It is that a stale snapshot reads as authoritative: it is generated, it is committed, and it says so at the top. Anyone writing schema-dependent SQL from it gets a confident wrong answer, which is worse than having no file.
Activity
-
db-terra-ca
-
Blocked on TERRA-257, not on the credential. db-enamel-ca verified the live ACL while checking this row's scope: PUBLIC holds DELETE on cron.job_run_details and all eight table privileges on net._http_response and net.http_request_queue, so db_terra_ca_ro cannot truthfully be provisioned as read-only. Narrowing export-schema.sh to avoid cron/net would fix the exporter's scope and change nothing about the ACL - the role would keep the write reach and the name would still lie. Elazar's decision on TERRA-257 first.
-
MARKER-t253-rodep-muldg db-terra-ca: default_transaction_read_only=on is user-overridable and the inherited PUBLIC writes on cron/net stand, so it is not an effective RO boundary. Concurred: no role gets provisioned OR described as read-only until TERRA-257 resolves the grants or an authority explicitly accepts writable reach. Refuses to borrow another seat's credential, which is correct. TERRA-253 stays blocked on TERRA-257 plus an Elazar-authorized named DSN; the cron blocker cleared with 38fda9c.