Repository navigation
Qualify original store custody after final parent sync refusal - #315
Merged
Merged
Conversation
6 of 8 tasks
Casey-allard
marked this pull request as ready for review
November 16, 2026 13:08
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.
Final directory removal can succeed before syncing its original parent fails. This slice qualifies the existing quarantine behavior at that boundary: the permit's first cleanup attempt must retain the same unlinked child, original locked owner, lease and complete debit after the sync refusal.
The consumer selects reviewed MVM f2ddbcbf, tree
165f5cc95fda4cba7da885e6546d22be8d3e94a5. Its three-file change is confined to tests. A Linux O_PATH parent is retained from fixture preparation; a nondestructive errno probe is separate from the first cleanup in permit Drop. After real removal, the original lock, lease, charges and prepared quarantine pointer/capacity remain, admission is fenced and drain refuses. The canonical 49-byte object is independently read back. This is a funded pool fixture, without a registered child or new VM boot.All 16 revision-only files change exactly 159 pin occurrences. Shared core
8994951b, package versions, features and dependency edges remain. Native controls 0–19 retain their exact execution order, privilege and assertions. Linux x64 and ARM64 append exact nonzero control 20; macOS retains 20 controls and an explicit NOT_RUN for the Linux mechanism. Original deadlines, security checks and destruction-before-credit assertions remain.Exact-source validation and focused independent source/security, executable-custody, SDK/paired and native-artifact reviews pass:
76665cadshare tree8438038d.Original test-ordering, naming-policy and formatting records remain source-specific. The earlier 79 historical preimages remain lost. No archived binary was executed to verify the archives. Builds, cache and preservation archives use HDD storage. Compact permanent evidence publication follows this source merge.
Refs #258 and #42. Both remaining #258 criteria and all five MVM delivery outcomes stay open, including joined phase-specific iterator/allocator peaks, remaining recovery, compatible signed runtime, accepted pins/private MVMD and supported platform/WAN/capacity qualification. This is an incremental SpiralCore slice, not the final upstream MVM contribution.