internal/

Package backend defines the interface for VM backends.

Package control is the client half of the holder protocol: it spawns a holder process, waits for its members to come up, and queries or stops them over the per-member unix sockets.

Package dhcp parses macOS dhcpd_leases file to discover VM IP addresses.

Package fetch downloads and caches remote files (cloud images, VMM binaries, firmware), verifying an optional SHA256 and writing atomically so a cached file is always complete.

Package fixture packs a host directory into a read-only ext4 filesystem image for attaching to a VM as a block device (ADR-0015).

Package helperdist resolves the signed fleetbox-helper binary the darwin client drives: it returns a locally pre-staged helper named by the FLEETBOX_HELPER environment variable, or downloads the checksum-pinned helper for this platform into ~/.fleetbox/bin, strips its Gatekeeper quarantine, and makes it executable.

Package holder is the server half of the holder protocol: one process owns one orchestrator.Cluster — its shared network and every VM on it — so a cluster gets the same VM↔VM connectivity the library StartN gives (ADR-0008).

Package image handles cloud image download, verification, and conversion.

Package opts holds the backend-neutral VM creation options and their serialization across the helper-process boundary.

Package orchestrator owns the VM lifecycle: it resolves the per-call dependencies (store, SSH key, image, backend), creates the backend network, and boots, waits for, and tears down VMs.

Package seed creates cloud-init NoCloud seed ISOs.

Package sshkey manages SSH key generation and provides an SSH client for VM access.

Package store manages VM state directories under ~/.fleetbox/clusters/<cluster>/<member>/.