Reply-not-sent alert goes through sendBakeAlert

Route the reply-not-sent #alerts page through sendBakeAlert with a declared reply_not_sent kind, pass property/org/contact as isTestScope, keep the per-email dedupe key, and delete the file's DIRECT_ALERTS_POSTERS ratchet entry in the same PR.

Status is DERIVED from each row’s own PR, decision and prod-evidence links by bin/refresh-tracker reply-alert-reroute — never typed. Last refreshed never.

Overall
—
 
—
Shipped
—
Merged
—
In flight
—
Open
—
Waiting on you
Groups — click to filter
Status
—

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.

PropFlow Docs