Super reads $XDG_CONFIG_HOME/super/fleet.json, or $HOME/.config/super/fleet.json when the XDG path is unset, empty or relative. This follows the XDG base-directory specification. Settings are local operator configuration, not a world record or a webview input. Create the file privately (mode 0600) with absolute paths:
{
"schema": "super-device-fleet@1",
"snapshotPath": "/absolute/path/to/collector/snapshot.json",
"checksConfigPath": "/absolute/path/to/restricted-check/config.json"
}The existing collector owns and atomically updates the snapshot. The check configuration still pins the approved target, key and known-hosts file; this settings file neither enrolls a host nor grants execution or acceptance. The app reads settings at launch. Restart after changing them.
SUPER_FLEET_SNAPSHOT and SUPER_FLEET_CHECK_CONFIG independently override saved settings. An explicitly empty variable disables that feature for the launch; an invalid explicit path does not fall back to the saved configuration. Missing, malformed, unsupported or relative saved paths leave the relevant feature unconfigured. Configuration files are bounded when read.
Isolated native test sessions receive their own XDG configuration directory; explicit fixture environment paths remain supported. Real-world verification must stop the app and take the usual locked backup first.
A read-only inspection on 2026-09-14 confirmed FreeBSD 15.1, Wifibox PID 4153, 457 GiB available in zroot, no host IP forwarding, and grub2-bhyve installed. UEFI firmware was absent at the standard package path. No separate Super guest exists. Preserve Wifibox, tap0 and the current management route.
Next: provision a distinct Linux guest, boot firmware, storage and an isolated network with a tested return path. Do not reuse Wifibox's VM or passed-through Wi-Fi hardware. Consult the official FreeBSD virtualization handbook. Guest creation and a physical network-outage drill are not yet completed.
Superseded 2026-10-11: the guest state and next step above, recorded on 2026-09-14, are out of date. The cd-floor-01 bhyve Linux guest super-worker-02 is enrolled; its checks run through the root-free jump row (T49, R103, R181), and its first advisory check from the installed cockpit passed on 2026-10-10 (E2, 14 of 14 tests). Wifibox stays separate: preserve Wifibox, tap0 and the current management route, and do not reuse Wifibox's VM or passed-through Wi-Fi hardware. The physical network-outage drill remains open.