Problem
turnloop-mongodb places two separate, unrelated obligations on the host to supply entropy or unique values, and documents them in two different places: the SCRAM authentication nonce is described in the README, while the requirement that the host supply an ObjectIdGenerator lives in the command module's own documentation.
Why it matters
Perry's P7 lane calls the ObjectIdGenerator requirement specifically "easy to miss until an insertOne reaches the server without _id" — meaning a host can integrate this crate, pass its own tests, and only discover the missing piece against a real server, where a write silently goes out without the id Mongo's own driver would have generated locally.
What would fix it
Consolidating both host-entropy obligations into one place — ideally the top-level README's setup section, since that's where a new integrator looks first — so neither is discoverable only by hitting the failure it causes.
Problem
turnloop-mongodbplaces two separate, unrelated obligations on the host to supply entropy or unique values, and documents them in two different places: the SCRAM authentication nonce is described in the README, while the requirement that the host supply anObjectIdGeneratorlives in thecommandmodule's own documentation.Why it matters
Perry's P7 lane calls the
ObjectIdGeneratorrequirement specifically "easy to miss until aninsertOnereaches the server without_id" — meaning a host can integrate this crate, pass its own tests, and only discover the missing piece against a real server, where a write silently goes out without the id Mongo's own driver would have generated locally.What would fix it
Consolidating both host-entropy obligations into one place — ideally the top-level README's setup section, since that's where a new integrator looks first — so neither is discoverable only by hitting the failure it causes.