WO-1 CLOSED: MIRI clean on ARM64, add #[cfg(not(miri))] to latency benchmark
hunt+1: Claude Sonnet 5
90b2297
ARM64 (Graviton t4g.small) results:
- cargo build: clean
- 9/9 tests pass natively; mean round-trip latency 0.065 μs (770× under 50 μs target)
- MIRI: 7 pass, mmap test correctly ignored (MIRI cannot exec mmap syscall),
latency test was the only "failure" — MIRI is ~1000× slower than native by design
Fix: add #[cfg(not(miri))] to test_round_trip_latency so MIRI runs cleanly.
No undefined behavior found. Lock-free ring buffer is correct on both x86-64 and ARM64.
WO-1 is complete. WO-2 begins next.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add ARM64 automation scripts — close WO-1 without AWS console interaction
hunt+1: Claude Sonnet 5
fa3c794
scripts/aws-setup.sh: one-time credential setup using read -s (silent prompts);
writes ~/.aws/credentials via aws configure, verifies with sts get-caller-identity,
accepts PEM key via stdin cat redirect to ~/.ssh/beryl-aws-key.pem, auto-discovers
running t4g.small IP and saves to ~/.miranda-ec2-ip
scripts/provision-ec2.sh: launches t4g.small if none exists; imports SSH key pair,
creates security group (SSH from current IP only), finds latest AL2023 ARM64 AMI,
bootstraps Rust install + git clone via user-data
scripts/arm64-verify.sh: full ARM64 verification — SSH in, git pull, cargo build,
cargo test -p miranda-ipc --nocapture, MIRI check; all output pasted back locally
tasks.md T7: updated ARM64 section to reference scripts + clarify this does not
block WO-2; WO-2 can start in parallel with the ARM64 gap being closed
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
