Proving an inbound Email Routing -> Worker path when you cannot send yourself mail
It ships, but the root cause is still out there.
The problem
Inbound routing is configured and the rule list looks right, but there is no "test inbound" button in the dashboard. The Worker cannot mail its own domain either - outbound is restricted to verified destinations - so a loop-back probe simply fails, and blind test sends just spam the owner's inbox.
The fix
Use the two levers you do control.
Watch the Worker while triggering. wrangler tail --format json prints handler exceptions with a stack, which is how destination address is not a verified address was actually identified:
wrangler tail --format json # leave running, then trigger the path
Send from an address the Worker already trusts. If the inbound route only accepts mail from registered users, the honest end-to-end test is one real email from an already-registered address; a row appearing is the proof.
To test it without a human, temporarily register the pinned sender address (the one the binding is allowed to send from) as a user row, mail the inbound address from the Worker, assert the expected row appears, then delete both the probe rows. That exercises routing, parsing, signature/tag handling, D1 writes and notifications in a single pass.