[AZ-228] [AZ-229] Add VIO and satellite sync boundaries

Co-authored-by: Cursor <cursoragent@cursor.com>

_docs/03_implementation/batch_06_cycle1_report.md

@@ -0,0 +1,39 @@
+# Batch Report
+
+**Batch**: 6
+**Tasks**: AZ-228_vio_adapter, AZ-229_satellite_service_sync
+**Date**: 2026-05-03
+
+## Task Results
+
+| Task | Status | Files Modified | Tests | AC Coverage | Issues |
+|------|--------|----------------|-------|-------------|--------|
+| AZ-228_vio_adapter | Done | 4 files | Pass | 3/3 ACs covered | None |
+| AZ-229_satellite_service_sync | Done | 4 files | Pass | 3/3 ACs covered | None |
+
+## AC Test Coverage: All covered
+
+| AC Ref | Coverage |
+|--------|----------|
+| AZ-228 AC-1 | `test_valid_synchronized_packet_emits_vio_state` verifies synchronized frame/IMU processing emits a relative VIO state packet. |
+| AZ-228 AC-2 | `test_timestamp_mismatch_is_explicit_validation_error` verifies timestamp mismatch is rejected with an explicit error. |
+| AZ-228 AC-3 | `test_tracking_loss_degrades_health_without_emitting_absolute_position` verifies health reports degraded tracking state. |
+| AZ-229 AC-1 | `test_pre_flight_import_returns_package_for_tile_manager_validation` verifies mission cache packages are exposed for Tile Manager validation. |
+| AZ-229 AC-2 | `test_post_flight_upload_records_retryable_failure_for_audit` verifies upload outcomes are auditable and retryable failures retain packages. |
+| AZ-229 AC-3 | `test_in_flight_sync_is_blocked_without_calling_network_boundary` verifies in-flight sync is blocked before network/uploader calls. |
+
+## Code Review Verdict: PASS
+
+Review report: `_docs/03_implementation/reviews/batch_06_review.md`
+
+## Auto-Fix Attempts: 0
+
+## Stuck Agents: None
+
+## Verification
+
+- `.venv/bin/python -m black --check src tests e2e/replay` passed.
+- `.venv/bin/python -m ruff check src tests e2e/replay` passed.
+- `.venv/bin/python -m pytest` passed: 38 tests.
+
+## Next Batch: AZ-230_satellite_service_vpr_retrieval

_docs/03_implementation/reviews/batch_06_review.md

@@ -0,0 +1,61 @@
+# Code Review Report
+
+**Batch**: AZ-228_vio_adapter, AZ-229_satellite_service_sync
+**Date**: 2026-05-03
+**Verdict**: PASS
+
+## Findings
+
+No findings.
+
+## Review Scope
+
+- Task specs:
+  - `_docs/02_tasks/todo/AZ-228_vio_adapter.md`
+  - `_docs/02_tasks/todo/AZ-229_satellite_service_sync.md`
+- Changed files:
+  - `src/vio_adapter/__init__.py`
+  - `src/vio_adapter/interfaces.py`
+  - `src/vio_adapter/types.py`
+  - `src/satellite_service/__init__.py`
+  - `src/satellite_service/interfaces.py`
+  - `src/satellite_service/types.py`
+  - `tests/unit/test_vio_adapter.py`
+  - `tests/unit/test_satellite_service_sync.py`
+
+## Phase Notes
+
+### Spec Compliance
+
+- AZ-228 AC-1 is covered by `test_valid_synchronized_packet_emits_vio_state`.
+- AZ-228 AC-2 is covered by `test_timestamp_mismatch_is_explicit_validation_error`.
+- AZ-228 AC-3 is covered by `test_tracking_loss_degrades_health_without_emitting_absolute_position`.
+- AZ-229 AC-1 is covered by `test_pre_flight_import_returns_package_for_tile_manager_validation`.
+- AZ-229 AC-2 is covered by `test_post_flight_upload_records_retryable_failure_for_audit`.
+- AZ-229 AC-3 is covered by `test_in_flight_sync_is_blocked_without_calling_network_boundary`.
+
+### Code Quality
+
+The implementation follows the existing Pydantic model style, keeps component logic inside the owning packages, and exposes only public API exports through component `__init__.py` files.
+
+### Security Quick-Scan
+
+No hardcoded secrets, shell execution, deserialization paths, SQL construction, or sensitive credential logging were introduced. The Satellite Service sync boundary explicitly rejects in-flight package exchange before invoking the uploader.
+
+### Performance Scan
+
+No unbounded network path or per-frame heavy retrieval path was introduced. The VIO adapter uses a bounded timestamp-window selection over the provided telemetry samples.
+
+### Cross-Task Consistency
+
+The VIO adapter and Satellite Service sync boundary remain independent batch outputs and share existing DTO/error-envelope conventions.
+
+### Architecture Compliance
+
+Imports respect `_docs/02_document/module-layout.md`: VIO imports only shared public APIs, and Satellite Service imports Tile Manager through the package public API.
+
+## Verification
+
+- `.venv/bin/python -m black --check src tests e2e/replay`
+- `.venv/bin/python -m ruff check src tests e2e/replay`
+- `.venv/bin/python -m pytest`

_docs/_autodev_state.md

@@ -9,6 +9,6 @@ tracker: jira
 sub_step:
   phase: 1
   name: batch-loop
-  detail: "batch 5: AZ-226_generated_tile_orthorectification"
+  detail: "batch 6: AZ-228_vio_adapter, AZ-229_satellite_service_sync"
 retry_count: 0
 cycle: 1