Repository navigation
R1: persistent boot-to-Zsh system #5
Description
Migration and public-source publication are tracked in #1. Retain the qualified legacy IDs below; completed historical work is not reopened.
Outcome
Assemble the mandatory first-release capability from R1-01 through R1-07.
Scope and non-goals
Dash, a RAM-only image, host package runs, NVIDIA and network fetch cannot substitute for or enlarge R1.
Responsibility: system.
Acceptance
- One image boots through sys-init into interactive serial Zsh with runner, persistent OpenZFS and native package install/list/verify/run/remove.
- The actual assembled system meets independent build, failure/recovery, notices and operator-instruction gates.
Verification
- Capability acceptance and child evidence on the same frozen system; release publication is separate.
Prerequisites
No additional blocking dependency is asserted here. Readiness still requires a bounded selected scope, available inputs and owner authorization.
Contracts and legacy IDs
Legacy IDs: R1.
Start and completion rules
This is a coordination epic, not a blanket implementation assignment. Keep distant work coarse; select bounded child issues before implementation. Close only after its capability exits and required child evidence are met.
A hosted source check, host fixture or peer-agent review is not native OS, recovery or release acceptance.
Activity
gonz0w commentedon Oct 27, 2026
AF09 diagnostic preparation #75 is complete through protected PR #76. The unfiltered host gate and complete eight-case offline family pass; separate review covers all 20 roles/40 files, actual commands and cleanup. Parent #64 now retains the next native admission/drain qualification gate and fresh concrete execution disposition. No guest, interactive Zsh session, persistent release ISO or R1 completion is claimed. Zsh/TTY, filesystem operation coverage, filesystem-backed exec, sys-init assembly and packages remain separate existing dependencies.
gonz0w commentedon Nov 3, 2026
Development checkpoint #143 is complete via merged PR #144: real interactive Zsh runs its held helper, receives status7 and returns to its prompt, then exits with filesystem export and all three processes reclaimed. The accepted trial took34.169s; final required CI and exact merged-tree verification passed. This advances the shell/process path, while assembled sys-init boot, persistent shell write/reboot readback, runner/packages and R1 remain open.
The selected next bounded work is #145: source-derived selection of one capability-scoped Zsh home-write/export/cold-readback workload. It adds no runtime authority or broad test campaign; consequential design/resource/gate choices will be brought to Cam as concrete reviewed proposals.
gonz0w commentedon Nov 3, 2026
Issue145 is delivered through PR147: real Zsh launched the fixed helper, completed its16-byte home write, returned to the prompt and exported cleanly; independent fresh OpenZFS readers verified persistence and unchanged original metadata/media. Protected merge
e55ce333cc49de25516ddb713e97980151b7c459has the exact reviewed tree and both required CI checks pass.This closes that persistent-shell prerequisite. This R1 epic remains open for its assembled sys-init/runner/package and release gates; #141 retains the broader host/integration gap.
gonz0w commentedon Nov 4, 2026
Delivered #148 through PR149, protected merge8e944fdf61fff31f48fd5de686e67958f030e592. Real Zsh executed the sealed3548-byte ELF acquired from OpenZFS, collected/printed23 and returned to its prompt; normal parent/engine export, mode restoration,21 cleanup phases and three reclaims passed in38.678s using42/96 requests. Both host holders and five clients have known cleanup; existing limits are unchanged. Required Source integrity/Kernel models and separate source/artifact/native-result reviews pass. The assembled sys-init → interactive shell/runner/package image and its recovery/release gates remain open; this is the approved fixed executable-loading checkpoint. #141 remains open.