Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. Should the test copy of the conversation-events processor update itself whenever main ships, so it never runs months-old code again?
The full question, as raised
conversation-events-bridge-preview :live alias sat on v1 (2026-07-15) for 3 months; deploy-lambdas.yml preview lane publishes per-PR versions but no CI lane flips any PREVIEW alias. Flip preview :live on push-to-main (main code only), on every PR preview (last PR wins the shared preview queue), or leave it manual via deploy.sh?
Why, and what was tried
The session raising this recommends: Follow main on every merge Keeps the preview consumer current without letting one open PR hijack the shared preview queue. Tried first, unsuccessfully: Recovered by hand: repointed the stale Temporal namespace, published v216, smoke-invoked, flipped :live, retried event signaled 3 consumers. Found no CI precedent for flipping a preview alias (git grep update-alias in .github/workflows: PROD_FN only); agent-runtime-preview alias also lags (1843 vs 2075).