Denied-pool reads: single-snapshot or bound-file reads and a non-denied ABA regression

PR #857 checks an H5's byte digest and content identity, reads it, then re-hashes; the identity of the loaded frame is checked in memory. Sol's final round on #857 noted the remaining ABA case: allowed file A present for both hashes, a non-denied file B held open during parsing, A restored afterward — the loader returns B labelled with A's authenticated manifest and digest. Post-read frame verification catches the case where B is denied, not the general misbinding. Follow-up: bind parsing to one immutable snapshot or a bound file object in the authenticated and generic loaders, add a non-denied ABA regression, and bind release and cache identities to the loaded snapshot rather than the pathname. Refs #856, #857.

🤖 Generated with Claude Code

Start by examining the authenticated and generic loaders discussed in PRs #856 and #857, focusing on how parsing, release, and cache identities are tied to a pathname. Add the described non-denied ABA regression and verify that reads, release, and cache operations remain bound to one loaded snapshot or file object.