admin
dd13f632c8
gates / gates (push) Failing after 7s
P5 measured: a failed run produces NO mail, NO notification row and NO log line from Gitea. A red tick in a web UI nobody watches is exactly the defect R-29 filed, rebuilt one layer up, so the run alarms itself on the project's existing transactional path (Resend, the same one the hub uses) and prints the provider's accepted id, making 'it was sent' an observable rather than an assumption. The key is a user-level Gitea Actions secret created out-of-band; it is in no committed file. The recipient is the operator address the hub already uses and is not a secret. This push is deliberately made while main is still carrying the Scenario B breakage, so the resulting run fails and demonstrates the alarm end to end.