Repository navigation
Conversation
added 30 commits
October 8, 2026 08:29
…tained-storage # Conflicts: # src/lib/native-compose-command.ts
…torage-witness-carrier
…torage-witness-carrier
Contributor
|
Found 1 test failure on Blacksmith runners: Failure
|
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light.svg)
This branch has not been deployed
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
1 participant
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.
This adds a private finite Linux ARM64 storage-content witness carrier. A durable Expected receipt precedes cold provisioning and the one create-only xattr seed. Enrolled volumes require read-only token proofs; missing markers, changed roots, uncertain helpers and interrupted enrollment retain recovery anchors and refuse workload admission or clean retirement.
The Docker port requires the pinned cached Bun image and fixed helper bytes before volume effects. It mounts the exact named volume with nocopy, checks its owner and birth before create and again before start, checks overlapping holders, disables daemon logging, and owns finite children through bounded private descriptor I/O and exact helper cleanup. Docker can create an empty volume during a missing-name race; that footprint cannot grant enrollment, helper start or workload admission. Saved recovery cannot reseed or retire unresolved helper work.
At exact head b522f10, a direct PostgreSQL cell observed one UID0 seed, a successful SQL insert/read, the UID0→70 and mode0700 transition, unchanged root device/inode, and read-only verification under UID70. Its fixture cleanup then refused at a startup-only authority check. The original attempt remains failed. A separately reviewed exact stop and nonforce container/network/volume cleanup passed, and an independent full original-inventory check passed. This proves the bounded persistent carrier behavior observed in that cell; it does not qualify ordinary CLI activation or retained SQL recovery.
Validation: cumulative independent source review through b522f10; closest synthetic owner/journal/FD/inventory/policy controls and scoped CLI typecheck, changed-path lint, privacy and diff checks. The helper remains byte-identical to the qualified 14,427-byte artifact. Historical foundation full/TLC evidence remains separate. Current hosted checks have eleven successes and one unresolved Docker E2E ownership refusal in the process-policy scenario; that required check blocks readiness.
Ordinary native-config commands do not activate this port in this PR. Ordinary cold/startup and retained SQL down/up/interrupted recovery, Linux amd64 helper/permission/SQL qualification, fresh required full gates, and current hosted CI remain open. No fresh-install dependency or emulation fallback is claimed.
Release signal: optional capability groundwork; ordinary CLI activation remains a separate increment.