Two tests raced the host: one asserted the staged copy was applied the instant the books reopened, the other that a dropped tampered copy's folder was gone, when the new host may look at the feed again and stage a fresh, true copy in its place. Both wait for what they mean now (the apply; the tampered bytes gone). Every whole-program comparison is on the sha256, so a failure's message is a line, not two binaries (GitHub kept nine lines of a step's log on one such message). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HS8WZziDnyxunC23MUxrLp