A Deploy Lambdas run whose compute job has waited 20+ min for a machine, with nothing executing, is cancelled by deploy-queue-watchdog.yml on its next sweep — slot freed within 30 min, no human.
Status is DERIVED from each row’s own PR, decision and prod-evidence links by
bin/refresh-tracker deploy-lambdas-stuck-clears — never typed. Last refreshed
2026-10-23 06:40Z.
Every row opens: when it was added, why it exists, and the links that prove it. Rows waiting on a human carry a Decide → link straight to the answerable question on the decisions page. Statuses are re-derived from live PR, decision and prod-evidence state by bin/refresh-trackers; nothing here is typed by hand. Merged and shipped both count as done (Gera, 2026-10-19); a prod_evidence permalink is what moves a row from Merged to Shipped.