Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…resolution

Add EnableBoostChannel *bool to CreateSandboxOpts (nil = use daemon default)
and defaultBoostChannel bool to SandboxService / NewSandboxService. Both Create
and CreateFromSnapshot resolve the option at create time and persist it onto
domain.Sandbox; handleCreate threads EnableBoostChannel and SandboxID through to
domain.CreateSandboxRequest so the provider can bind the boost socket. All
NewSandboxService call sites updated to pass false for now; Task 11 will swap
cmd/navarisd/main.go to cfg.boostChannelEnabled.

Default Source to "external" when empty; propagate to EventBoostStarted,
EventBoostExpired, and EventBoostRevertFailed payloads. Pass Source:
"external" explicitly from the operator HTTP handler. Tests cover both
explicit in_sandbox and default-external paths.

Implements BoostHTTPHandler which serves a minimal HTTP/1.1 API over
per-sandbox connections (net.Conn). Reads one request via http.ReadRequest,
dispatches to BoostService (POST/GET/DELETE /boost) or SandboxStore
(GET /sandbox), writes one response, closes the conn. Rate-limits per sandbox
via the token-bucket RateLimiter from Task 6 with flat per-conn accounting.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Add a per-VM unix-socket listener that accepts guest-initiated vsock
connections on <vmDir>/vsock_1025 (or <vmDir>/root/vsock_1025 with
jailer) and dispatches each connection to the BoostHTTPHandler via the
boostServer interface. The interface decouples the firecracker package
from internal/api to avoid cyclic imports.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…er wiring

Add --boost-channel-enabled (default true) and --boost-channel-dir flags to
navarisd; swap the hardcoded false in NewSandboxService to cfg.boostChannelEnabled;
pass cfg.boostChannelDir into incus.Config.BoostChannelDir.

Introduce provider.BoostServer exported interface in internal/provider/boost.go so
both the firecracker and incus providers can expose SetBoostHandler(provider.BoostServer)
without importing internal/api (which would violate layering). After boostSvc and
BoostHTTPHandler are constructed, main.go walks the builtProviders slice and calls
SetBoostHandler via a local boostHandlerSetter interface assertion.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Add RestartBoostListeners (FC) and RestartBoostChannel (Incus) to replay
boost listeners for surviving VMs/containers after a daemon restart.
Wire both replay calls in main.go after SetBoostHandler is wired, fixing
the silent no-op that would occur if called inside recover().

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…k 502 not file presence

The agent's RunBoostProxy always creates /var/run/navaris-guest.sock inside
the guest regardless of host-side opt-out, so the file-existence assertion
was wrong. With EnableBoostChannel=false the host-side vsock_1025 listener
isn't created, the proxy's vsock.Dial fails, and the proxy returns 502 —
that's the right behavioral indicator.

Previous commit edited the wrong Dockerfile — Dockerfile.navarisd is for
Incus paths; FC compose uses Dockerfile.navarisd-firecracker. Adding curl
to both the alpine and debian rootfs builds so the boost-channel tests
can POST via curl --unix-socket from inside the guest.