forward-only rewind: every commit on main between b91382b and 4f3d1d4 has been superseded or is suspected of being implicated in the 2026-04-09 HTTP / delivery outage. rather than force-pushing history backward, this commit creates a new snapshot whose tree matches b91382b exactly, parented on 4f3d1d4. git pull --ff-only continues to work. the superseded commits remain in ancestry and can be referenced via the ops-changelog: - 4f3d1d4 gcLoop: disable malloc_trim, bump interval 10min→1h - 795cc41 host_authority: slot recovery + pool metrics + preload account count - bbba92c fix build: drop unused err1 capture in resolveHostAuthority - 584571a disable keep_alive on host authority resolver pool + log resolve errors - ee4e368 bump per-consumer buffer 8192→65536 + host_authority reject breakdown - 31825b2 subscriber: extract prepareFrameWork + add UAF regression test - 1eec324 fix UAF: dupe FrameWork.hostname per submit (will be re-applied on top) - 168d9f1 bump websocket.zig + zat: fix requestCrawl POST hang - fbdffbe mark DB success on did_cache hits - 3dc21b9 fix gcLoop: silently exited after one tick - e5f415f update README, CLAUDE.md, Dockerfile for current state this commit and the two following it (cherry-pick 1eec324 + pin zat alpha.21) constitute canary 1 per docs/zlay-canary-plan-2026-04-09.md. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>