plugin-cardwire
| Version | 2026.243.0001 |
| Repo | box/github.com/opencharly/plugin-cardwire:v2026.243.1202 |
| Plugin | yes — see the plugin reference |
OUT-OF-TREE charly COMMAND-class plugin for the cardwire GPU-manager surface
(ogc/cardwire — the Open Gaming Collective’s eBPF/LSM GPU-blocking daemon,
CachyOS/Arch first): command:cardwire (status | list | config | gpu status is a deterministic, GPU-less-graceful host
report: the cardwired systemd state, the /etc/cardwire/cardwire.toml
whitelisted keys (auto_apply_gpu_state / experimental_nvidia_block /
battery_auto_switch / battery_auto_switch_mode /
external_display_auto_switch) and the BPF-LSM facts read DIRECTLY from
/sys/kernel/security/lsm (the same canonical reads plugin-bpf’s status
performs — R3: one canonical surface, no ad-hoc copies, no shelling out to
charly bpf; the plugin is self-contained). list parses the REAL cardwire
list –json shape (the two-GPU fixture captured in the Phase-0 spike:
Virtio 1.0 GPU id 0 + NVIDIA GeForce RTX 4080 SUPER id 1) into stable
keys, N/A-graceful when cardwire is absent (exit 0 — the host-independent
check-cardwire-local bed assertion), exit 1 only on a REAL failure of an
installed cardwire. config get|set <key> [value] reads/writes the toml
atomically (tmp+rename, mirroring cardwire’s own approach). gpu <id> block|unblock is the MUTATING enable/disable surface: it forks
/usr/bin/cardwire, then VERIFIES the blocked flag actually flipped via
cardwire list –json (the daemon enforces mode-dependent semantics;
verification is the honest contract) — cardwire UNAVAILABLE → exit 1 (a
mutating surface refuses, never pretends). manager status passes through.
This candy carries NO install content: the CachyOS/Arch install plan lives in the sibling candy/cardwire-install candy (the ONLY install surface), keeping the check-cardwire-local R10 bed’s host deploy NON-MUTATING (R1: the in-plugin-candy install executed on the operator host during the local bed’s deploy-add). The check-cardwire-vm bed (opencharly/distro-cachyos, goal task 4) composes both candies.
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 cardwire plugin ships a buildable Go module the host can build + fork/exec; the deterministic end-to-end (status / list / config exit-code contracts) is exercised by the check-cardwire-local bed in opencharly/charly |