Repository navigation
test(mvm): retain custody after final store removal refuses - #311
Merged
Merged
Conversation
6 of 8 tasks
Casey-allard
marked this pull request as ready for review
November 16, 2026 07:46
This was referenced Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A real installed-store directory-removal refusal after codec cleanup unlinks the owner filename must retain the original inode lock, child/lease and all booked charges in quarantine. Restoring fixture permissions must not return credit or reopen admission.
The native consumer workflow preserves the original fourteen controls and their order, including the destruction-before-credit assertion. It appends one explicitly selected unprivileged control and requires fifteen nonzero passes plus the exact refusal event. A root actor fails. Deadlines, security checks and
--lockedremain unchanged.Consumers select published MVM
cc2ed208a7b1adde7fa1f075bbfff2428f911e18(tree52e3463526c94a5941a16fa187158fd630c258bd), on canonical2b1cd835, with reviewed SpiralCore8994951b. The ADR-061 framing reconciliation moves the two existing contributor helper bodies byte-for-byte to core and retains the hostd facade. Four compatibility controls cover bytes, caps and validation before typed parsing. The cc2 successor corrects only native metadata comparison types in the new test, preserving device/inode identity without casts.Reviewed head:
35efbb610e291c985fc16569f8ec8b6e3030bd98. Its treeff95d48508419daa17f9f6bace0e8a6dea15b162equals successful CI merge40575540.Validation:
The exact 49-byte refusal fixture records 268/218 serialized in-memory request/reply bytes and zero network traffic. Seven native FlowMux rows recover 64 MiB each direction and record 10,790,065 actual TLS bytes. Windows ARM records 183.000709 s lifecycle / 96.578125 s whole-process CPU under unchanged guards. These are observations, not a causal speedup, booted MVM or WAN result.
Original 34e locked-resolution failures, 038 macOS compile failure and 5fe full1 stale-target-count failure remain recorded alongside the full2 preservation loss. Full #258 remains open for prepared funded retention metadata and the joined original-owner concurrency/allocator witness. All five #42 outcomes remain required, including compatible signed runtime/boot, separately admitted access, supported platform/WAN/capacity and final upstream acceptance. Maintainer pin agreement and private MVMD remain external. This is a SpiralCore integration slice, not the final upstream contribution.
Refs #258, #42, #268.