Integration test automation outside Graviton3

[Brad-Edwards]

Problem

All integration/E2E testing requires SSH/SSM into the single Graviton3 instance (i-0739acb344b2a9a51) and manually running scripts/verify.sh. CI cross-compiles and runs unit tests, but never exercises the kernel module, eBPF programs, or daemon against live cheats.

If that instance is stopped, misconfigured, or its AMI drifts, there's no automated gate catching regressions in the integration layer.

Proposal

Options (not mutually exclusive):

1. CI job that boots the Graviton instance, runs verify.sh via SSM, and reports results — partially exists in .github/workflows/ci.yml but needs verification it's wired end-to-end
2. QEMU-based ARM64 integration tests — slower but removes single-instance dependency
3. Docker + kernel module test harness — limited (no real kprobes) but could exercise daemon + mock chardev

Acceptance

• At least one integration test path runs automatically on PR or merge
• Failure in integration blocks merge (or is clearly visible)