[FEATURE] Complete native shell/build utilities and provide help and offline manual pages #1
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/exsh#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
Users must launch compatibility tools and full builds through the native shell, with reliable job control and discoverable documentation. Tool-name exceptions or importing a shell to hide native POSIX gaps would leave the normal user path incomplete.
Proposed behavior and scope
Close selected POSIX shell and utility gaps, integrate real process/job semantics, and provide internal help plus a native man applet. Cover every CLI and IPC/Rust/C API with current indexed documentation and exercise scripts, pipelines, redirection and interactive navigation through real inputs.
This issue records planned work; its unchecked criteria are not implementation proof. The normative basis is Phase 6 and AC1–AC24.
Authority, security and reliability
Preserve native descriptor/job envelopes and exact TTY consent boundaries. Built-in help gains no filesystem authority; manual lookup reads only delegated roots and never executes page macros or embedded commands. Program names, arguments and environment paths cannot select broader authority.
Apply the priority order: security, reliability, then performance. Keep suspected vulnerabilities in the repository’s restricted SECURITY.md reporting channel.
Acceptance criteria
Checklist
against the selected POSIX shell standard; enumerate remaining syntax, expansion, built-in,
signal, group and stopped-job gaps with tests.
remaining mandatory profile items; preserve native descriptor/job authority and distinguish
true fork from in-process descriptive state copying.
executable-name/argv-specific authority semantics; tools request/fail operations on their own,
within the launch envelope.
wait/trap/job-control interactions against real POSIX processes and groups.
descriptors, interruption and concurrent output; remove incidental shell storage limits
through caller/resource-owned growth.
required clean-room behavior in thematic modules and record where an explicitly inventoried
extended GNU tool is required instead.
trusted consent, output drain and repeated-command behavior under build load; add focused and
existing regression VM coverage.
checking exact output/status and zero authority leakage.
helpcommand with Bash-like behavior: no-argument topiclisting, pattern/topic selection, short description (
-d), manual-style output (-m),synopsis (
-s), option errors and match/no-match exit statuses. Verify combinations againstthe selected Bash reference.
helpfrom exsh's authoritative built-in/topic registry, documentingactual exsh behavior rather than advertising unimplemented Bash extensions; it must not spawn
an external executable or acquire filesystem authority for built-in help. Author original
explanatory text.
flags, invalid requests, redirection, pipelines and exit statuses.
coreutils man: section/name lookup, disambiguation, multiple pages,search/index behavior, terminal versus redirected output, missing-page errors and scoped
manual-directory discovery.
manas a native coreutils applet with readable paging,scrolling/search/quit and plain-text fallback for pipes; safely parse the chosen documented
man format and never execute page macros, escapes or embedded commands.
and Rust/C linkage APIs; inventory every exported interface and require an indexed page or a
clearly linked owning API page.
authority needs and errors for every tool, including
help,man,boot-tool,sha2-tool,exsh and extop; include admitted extended-tool manuals only under their declared
source/license/manifest policy.
layout or signatures, safety/ownership/lifetime/authority, errors, examples and
cross-references to canonical rustdoc/header/manual text.
authority; environment paths cannot broaden the manual scope or cause execution. Make docs
available without network access on both images.
mannavigation,resize, pipe/redirection, missing-page and denied-root VMs. Verify every CLI/interface
inventory entry resolves to useful current content.
For each implementation slice, retain actual formatting, strict Clippy, unit/doctest and warning-denied build results for all altered Rust repositories and valid configurations. Add relevant runtime VM coverage, monitor older unit/VM regressions in exact-head CI, and update canonical component documents and affected technical-manual/API material. Every authored code file must remain below 1,000 physical lines, with meaningful inline documentation and missing_docs enforcement in Rust crates.
Alternatives and tradeoffs
Admitted GNU tools or bash may cover declared non-POSIX recipe needs, but do not substitute for mandatory exsh behavior. Generate documentation from actual semantic registries where useful without advertising unsupported extensions.
Those runs provide no workspace or complete frame acceptance. Complete source/effect/frame admission, source-bound consumer VMs, complete realm operation and both full guest builds remain required.
Both original runs fail the required complete frame-proof gate after 961 Rust units and 355 checker controls pass. Complete realm execution and both full guest builds remain required.
Native caller diagnostic producer — 19 September 2026: Signed
183bcb9e9b4e37ecfab65bd0baa0cde53d02c728adds an explicit diagnostic on the existing authenticated Launchd route, sending no capabilities. It exercises eleven calls covering reservation, full-width generation refusal, missing-scope refusal, retirement and record reuse. No complete frame or diagnostic VM acceptance is claimed. Matching Integration scenario validation and original CI are in progress; successful preparation, mediator startup/configuration/seal/client I/O, native toolchain rebuilding and both full OS builds remain required.Tracking and rollout
Caller-loss startup boundary — 29 September 2026: source audit found that the draft helper could not use the ordinary Exsh manifest as planned. Launchd derives fixed routes from the authenticated manifest: the ordinary entry supplies a redirection resolver even if the request omits its destination, and does not declare inherited launch. Host transport tests alone did not establish the helper's actual startup authority. The earlier full validation attempt was explicitly cancelled with owned-child cleanup before changing its frozen source; it is not native acceptance.
The implementation now packages a distinct
/bin/realm-owner-loss-callerentry backed by the same Exsh artifact. Its manifest declares only cwd and inherited launch, with zero authority rows and no resolver or observation broker. The original Exsh graph root and ordinary startup inventory remain intact. In the selected diagnostic image, immutable LCS1 command-entry evidence selects the reduced inventory; argv cannot select it. Exact helper commands are required, with no environment or extra description records. Every architectural capability slot is checked, including absence of excess authority. The existing status-only parent wait and original VM gates are preserved.Four focused startup controls, eight actual transport controls, strict native all-feature Clippy, five graph/manifest/installer controls, seven existing generic-manifest controls and six scenario controls pass. Installer controls exercise the actual validation and generated alias/sidecar commands; they do not claim an ext4 mount or native execution. The updated manual passes 45 controls; its complete render remains pending. A corrected full Exsh matrix is running. Coordinated signed source adoption, full Integration validation, native execution and original CI are still required. No lifecycle checkbox or completion credit is added.
Caller-loss implementation — 28 September 2026: a separate opt-in native diagnostic is being implemented for the active realm-lifecycle requirement. The initial shell keeps one realm sealed while a second, ordinarily launched Exsh configures the other realm and exits without ABORT. Two helper generations cover sealed clients and one START-acknowledged client with its reciprocal peer still unstarted. The parent requires the original Exited/zero helper outcome before testing reclamation, then replacement execution and acknowledged retirement beside the surviving peer; the peer itself must execute successfully afterward. This addresses loss of an actual realm caller, not loss of Launchd itself.
The helper uses the already authenticated scoped launch route, cwd SEND and independently provisioned job-bound TTY streams. Its parent requests only a status return route: no administrative kill, job control, inspection, interactive approval, extra object grants or redirection resolver. Only canonical, correlated, authority-free resource exhaustion can be retried, with a new request ID and yield. Lost replies and uncertain cleanup remain fatal. The independent VM retains the 120/45-second gates, two realms, four clients and 576 plan bytes; 39 managed rows account for the additional ordinary helper. The existing 38-row disposal witness is unchanged.
Eight focused Exsh host controls and strict native all-feature Clippy pass; composed real launch/realm transports exposed and corrected use of the foreground wait path, which required unwanted job-control authority. The diagnostic now uses the existing status-only wait. Six Integration controls cover actual intake, conflicting selections, emitted BootConfig geometry, original exit/deadline gates and ordered markers. Full component validation, signed graph adoption, native VM execution and original CI are pending. No native caller-loss acceptance or additional checklist credit is claimed.
The preceding roadmap-only revisions have complete original CI evidence: Kernel runs 708/709, Docs 1105/1106 and Lib-cstd 15/16 pass with twelve complete logs and zero final warnings. The manual passes 45 controls and builds 2,657 pages. Integration 1831/1832 remains waiting. These newer Docs successes do not resolve bug 11: earlier runs 1103/1104 retain three failed job logs returning HTTP 500 and an unknown cause. No unchanged failed job was rerun for acceptance.
Prioritize completing each checklist item fully in one sustained pass: implementation, security/reliability audit, required validation, documentation, signed publication and complete CI review before unrelated work. Keep genuine blockers explicit and do not substitute intermediate checkpoints for full acceptance. The active remaining realm-lifecycle item includes positive numerical NeverExecuted accounting, abort/retire and partial-cleanup paths, supervisor loss and resource-ceiling validation. Already accepted native disposal/reuse and pool refusals remain prerequisites. Unrelated optimizations and regressions stay tracked unless evidence makes them dependencies. This execution priority does not change the phase scope, original gates or completion arithmetic.
Exact Launchd 2-realm/4-client/576-byte, Procd 38-record and Pagerd 102-binding budgets require reclamation. All six actual successful client exits, realm/client/plan refusals and original capability routes remain intact.
The client VM and older preparation/startup VMs pass every original marker, exit and 120/45-second gate. Retained client evidence binds 109 artifacts, 57,045 serial bytes, empty QEMU stderr and zero warnings. This accepts the native disposal/reuse sub-item. Separate positive NeverExecuted CPU accounting remains required: the first capture was rejected before boot because the host GDB package changed; after RPM identity/API verification and fresh two-positive/twenty-negative verifier controls, a separate capture reached the original 120-second limit after five Measured commits, before either NeverExecuted snapshot. Its failed result and cleanup are retained. No deadline, guest byte, authority or oracle was weakened; no numeric completion or speedup is claimed.
All fourteen Exsh development/release selections pass 988 tests each, strict host/native builds, Clippy, rustdoc and 355 checker controls pass without warnings, while native frame proof issue 4 stays open. Docs CI1099/1100 passes 45 document controls and the complete 2,657-page manual with zero final warnings. Integration passes its 187 host commands. Original CI1824 passes all 492 scenarios and subsequent image/input gates. CI1823 instead stops in the known physical utility host fixture, before catalog VMs. The companion pass does not resolve that intermittent failure.
All 22 original Integration runs 1803–1824 now have complete reviewed logs: 66 logs, 264,989,379 bytes, zero warning candidates. The smoke-policy defect is closed on its source correction and matching full-CI evidence. Remaining observations are retained under pipeline, ext4 quota, physical consent, interrupt reuse, canonical release, and the new canonical-template reports for release COM1 editor and canonical development. Their causes are not inferred from wrapper failures, and no unchanged CI job was rerun.
The phase checklist now records 419/879 completed sub-items, 17/460 accepted parents, and 15.45% weighted progress. Numerical NeverExecuted accounting, remaining authority/lifecycle cleanup, complete CI/frame acceptance, external Rust/LLVM/toolchain rebuilding and both complete EriX builds inside EriX remain required and unproved.
Both stale-client generations must remain absent. All six actual successful client exits, realm/client/plan capacity refusals, original capability routes and the 120/45-second guest gates remain mandatory. Independent native accounting must positively capture two zero-CPU NeverExecuted clients, six Measured clients and six Measured mediators. Local cancellation or absence cannot substitute for those records.
The preceding shell fails at call 88 in the independent 141-call transcript; all eight focused controls pass on the new source. All fourteen ordinary development/release selections pass 988 tests each under unchanged limits, with strict host/native builds, Clippy, doctests, private rustdoc and 355 frame-checker controls passing without warnings. All six separate local optimized frame observations produce incomplete reports and retain exit 1: runtime 271/97, all-features 298/63 and configured clients 323/100 reached/unresolved in both deployment profiles. These are not accepted frame proofs.
Original Exsh CI 291 and 292 each pass 988 unit tests and 355 checker controls, then fail the still-open native frame proof. Their own artifacts report runtime 256/101 and all-features 288/68 in both profiles. All four complete logs, totaling 323,674 bytes, are reviewed with zero warnings and no additional compiler or test failure. Native frame counts belong to their exact build configurations; different observations are not combined into a proof or speedup claim.
All 45 document controls, Markdown/template/link/reference checks, the complete 2,657-page manual and all 491,759 word bounds pass; three affected/adjacent pages are visually reviewed. Original Docs CI 1099 and 1100 pass, with all four complete logs reviewed and zero final warnings. Integration passes all 187 host commands: 174 helper controls, six profiler commands, strict orchestration Clippy, both unit selections, formatting, dependency policy, Markdown and diff checks. All 76 original source signatures and transitive dependency closure pass. The fresh structural audit finds all 3,196 code files below 1,000 lines and missing_docs gates at all 98 detected crate roots; this does not replace semantic authority review.
Original Integration CI 1823 and 1824 are queued. The isolated coordinated image build and configured-client VM are running. Its native result, older preparation/startup regressions and the separate positive NeverExecuted accounting capture remain pending. The observer's two positive host transcripts and twenty negative cases establish verifier behavior only. No new checklist acceptance or progress credit is claimed. Remaining authority/lifecycle work, full CI, native frame proofs, external Rust/LLVM/toolchain rebuilding and both complete EriX builds inside EriX remain required.
Measured host test compilation accepted — 25 September 2026: signed Exsh ef26d89c shares nine borrowed parser adapters across eighteen library test modules and four runtime fixture setup bodies. No allocation, global state or authority is added.
Matching library compiler diagnostics reduce Parser::run specializations from 166 to 2 and command duration from 250.624 to 75.908 seconds; both exact optimized library binaries pass 507 tests. Matching binary diagnostics reduce command duration from 135.869 to 107.280 seconds; both exact optimized binaries pass 480 tests. These are single instrumented host observations, with nested timings kept separate; no full-workspace or native speedup is claimed. Reproduction and interpretation records the unchanged compiler, inputs and diagnostic limits.
All fourteen ordinary development/release selections now compile and pass 988 tests each with the original two Cargo jobs, LTO, 600-second hard/120-second inactivity bounds and 64-MiB output bound. Formatting, fourteen strict host/native build, Clippy, doctest and private-rustdoc configurations and 355 frame-checker controls pass without warnings. Current original CI289, CI290 passes 988 unit tests and 355 checker controls per run; all four complete logs are reviewed with zero warnings. CI still fails the existing incomplete native frame proofs, tracked in issue 4. Its runtime/all observations retain the earlier 256/101 and 287/68 reached/unresolved counts. No unchanged CI run was restarted.
The scoped compiler regression in issue 9 is resolved. Earlier silence failures, the superseded partial candidates and their cleanup receipts remain retained. This test-only refactor adds no runtime feature needing a new VM scenario; the previously accepted native image remains bound to its exact source graph. Full CI closure, remaining authority/lifecycle work, external Rust/LLVM/toolchain rebuilding and both complete EriX builds inside EriX remain required. The phase checklist now has 418/878 completed sub-items, 17/460 accepted parents and 15.45% weighted progress.
Valid counts independently exhaust each free pool, require exact RESOURCE_EXHAUSTED and unchanged Guarded/Sealed peers, then allow normal configuration.
The client VM and older preparation/startup VMs pass with every original marker, native exit and 120/45-second gate. Retained client evidence contains 109 artifacts and 57,045 serial bytes, with empty QEMU stderr and zero image warnings. Independent BootConfig decoding verifies 2 realm records, 4 client records and 576 plan bytes; packaged Procd/Pagerd layouts retain 38 records and 102 bindings. Requests add no capability or guest inspection route.
The phase checklist now has 417/877 completed sub-items, 17/460 accepted parents and 15.43% weighted progress after exact recalculation. This accepts the two configuration-storage ceilings. Existing compiler/frame gates, supervisor loss, partial cleanup, NeverExecuted accounting, complete CI review, external Rust/LLVM/toolchain rebuilding and both full EriX builds inside EriX remain required. All earlier failures are retained, and no unchanged CI job was rerun.
Original CI1799 and CI1800 are fully reviewed: 372/492 and 371/492 scenarios pass, with six complete logs and zero warning candidates. Both retain 119 obsolete policy refusals and the known configuration-carrier stall on their older graph. The pipeline descriptor scenario passes in 1799 and fails in 1800 on the same source graph, reproducing open Integration issue 91. Its cause remains unproved; a companion pass does not resolve it.
Exact RESOURCE_EXHAUSTED replies must preserve the original Guarded mediator and Sealed peer, then allow normal configuration. Requests transfer no capabilities; every existing byte-I/O, actual exit, retirement and reuse gate remains required.
The preceding probe fails at call 22 in an independent 111-call transcript. Eight focused controls and seven development selections of 988 tests pass. Fourteen strict host/native build, Clippy and rustdoc configurations and 355 frame controls pass without warnings. Seven release compilations retain their output-silence failure. Four native frame reports are incomplete; two further runs exit 1 without reports near the checker's 60-second bound. Those observations overlapped the host matrix; the outer owner did not time out. Original Exsh CI287/288 passes 988 unit tests and 355 checker controls, then emits all four incomplete reports per run: runtime 256 reached/101 unresolved and all-feature 287/68. All four complete logs are reviewed with zero warnings. None accepts the compiler or frame gates tracked in Exsh issue 9 and issue 4.
A separate built-in timing diagnostic completes in 250.623833 seconds without warnings and its exact executable passes 507 optimized library tests. Rust reports 115.623711 seconds in LLVM optimization and 108.817139 seconds in fat LTO. The complete LLVM trace attributes 76.09% of inclusive function-pass time and 65.88% of machine-function optimization time to Parser specializations, with 166 run specializations before LTO and 158 in the machine-function trace. These classes are nested and not additive. Instrumented library-only timings identify a refactoring candidate; they do not establish an ordinary-build speedup or accept the release gate. The exact installed compiler uses explicitly selected diagnostic switches only; maintained configuration is unchanged.
All 187 Integration host commands, 76 original signatures and complete catalog closure pass without warnings. The full 2,657-page manual and all 45 document tests pass; all 491,619 word bounds and three viewed pages pass with no final warnings. Original Docs CI1095/1096 also passes; all four complete logs are reviewed through the final warning-free TeX pass. Fresh native execution with the original markers and 120/45-second limits remains required. This checkpoint adds no checklist credit. Supervisor loss, partial cleanup, NeverExecuted observation, complete CI review, external toolchain rebuilding and both full EriX builds inside EriX remain open in the phase tracker.
Native full-table realm refusal accepted — 25 September 2026: signed Integration bdd04a62 runs the new Exsh bc5cc8ac probe. The added requests transfer no capability and use the original authenticated Launchd route.
All original client markers, native exit and 120/45-second limits pass. The 109 retained artifacts include 57,045 serial bytes and empty QEMU stderr, with zero image warnings. Independent BootConfig decoding follows the actual Launchd filesystem role to its 2-realm/4-client/576-plan-byte policy; packaged Procd and Pagerd layouts retain 38 records and 102 bindings. The original preparation-only and startup VMs also pass, with 108 retained artifacts each, 56,131/56,165 serial bytes and zero warnings. No guest inspection endpoint, grant or deadline change is introduced.
All 187 Integration host commands, seven 987-test Exsh development selections, fourteen strict host/native build/Clippy/rustdoc configurations and 355 checker controls pass. Docs CI1091/1092 passes the complete manual and 45 tests without final warnings. Exsh CI283/284 passes 987 unit tests and 355 checker controls, then fails the existing native frame proof: runtime 256 reached/101 unresolved and all-feature 286/68 in both profiles. All four complete logs contain zero warning candidates. Seven local release unit compilations and the native frame gaps remain open under compiler issue 9 and frame issue 4.
Documentation status is signed and pushed as Exsh 232e6849, Docs e2131e57, Integration c5958f12. Only ROADMAP changes in those follow-ups; code, catalog, helper and manual inputs retain their original validation identity. The phase tracker now records 416/876 completed sub-items, 17/460 whole parents, and 15.43% weighted progress after recalculation. This accepts the realm-record ceiling only. Client/plan exhaustion, supervisor loss, partial cleanup, NeverExecuted accounting, complete original CI review, external toolchain rebuilding and both full EriX builds inside EriX remain required.
Realm-capacity witness checkpoint — 25 September 2026: signed Exsh bc5cc8ac requires a third BEGIN to return canonical RESOURCE_EXHAUSTED while both selected realm records are occupied. The reply must be Unconfirmed with zero identity and receiver fields, and both original generations must still read as sealed. Every original byte-I/O, native exit, independent retirement, stale-selector and record-reuse check remains required. The three additional requests use the existing Launchd route and transfer no capability. The independent 99-call transcript rejects the preceding probe at its missing request; seven focused controls cover exact refusal, malformed replies, transport loss and unwanted receipts.
Seven development selections pass 987 tests each. All fourteen host/native build, strict Clippy and private-rustdoc configurations and 355 frame-checker controls pass without warnings. Seven release unit compilations retain the original silence failure, and six current native frame observations return incomplete reports with exit 1. Compiler issue 9 and frame issue 4 stay open. One bounded read-only compiler stack sample finds active LLVM inlining; it does not establish time attribution or a speedup. Original red-selector and Markdown-wrapping failures remain preserved.
Signed Docs e2d4ffc1 records the contract and reconciles resolved grant regressions. All 45 document controls pass; the complete 2,655-page manual builds without final warnings, all 491,488 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI1091/1092 passes, with four complete logs reviewed through the final warning-free TeX pass.
Signed Integration bdd04a62 selects both original sources. All 174 helper and six profiler commands, strict orchestration Clippy and both unit selections, formatting, dependencies and Markdown pass: 187 commands, zero warnings. Both catalog policies, all 76 original signatures and complete transitive closure pass. The fresh structural audit covers 3,194 code files below 1,000 lines and 98 crate roots enforcing missing_docs; semantic authority closure remains separate. Fresh native capacity execution is pending with the original 120/45-second limits. No completion credit is added before that evidence.
Earlier guarded-fixture CI1797/1798 each passes 372/492 scenarios, including admission, preparation, startup and ext4 quota. All 120 failures are classified: 119 obsolete policy refusals tracked in Integration issue 96, and the original counted grant refusal resolved in Loaderd issue 5. Six complete logs total 25,636,311 bytes with zero warning candidates. No unchanged job was rerun; the later fixes still need their own full CI. Remaining supervisor loss, exhaustion/cleanup, external toolchain rebuilding and both complete EriX builds inside EriX remain required by the phase tracker.
Guarded preparation uses the actual Posixd root with its required immutable layout, and actual private mediators reach readiness and retire independently.
The configured-client VM now passes all three inherited markers, then its first PREPARE_REALM_CLIENT request 34 (opcode 0x6d7) returns INTERNAL (5). The original failed run retains 109 artifacts and 56,226 serial bytes, with zero build-warning candidates and no process-owner cleanup failure. Loaderd issue 5 records the separate defect: the counted Launchd client producer selects its own grant column, while Loaderd's intake, handler and reply retain legacy fixed destination 645. Two independent actual-code tests reproduce intake refusal and reply redirection. A correction must preserve the exact original client destination while retaining legacy destination, source receipt, actual caller, relation and cleanup gates.
The mediator-fixture correction is demonstrated in both prerequisite VMs; Exsh issue 10 remains linked to full configured-client validation. No client execution, configuration/seal/byte-I/O acceptance, managed-row reuse, profiler observation or full guest build is claimed. Original Exsh CI281/282 is running, and original Integration CI1797/1798 is queued; earlier original Integration cohorts remain under observation. Exsh compiler/frame gates remain open, and no unchanged CI was restarted. These repairs add no canonical checklist credit.
All 174 Integration helper commands and six strict profiler commands pass. Sixteen selector combinations include preparation-only packaging and admission-only exclusion; actual private filesystem aliases still require exact artifact and runtime-graph identities. Seven Exsh development selections pass 986 tests each, fourteen host/native builds, strict Clippy and private-rustdoc configurations pass, and all 355 frame-checker controls pass without warnings. The initial changed wire-test byte count and documentation wrapping failures are corrected with original receipts retained. The unchanged Integration orchestration retains four strict 320/321-test matrices. No Loaderd check, capability right, sidecar rule or guest deadline is relaxed.
Seven Exsh release unit-test compilations still reach the original silence limit and all six native frame observations remain incomplete; compiler issue 9 and frame issue 4 stay open. Fixture regression 10 preserves both original failed VMs. Fresh corrected preparation-only, older startup and configured-client VM execution remains required. These component checkpoints earn no new acceptance credit; complete authority closure, managed-row reuse, profiler observation, external toolchain rebuilding and both full EriX guest builds remain open.
Exsh regression 10 records the canonical bug report and correction criteria.
The guarded fixture selects
bin/true, but the actual packaged Coreutils root has no loaded immutable realm layout. The packaged Posixd root has exactly one read-only, non-executable layout descriptor. Loaderd correctly refuses the ordinary executable as a mediator. The correction selectsbin/posixdand includes explicit private packaging for preparation-only images; it must preserve the strict layout gate, borrowed cwd scope and original 120/45-second guest deadlines. Exsh endpoint 0x520 exits E5; that observation does not attribute this failure to Launchd's process-event path.Both original source graphs, command statuses, serial logs and image artifacts are retained. There are zero image-warning candidates and no process-owner cleanup failure. Fresh preparation, startup and configured-client VM validation is required. This failure earns no checklist credit; complete authority closure, managed-row reuse, profiler evidence, the external toolchain rebuild and both complete guest-build generations remain open.
It freezes complete plans, requires two-sided seal and actual Exited/zero outcomes, checks retained outcomes after retirement, retires realms independently and exercises replacement clients with stale-handle refusal.
Seven development selections pass 986 tests each. Fourteen host/native build, strict Clippy, doctest and private-rustdoc selections and all 355 frame-checker controls pass without warnings. All seven release unit-test compilations reach the original 120-second silence limit before execution; compiler regression 9 remains open. Three optimized diagnostic artifacts build, but six native frame observations remain incomplete; frame regression 4 remains open. Original CI279 and CI280 fail the existing native cleanup-frame proof gate. All four complete logs are retained (322,890 bytes, zero warning candidates). Each original runtime profile reaches 256 functions with 101 unresolved observations; each all-feature profile reaches 286 functions with 68 unresolved observations. Workspace mapping and fallback frames are proved, but direct routes and ordinary source-frame membership remain incomplete. The 507 library tests, 478 binary tests, one doctest and all 355 checker controls pass. No unchanged run was retried. This is a WIP checkpoint: no release-test, frame or VM gate is waived, and host tests do not establish native I/O or either complete guest build.
It requires two simultaneously ready realms, independent retirement and both stale-handle refusals.
Original exact-source CI runs 277 and 278 both fail the existing cleanup-frame gate. Their four complete logs contain zero warnings. Runtime profiles reach 256 functions with 101 unresolved observations; all-feature profiles reach 259 with 69 unresolved observations. Entry-local frames are 6,864 and 6,880 bytes against 8,192, fallback is complete at 48/33,792, and workspace mapping is complete; these partial measurements do not establish the full frame proof. See frame regression 4 and release compilation regression 9. Local frame attempts separately retain empty reports after successful disassembly. Guest execution, configuration/seal, mediated client I/O and complete guest rebuilds remain unproven.
Detailed scope and contracts
Dependency adoption frame evidence — 15 September 2026
Dependencies identify required contracts and closure gates; preparatory inventory/design can proceed in parallel under one owner per edited file. Link bounded implementation issues and their PRs here before claiming acceptance.
Close criteria only with their own reviewed deliverables and validation evidence.
Native diagnostic observation — 19 September 2026: the first actual caller VM fails before its required success marker.
No unchanged retry or successful runtime acceptance is claimed.
A matching fixed-server VM is required to establish the correction.
Signed cleanup refinement — 19 September 2026:
9c0f7ab851d527dd9dd10161d6a98e1fdc14598emakes no stdout IPC after uncertain capability disposal. A fresh matching VM with the signed Launchd correction remains required for Integration issue 66.The actual VM passes all eleven admission calls over the shell's existing private script route: reservation, reads, full-width stale-generation rejection, missing-scope refusal, acknowledged retirement, record reuse and stale-abort rejection.
Successful preparation, mediator configuration/readiness/sealing, client byte I/O, complete source/effect/frame proof, native Rust/LLVM rebuilding and both full EriX builds remain required. This partial lifecycle acceptance adds no whole checklist item.
The new diagnostic will reserve a record, transfer exactly one SEND-only copy of its explicitly supplied startup cwd to the BEGIN-reserved receipt slot, select
bin/truewithin that initial root scope, require PREPARE/Guarded and READ/Guarded, then require ABORT/Retired and a stale READ/NOT_FOUND.No ordinary start, new endpoint, root capability or implicit namespace is introduced. Launchd must retire its received directory copy after exact resolution; Loaderd must return the original staged child and grant, and Procd must retain the actual returned grant and guarded sender branch before acknowledging Guarded. Abort must retire that exact stage and retained custody. Error telemetry must preserve application refusal codes and stop ordinary output after uncertain receipt disposal. The new actual VM retains the 120-second hard and 45-second progress limits and requires its own unique marker before ordinary shell exit. Full source/effect/frame proof, configured/sealed mediator execution, real client byte I/O, native Rust/LLVM rebuilding and both full EriX builds remain required.
The actual VM passes the eleven existing admission calls followed by BEGIN/Reserved, PREPARE/Guarded, READ/Guarded, ABORT/Retired and stale READ/NOT_FOUND. It transfers exactly one SEND-only copy of the explicitly supplied initial cwd to the authenticated reservation and selects
bin/trueinside that scope. The existing private Launchd route is reused; no new endpoint, root grant or implicit namespace is introduced.Eight actual frame observations retain complete workspace mapping but incomplete 97/63/100/100 runtime/all/admission/preparation proof in both policies; the full frame gate remains required.
Complete typed mediator bootstrap, readiness/configuration/sealing, real client byte I/O, complete source/effect/frame proof, native upstream Rust/LLVM rebuilding and both full EriX build generations remain required.
Original guarded-preparation CI — 19 September 2026: Exsh run 271 and 272, for signed
ffe50612889dd58a45a40d04593a4aa3a3ffa512, both fail the required complete frame proof. No workflow was rerun or cancelled to obtain acceptance.Catalog regression 68 remains open until the remaining Exsh selection and complete original catalog are validated together. Individual repository success is not full service-image acceptance.
The complete source/effect/frame gate also remains open.
Canonical acceptance remains 15/460 leaves, 3.48% weighted. Full service lifecycle, terminal accounting, source/effect/frame proof, the 128-page Pagerd gate, profiler attribution, native external Rust/LLVM/runtime rebuilding and both full EriX-in-EriX generations remain required. Static audit currently passes 3,150 authored code files below 1,000 lines, 74 manifests, 259 explicit Git pins, 172 direct missing_docs gates and 92 conventional Rust roots; full semantic authority and documentation review remain open.
Corrected-source original CI 1695/1696 is running; bug 68 remains open pending that observation and full consumer acceptance remains separate.
These local and CI artifacts are distinct; no frame or release-unit acceptance, relaxed deadline or unchanged retry is claimed.
Canonical acceptance remains 15/460 leaves, 3.48% weighted. Full consumer lifecycle, terminal accounting, source/effect/frame proof, the 128-page Pagerd gate and profiler attribution remain required; no canonical leaf closes at this checkpoint.
The WIP PR awards no complete runtime or self-hosting acceptance. Actual service CPU/profiler VMs, complete authority/source/effect/frame proof, native external Rust/LLVM/runtime rebuilding and both full EriX guest build generations remain required in Phase 6 completion.
Each passes 976 unit tests and 355 checker controls before the required frame gate fails.
Complete frame issue 4 and local release compiler issue 9 remain open.
Original native stream identities — 30 September 2026
Ordinary namespace and executable routes cannot allocate one.
Original event times remain Unknown; this scalar metadata cannot turn an incomplete observation into successful compatibility status.
They cover literal wire rejection, atomic encoding, administrator isolation, lost-delivery allocation, binding refusal, exhaustion, directional lifetime, teardown/reuse, original ownership, malformed observations and receipt cleanup.
The full status/directory feature remains open for original native event-time capture, complete FAT metadata and whole-feature integration. Both full EriX guest build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.
Original native stream event times — 30 September 2026
Alias creation, metadata queries, empty or refused operations and terminal device progress do not query a historical clock.
Ttyd receives an exact authenticated SEND-only Timed endpoint for this source purpose; Launchd uses its already admitted endpoint. Clean refusal remains Unknown.
The seeded boundary control retains the whole original object and proves the intended no-clock refusal contract when executed; no runtime reproduction or practical path to 2^64 bytes is claimed.
They cover source-event independence, unknown evidence, full-range dates, malformed replies, receipt cleanup, exact SEND-only admission, alias/retirement/reuse and overflow refusal. The existing realm workload now requires successful inherited fstat and original PTY clock evidence with stable birth before and after realm retirement; its independent transcript remains 385 calls.
The full status/directory feature remains open for complete FAT metadata and whole-feature integration. Both full EriX guest build generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.
Related records and contracts
[FEATURE] [P12] Complete native shell/build utilities and provide help and offline manual pagesto [FEATURE] Complete native shell/build utilities and provide help and offline manual pageserikinkinen referenced this issue2026-09-12 15:07:27 +02:00
78691e67 adds built-in
helpwith a shared 33-topic registry, topic/pattern selection and-d,-m,-soutput. It uses the active command’s streams and requests no filesystem authority. The help contract documents Exsh’s actual behavior, including mixed-match statuses and function precedence.