Data API OFF is an unowned config that terra's pg_temp LATENT rating silently depends on

Terra's LATENT rating on the pg_temp shadowing exposure rests entirely on the Supabase Data API being OFF (db_schema="" from the Management API, corroborated by a pg_pgrst_no_exposed_schemas sentinel in the postgres log ~every 32s; measured 2026-07-31, two planes/two credentials, by coder-enamel-cc + db-enamel-cc). That is a CONFIG, not a property: one deliberate enablement on enamel's surface flips it and flips terra's rating with it. No owner, no alarm, and NO CATALOG READ PATH — pg_db_role_setting checked in full, no pgrst.db_schemas under any role or database. Instruments are a Management API field and a RETENTION-BOUNDED log line, so a future reader finding no sentinel must NOT read that as a state change. Inverted trigger (pmmaster ruling 2026-07-31): the arming event is a routine enablement someone performs to expose a table to a client, reviewed on its own merits, by someone not looking for a shadowing rating that depended on it. DURABLE half, cite SEPARATELY and never joined: anon/authenticated hold ZERO grants on every terra and shared table and zero EXECUTE on all 13 functions — that survives an enablement; db_schema="" does not. The joined form is the reassuring one and has already been used as such. CROSS-BOUNDARY: the enablement surface is enamel's (terra has no Supabase project), so the record must live where enamel's operator stands — raise with pm-enamel-cc; a record on the wrong side of a shared boundary is the same as no record.