feat: release native transparent session filesystem preview - #1
Merged
Conversation
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.
CodexFold v0.3.0-beta.1
This release turns the transparent session filesystem work into a versioned,
reviewable preview. The storage engine remains local-first and byte-exact. On
macOS, the terminal architecture is an Apple-native Swift FSKit extension
connected to the Go daemon over a capability-negotiated Unix-domain-socket
protocol.
Highlights
deltas.
read-ahead, generation invalidation, and stale-size repair.
tails between parent and child sessions.
macOS Canary Evidence
The signed local build 102 candidate passed an isolated Apple-native FSKit
Canary without routing the production Codex home or production SQLite state.
Release source metadata is
0.3.0 (103): build 103 completed a signed Releasebuild and nested Host/extension signature verification. Its FSKit behavior is
unchanged from build 102, so the mounted and real-client evidence below remains
attributed to the exact candidate that produced it.
0.145.0-alpha.30resume, history use, tool execution,and append passed.
26.715.72359+5718resume, send, fork, child continuation,archive/unarchive, and restart passed.
expected native or reconstructed forms.
fs doctorcomponents were healthy after the final host restart.cold-read ratio gate of
0.70and warm-read ratio gate of0.80.0.762,2.042,0.800,1.761, and0.941;warm ratios were
0.954,1.011,0.963,0.993, and0.981.164,688 KiB, below the256 MiBbound.5.96 GiB/sand
17.73 GiB/s; FSKit append plusfsyncmeasured5.21 msp50,9.51 msp95, and19.71 msp99. These are observations, not guaranteedthroughput on other machines.
Install the CLI
This prerelease changes the canonical module path. Install it explicitly:
GitHub Release archives contain the default storage-oriented CLI for macOS,
Linux, and Windows on
amd64andarm64, pluschecksums.txt.FSKit Source Build
The FSKit App is intentionally not attached as a public binary. The validated
candidate is signed with a maintainer Apple Development identity, not a
Developer ID distribution identity, and is not notarized for general use.
Build the App from
platform/darwin/fskitwith Xcode 27, XcodeGen, an eligibleApple development team, and isolated test paths. Follow the maintainer guide
and macOS Canary report before enabling any route.
Readiness Boundary
This is a preview release, not permission to delete native session sources or
bulk-enroll a production Codex home. Production promotion still requires:
capability claim.
The complete evidence and limitations are documented in
docs/validation-macos-canary.md,docs/validation-linux-fuse3.md, and thetransparent filesystem product contract.