Require parent directory URI on document delete
The old signature took Option<&str> and silently skipped the parent's
entries-array cleanup when None was passed. The web store was passing
undefined while viewing the cabinet root (the currentDirectoryUri was
losing the root URI at load time), which left dangling document URIs
in the directory record on the PDS. Any consumer mirroring that record
— the indexer included — saw a ghost document that kept showing up in
tree views even after the document itself was deleted.
Two stacked fixes:
- Make parent_directory_uri required all the way up the stack (core →
wasm → sdk → react hook). Callers can no longer silently corrupt
tree state.
- Track resolvedUri (not the caller's input) on loadDirectory in the
web store, and resolve the parent via findParentUri in deleteDocument
so the mutation is robust against viewing context.
Adds an integration test in manager_tests.rs that asserts the
applyWrites batch carries both the document delete op and the directory
update with the URI pruned and siblings preserved.