Baton v0 Slack runtime bringup

Implemented ALL-919 smoke runner at scripts/baton/smoke-all-919.ts and added root npm script smoke:baton:all-919. Local TypeScript check passes; smoke command executes and fails expectedly on missing Baton/Slack env vars. Next: run against deployed baton-agent once BATON_AGENT_BASE_URL/TOKEN and Slack smoke env are available.

Baton runtime bringup not live. Lyra verified fleet-baton-01 can read Fleet Secrets and Slack/Anthropic secrets exist, but Neon Postgres - Baton DB item is missing. Waiting on Victor to provide baton-db Neon connection URI; required 1P field name connection_uri. ALL-919 smoke blocked until deploy succeeds and /ready is 200.

Lyra reported agent-infra PR #181 deploy workflow merged and PR #182 Anthropic 1P field fix merged. Runtime bringup still blocked only on missing Neon Postgres - Baton DB connection_uri in Fleet Secrets; holding for Victor/Lyra to provide URI before deploy + /ready + ALL-919 smoke.

Lyra supplied corrected Baton DB 1Password refs: op://Agent Secrets/Neon Postgres - Baton DB/{connection_uri,pooled_connection_uri}. Updated ALL-919 smoke design doc to use Agent Secrets paths. Validation on fleet-talos still shows only Fleet Secrets vault visible to HOME=/var/tmp/op-agent SA, so Agent Secrets read fails on this host; reported back in #agent-ops thread without logging URI.

Correction from Lyra: ALL-919 smoke runner should use Doppler project baton/config prod_baton secret DATABASE_URL, not direct 1Password refs. Updated smoke design doc accordingly and noted disjoint 1P SA visibility. Initial fleet validation with doppler CLI failed because no Doppler token is present in current process environment (Doppler Error: you must provide a token); discovering token injection path next without logging secrets.

Lyra corrected Doppler status: no fleet-host Doppler token exists; PR #183 was deploy-script only; Doppler/GCP work is on unmerged lyra/baton-ci-doppler fd5173b with baton/prod vs prod_baton mismatch. Updated ALL-919 smoke design doc to make GitHub Actions with BATON_DOPPLER_TOKEN the short-term canonical smoke path after branch merge/config drift resolution; fleet-local smoke explicitly blocked until scoped token is provisioned in Fleet Secrets.

Lyra confirmed option #2: she owns unblocking agent-infra lyra/baton-ci-doppler by resolving prod/prod_baton drift, manually populating canonical Doppler config, opening/green/self-merging PR, then ALL-919 smoke should wire to GitHub Actions with BATON_DOPPLER_TOKEN. Talos will not request temporary Fleet Secrets token; fleet-local smoke remains blocked unless explicitly provisioned later.

Opened mono PR https://github.com/TextureHQ/mono/pull/10755 for ALL-919 smoke runner after green agent-infra sync-baton-secrets run 26006499376. Local gates: tsx expected missing-env failure, direct tsc script typecheck, package.json parse.

Pushed PR #10755 fix 9dccff91b for ALL-919 smoke review feedback; local focused TS/biome/diff-check passed; CI rerunning.

lease expired — re-queued for retry

Pushed PR #10755 fix b9d00d000 for latest ALL-919 smoke Cursor findings; local tsc/tsx missing-env/static/diff checks passed; CI rerunning.

lease expired — re-queued for retry

PR #10755 checked: CI was green on b9d00d000, review required. Cursor Bugbot reported Slack bot response detection issue (!m.user). Fixed in 144700223d by using bot/app metadata, validated tsx expected missing-env failure + tsc + package JSON, pushed branch, resolved review thread. New CI has not reported checks yet immediately after push. Next: wait for CI rerun to go green; then PR is still review-required and blocked on Doppler/secrets/runtime config (Victor/Lyra) before useful E2E smoke/merge.

ALL-919 PR #10755 verified green with zero unresolved review threads; blocked only on human approval / Victor Linear status. ALL-914 not Lyra-actionable.

ALL-919 smoke runner merged and runnable; real smoke blocked on missing BATON_SMOKE_* env/Slack token target/base URL. Infra gate for gcp-baton-01 remains green.