Repository navigation
Add retained custody for protected initial setup - #120
Draft
hypler-dev wants to merge 14 commits into
Draft
hypler-dev wants to merge 14 commits into
hypler-dev wants to merge 14 commits into
Conversation
Retain Linux ACL, mount and SQLite sidecar custody around a private selected-only migration to inert schema 19. Ordinary opens remain at schema 18; this does not add an initializer or an execution route. Publish as a draft to obtain native Ubuntu validation. Static review passed; the local combined gate still has two contention failures. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Bind PHR-0106 to the reviewed source commit and tree. Record static source approval while retaining native validation and readiness gaps. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Add the existing Linux store-to-rustix dependency to mocked metadata so receipt, graph, and command policy tests reach their intended stages. Keep production graph predicates and all test assertions unchanged. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Bind the reviewed mocked graph correction to its exact source commit and keep runtime and execution authority closed. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Serialize ordinary and selected writers by the retained SQLite file identity, retain selected journal custody, and preserve the original native budget across the private store relocation. Add bounded canonical initializer inputs while keeping genuine preparation and atomic installation closed. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Bind the reviewed writer synchronization, selected-journal custody, native budget relocation and canonical initializer inputs to their exact source tree. Preserve all runtime and deployment authority denials. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Require absent WAL and SHM names before selected custody retirement; post-close device/inode equality cannot establish object continuity. Preserve irreversible writer seals while isolating deliberately sealed fixtures in bounded owned processes with retained child diagnostics. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Bind the reviewed retirement predicate and fixture isolation to exact source blobs, preserving prior history and all runtime authority denials. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Retain partial selected-file owners and the original control context on uncertainty. Add finite fresh-schema checks while preserving ordinary-store behavior. This is a private source prerequisite. Complete cleanup planning, genuine strong-profile preparation and atomic initialization remain unfinished. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Bind PHR-0110 to reviewed source 3f0d12d. Register exact source blobs and canonical diff, then refresh generated inventory. Records pre-release source evidence. Runtime, merge, deployment and release authority remain closed. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Create an owner-private hosted-runner root for the five rooted custody fixtures. Preserve every source gate and pin the exact corrected workflow. Keep PR #120 draft; no runtime or release qualification is supplied. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Bind PHR-0111 to reviewed source 8128bf3 and canonical source diff. Keep runtime, merge, deployment and release authority closed. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Retain the original operation and procfs/journal descriptors across bounded custody checks. Keep pending records data-only and leave genuine preparation and atomic initialization closed. Bound outer macOS libtest scheduling without changing explicit 32-writer races or production acquisition budgets. Record focused and full Rust remainder evidence while preserving earlier failed attempts. Signed-off-by: jefftj86 <jefftj86@gmail.com>
Register PHR-0112 against the exact reviewed rooted pending-journal and macOS harness source checkpoint. Preserve source blobs and record source-only scope; genuine preparation, atomic initialization, runtime, and merge remain closed. Signed-off-by: jefftj86 <jefftj86@gmail.com>
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.
Protected initial setup needs exclusive store ownership and reliable handling of uncertain native returns. This draft adds shared physical-file writer synchronization, Linux mount/ACL and WAL/SHM lifecycle checks, inert selected schema 19, compact fresh-schema verification, and a root retaining partial owners and their original control context. Ordinary stores remain schema 18; no public setup entrypoint is added.
The latest source writes only the canonical Pending journal revision. It checks independently selected context, reserves six fixed journal roles, retains returned descriptors before postchecks, and performs bounded write/readback, synchronization, stable scans, and custody checks. Pending data confers no installation authority. Complete cleanup planning, probe/cleanup phases, checked SQL lifecycle, genuine immutable helper/image/kernel preparation, atomic initialization, and management integration remain unfinished.
The macOS legacy Rust runner now defaults outer libtest scheduling to one thread only when the caller supplies no RUST_TEST_THREADS value. Explicit values, Linux behavior, inner 32-writer races, and the single 20-second production acquisition budget are preserved. Historical contention failures remain recorded; their cause is not established.
Source checkpoint:
829a868da4314cbde7a0cb89eadaf68520b8b05b, followed by the exact three-file PHR-0112 metadata childd4d9cdbd3c98949bf207c368593d998238de3af4. Independent source, integration, committed-source, and metadata-outcome reviews passed. Direct-child and publication verification have separate records. No formal GitHub approval is claimed.Validation:
1fd21d36, passed the complete source/signature/audit/build gate and all 19 then-published rooted groups. Separate counts were selected store 155/0/0, full store 659/0/5 and daemon 309/0/0. That tree precedes the new Pending revision. The earlier failed fixture-environment run 42253565432 remains failed; no identical-head retry occurred.New-head Ubuntu Source verification 42316892961, attempt 1 at
d4d9cdb, succeeded. The actual job log names synthetic checkoutc425e296, whose exact base/head parents and tree match the reviewed candidate. All source/signature/audit/build steps passed. Forty-four unique rooted source/fixture groups passed, including the four new native Pending cases and three canonical-input cases. Separate counts were selected store 155/0/0, full store 691/0/4, and daemon 309/0/0; daemon summaries repeat and are not added into unique totals. History pending 0/attested 111 passed. This is a synthetic PR checkout, not a main merge.The push also reported two moderate default-branch advisories; package/advisory identities remain untriaged in this slice. Passing installed-tree CI audit/signature checks do not clear all default-branch advisory types or history. Source CI does not qualify physical custody, native deadlines/cleanup, genuine preparation, Phase 11 runtime, installed tools, support, or release.
Keep PR #120 draft. No merge, deployment, or real target-host/runtime operation is authorized.