Repository navigation
Fund installed store quarantine before operational effects - #313
Merged
Merged
Conversation
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.
Uncertain installed-store retirement could grow its quarantine vector after cleanup had already failed. Select reviewed contributor MVM 1298ffe9, which prepares bounded retention slots before pool publication and funds their checked layout from the original retained metadata owner. Generic parent callers permanently carve this bookkeeping from their existing resident ceiling; operational refunds do not release it. Original store/lock/parent custody, destruction-before-credit, cleanup-specific authority, budgets and deadlines remain.
Update active MVM pins and lock identities without package/version/feature changes. Both direct MVM dependencies and all five shared-core packages retain SpiralCore
8994951b. Native consumer CI preserves original controls 0–14, including control 6's destruction-before-credit assertion and control 14's final-rmdir refusal, then appends five exact nonzero funding/retention controls. Document permanent metadata versus operational drain, with allocator/RSS/simultaneous-peak limitations explicit.Validation binds reviewed head
448da7a4, CI mergeccfa6b25and tree17067b9b. All 35 executed checks pass; genuine signed export is skipped/NOT_RUN. Original 28 ZIPs/3,665,755 bytes match GitHub digests; 909 members, 644 embedded checksums and 25,010 source rows verify. Native Linux x64/ARM64 and macOS ARM64 each execute all 20 controls. Both Linux original-Root/store-load rows preserve 64 publications, exact 1 MiB each direction, the original 2 GiB ceiling and 295,698,432-byte hard address-space limit, seven-thread sampled envelope and retained VM debit. Seven FlowMux rows recover 64 MiB per direction with 10,790,065 actual TLS bytes under unchanged two-second/240-second guards. Windows ARM records 98.043522 s lifecycle and 96.640625 s whole-process CPU; no causal speedup or WAN claim.Frozen MVM
1298ffe9, tree228b513d: formatting, strict workspace Clippy, Linux all-target and explicit BDD compilation pass; all 86 policies and full execution pass with 21,890 outer binary tests plus 27 doctests, zero failures, 72/eight ignored. All 4,758 inputs and 286 freshly compiled/actually executed ELF pre/post identities match. The test command records 486.79 s wall/175.34 s user/88.46 s system CPU. SDK 175 live/29 owner/74 supervisor/addressed and paired 18-test scopes pass with explicit ignores, original executable custody and complete 490/17/five-fixture source guards. Four SDK invoking roots retain core/crypto opt2, debug assertions and overflow checks; paired opt0 is separate. Eight normalized graphs plus the canonical Linux alias match the reviewed predecessor. Independent source/security, qualification and native-artifact reviews are clear.Retain original failed evidence: the first compile lacked Debug on a fixture; the first full controller stopped at missing archived uvx; the first SDK run correctly refused ZFS for its existing ext4/XFS-only startup-bound fixture. Restored HDD codegen tools/cache pass no-drift validation, and the existing operator-selected small ext4 test root passes unchanged address-space/filesystem assertions and is removed afterward. The original exits remain failed. Historical 79 lost executable preimages remain lost. New current executables are losslessly archived/verified before later compilation. The former 107 GiB SSD scratch is archived on HDD; builds/cache stay on HDD and torrent/media paths are untouched.
Refs #258 and #42. This bounded custody/funding slice does not complete iterator/allocator/concurrency, installed MVM, WAN, capacity, FIPS or final upstream acceptance. Compatible signed runtime/accepted pins/private MVMD and all five delivery outcomes remain gates. Preserve Ari's canonical service, V3 ownership and source-specific CLI grant/audit migration path.