Attempted Path-3 (Full SITL with community images) for the SUT Reality
Gate. Discovered sitl_observer is offline-fixture replay, not a live
SITL client -- compose-file SITL services in environment.md are
aspirational. The real Path-3 needs the fixture builders + SUT CLI
end-to-end, which surfaced 5 additional integration drifts (H-10..H-14)
on top of the prior 9.
Fixes:
- tests/fixtures/calibration/adti26.json: body_to_camera_se3 was a
{rotation_xyzw, translation_xyz_m} dict; runtime_root/_replay_branch.py
loader strictly expects a 4x4 SE3. Identity quaternion + zero
translation = identity 4x4, semantically equivalent.
New files:
- tests/fixtures/replay_config_minimal.yaml: minimal replay-mode config
for harness reproduction (mode=replay, ardupilot_plane defaults).
- .gitignore: e2e/fixtures/sitl_replay/ (generated by build_p0X_fixtures).
Documentation:
- Step 11 report: appended Path-3 attempt section.
- Leftover doc: H-10..H-14 ticket payloads added.
- Autodev state: reflects Path-3 outcome.
Step 11 stays blocked; H-13 (auto-sync AC-8 hard-fails on stationary
fixtures) requires a SUT design decision and cannot be unilaterally
fixed mid-session.
Co-authored-by: Cursor <cursoragent@cursor.com>
Bugs found during Step 11 (Run Tests) functional gate:
1. e2e/docker/docker-compose.test.yml referenced docker/Dockerfile
(doesn't exist). Renamed to docker/companion-tier1.Dockerfile.
2. fdr-output volume declared tmpfs size=64g, which requires actual host
RAM. Docker Desktop on macOS has only ~3.8 GiB; tmpfs alloc fails.
Switched to a plain named volume (the SUT enforces the 64 GB cap
internally per NFT-LIM-02; the volume-layer cap was belt-and-
suspenders only). Documented the overlay2+xfs override path for CI
runners that support it.
3. Added e2e-results/ to .gitignore (runtime output dir created by
the bind-mount).
These bugs predate this session; the harness had never been bench-tested
end-to-end. Surfacing them was the actual outcome of running test-run.
Co-authored-by: Cursor <cursoragent@cursor.com>
Add the initial source, test, infrastructure, CI, configuration, and evidence-path scaffold so dependent implementation tasks have stable package and runtime boundaries.
Co-authored-by: Cursor <cursoragent@cursor.com>
Oleksandr Bezdieniezhnykh