charly
| Version | 2026.162.1430 |
| Repo | superproject |
The full charly toolchain on a deployment — the on-PATH charly CLI plus its composed VM / encrypted-storage / console-relay stack.
Full charly toolchain — the CLI binary + the VM stack (virtualization),
encrypted storage (gocryptfs), and console relay (socat) — composed into
ONE layer that works identically on container/pod, host/local, and
bootc/VM targets via the virtualization layer’s mixed-entry service:
pattern. This is the single canonical charly layer: bake it where a
deployment needs a persistent on-$PATH charly or the full toolchain inside
(the charly-mcp server, the *-charly showcases, nested-pod orchestrators).
Images that only need transient in-container charly (the dbus delegation
path) need NOT bake it — the host copies charly in on demand
(EnsureCharlyInDeployVenue; see /charly-tools:charly).
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
check |
the charly binary resolves on the deployment’s PATH |
check |
charly version prints a CalVer build stamp on stdout |
check |
the gocryptfs encrypted-storage binary (gocryptfs candy) is installed |
check |
the socat console-relay binary (socat candy) is installed |
check |
the libvirt virsh client (virtualization candy) is installed |
check |
the qemu system emulator (virtualization candy) is installed |
check |
charly doctor runs and emits its Summary line |
check |
command=command -v charly |