Add a small validation path for running scoutd in a real Firecracker guest environment. This can begin as a manual harness, but it should prove the real behavior of the guest init path rather than relying only on isolated unit tests.
The goal is to validate that scoutd mounts the guest filesystems, brings up networking, fetches MMDS, launches a workload, reports status, and powers the guest off correctly.
Why
PID 1 behavior and guest boot logic are hard to trust from unit tests alone. This repository needs a real guest validation path.
In scope
- local harness for Firecracker guest testing
- booting scoutd in a real guest
- validating the guest startup path end to end
Add a small validation path for running scoutd in a real Firecracker guest environment. This can begin as a manual harness, but it should prove the real behavior of the guest init path rather than relying only on isolated unit tests.
The goal is to validate that scoutd mounts the guest filesystems, brings up networking, fetches MMDS, launches a workload, reports status, and powers the guest off correctly.
Why
PID 1 behavior and guest boot logic are hard to trust from unit tests alone. This repository needs a real guest validation path.
In scope