DatCaptainHorseandClaude Sonnet 5.5
3149a9d4b1
The boot descriptor gains `images`: read-only EROFS images mounted on their own, with no writable layer over them. nesinit mounts them first, before overlays and shares, with the same nosuid/nodev guards every layer has and without noexec because what is in one is run. CONTROL_VERSION moves to 5: the descriptor refuses fields it does not know, and a guest image without Proton is useless to a host that does not send one, so the mismatch is named at the handshake. The guest rootfs no longer contains Proton. The checks that used to guard the in-image copy (every library its programs and Wine's core link, an interpreter behind the entry point) move to a compat_check stage that verifies the Proton named by PROTON_IMAGE and leaves a marker in the image saying which one. The leaf stages copy that marker out of it so the stage cannot be skipped as unused. With nothing at a Proton path, a box started without one fails saying where it looked. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
crates/
Shared Rust: a library another crate in this repo depends on. A binary someone
runs goes in apps/; shared JS/TS goes in
packages/. The split is by what a thing is, not by what
language it is written in — same rule on both sides of the repo.
Empty today. Components move here one at a time as they are opened.
Two rules
Every version is pinned in the root Cargo.toml. A member writes
tokio.workspace = true and never a version, so two crates in this tree cannot
disagree about a dependency.
Nothing here may depend on anything closed, or name it. This repo is public. A crate that needs a private component is in the wrong repo, and a comment explaining who calls this wants a category noun — "the caller", "a supervising agent" — rather than a name. The requirement is the interesting part; who currently satisfies it is not.