doyle on 8c083aa, three more things. Verbatim.

"Keep 8c083aa unadmitted; no need to re-review interim revisions before perri completes the four requested changes."

That is aimed at me as much as you: I stop reviewing each interim commit. Push at whatever granularity suits you and ping me when the four are complete -- I will read the whole thing once, not each step.

1. ACCOUNTING, and this is a NEW requirement on top of void-vs-null: "retain every scheduled case in the results. Unavailable evidence may be excluded from a rate's eligible denominator, but report scheduled, attempted, evaluable, and unavailable counts separately - never make VOID cases disappear."

Four counts, reported separately, not one denominator with an asterisk. Scheduled is fixed up front (your 5 + 5). Attempted is what actually launched. Evaluable is what the rate is computed over. Unavailable is the NO-KILL and ROLLED cases. Your 8c083aa change excludes void from the denominator, which is correct as far as it goes -- his point is that exclusion must not also remove them from the report. A run of 10 scheduled, 10 attempted, 2 evaluable, 8 unavailable is a legitimate and highly informative result, and it must be impossible to read it as 2 of 2.

2. TRUSTED DIRECTORY: "Verify the named trusted directory's effective imports/configuration read-only; do not alter it to manufacture isolation."

So when you name the already-trusted dir, you VERIFY what it actually imports and what config is effective there, read-only -- and if it turns out to carry a CLAUDE.md or an AGENTS.md or anything else that breaks the import-free property, you REPORT that, you do not delete or move files to make it clean. Manufacturing the isolation would make the dir a thing you modified, which is the write he just ruled out arriving through a different door. If no suitable trusted dir exists, that is a finding for him, not a problem for you to fix by editing one.

3. NEXT HANDOFF, verbatim: "Next handoff is the complete bounded precondition-check plan, with no trust writes or automatic interactive fallback."

So the deliverable he is waiting on is the PRECONDITION CHECK plan, complete and bounded, carrying the no-trust-writes and no-auto-fallback constraints -- D1 and D2 as their own admissible unit. The 10-case battery follows it; it is not the next thing he wants to see.

Standing: nothing granted, no window held by either lane, no execution or config mutation authorized.