The inbox-watch failure page was routed to the digest by the default flip, and never DMed.
Two pages that stopped paging
cron-quota-exhausted lost its POLICY entry as well.
What changed
POLICY now pages inbox-watch:broken, and cron-quota-exhausted pages again. Both changes came with tests.
The same commit that restored cron-quota-exhausted also changed two other things:
Blog and social git spawns are hidden.
The nightly failure notice now leads with failing test ids.
The ticket behind that commit fixed 4 of 6 nightly failures. The other 2 are a live-data alarm, left red on purpose.
The drill
The CLI also gained inbox-watch --drill, with --notify, which sends a drill-labelled page through notify_ben.
AI Skills
Use this lesson with the AI assistant you already use
A default flip sent the inbox-watch failure page to the digest, so it was never DMed. The cron-quota-exhausted page had also lost its POLICY entry and stopped paging.
Paste the prompt, share only the context needed to answer it, and treat the result as a draft for your review. Do not include confidential information or let an AI assistant make changes without your approval.
Optional: for a visual report and saved memory, run /dxdev first.
Don’t have it? Get it at dxdev.com/skills/dxdev. The prompt works without it.
dxdev LESSON · paste into your AI coding agent
LESSON: When You Flip A Routing Default, Pin Every Must-Page Alert Explicitly And Prove It With A Drill
SOURCE: dxdev.com/blog/failure-page-sent-to-the-digest
WHAT HAPPENED: A change to the notification default routed the inbox-watch failure page to the digest instead of a DM. The page that should have interrupted someone became a line in a summary. The cron-quota-exhausted alert had also lost its POLICY entry, so it stopped paging too. The fix added POLICY entries so inbox-watch:broken and cron-quota-exhausted page again, and both changes came with tests. The CLI also gained an inbox-watch drill command with a notify option. It sends a drill-labelled page through notify_ben, so the real delivery path can be exercised on demand.
THE RULE: When a routing default changes, every alert that must interrupt a person needs an explicit policy entry backed by a test, because anything not listed silently falls to the quiet default. Prove the delivery path with a labelled drill instead of assuming it works.
CHECK MY CODE, then report PASS or FAIL with file:line for each:
1. Every alert that must reach a person has its own explicit entry in the routing policy, and a test fails if that entry is removed.
2. A test asserts the routing of each critical alert id after any change to the default, so a flip cannot demote one without a red build.
3. A drill command exists that sends a clearly labelled test page through the real notification function, and it has been run to confirm the page arrives as a direct message and not in a digest.
THEN PRINT: a table (check, PASS/FAIL, evidence, fix) + a verdict (applies / partially / OUT_OF_SCOPE / no) + the single most important next action.
