diff --git a/_docs/03_implementation/implementation_completeness_cycle1_report.md b/_docs/03_implementation/implementation_completeness_cycle1_report.md
index d92de7d..419cb44 100644
--- a/_docs/03_implementation/implementation_completeness_cycle1_report.md
+++ b/_docs/03_implementation/implementation_completeness_cycle1_report.md
@@ -503,4 +503,56 @@ If either remediation task grows beyond 5 points during decomposition,
 split into infrastructure + estimator-wiring + per-frame-cov-read
 sub-tasks before scheduling.
 
+## Addendum — 2026-05-19 (post AZ-591, AZ-618 umbrella, AZ-687)
+
+This addendum re-runs the gate against the bootstrap work that landed
+between the 2026-05-16 verdict and 2026-05-19. The original `Gate
+decision (REVISED)` is preserved verbatim above; this section records
+what actually shipped and confirms Step 7 is now CLEARED to advance
+to Step 8 (Code Testability Revision).
+
+### What landed since 2026-05-16
+
+| Task | Title | Status | Batch | Notes |
+|------|-------|--------|-------|-------|
+| AZ-591 | compose_root per-binary bootstrap | Done | Batch 66 → archived | Lands `register_airborne_strategies()` plus per-strategy wrappers in `runtime_root/airborne_bootstrap.py`. `_STRATEGY_REGISTRY` is now populated for the airborne binary. Removes the original "compose_root cannot run" blocker. |
+| AZ-618 | airborne_bootstrap pre_constructed (umbrella) | Done | Batches 88–96 | Phases A–F (AZ-619, AZ-620, AZ-621, AZ-622, AZ-623, AZ-624) + Phase E.5 (AZ-625) all archived to `done/`. `build_pre_constructed` populates every key in `AIRBORNE_REQUIRED_PRE_CONSTRUCTED_KEYS`; `runtime_root.main()` wires it through `compose_root`. |
+| AZ-619 | Phase A — c13_fdr + clock seeds | Done | Batch 88 | First two seeds. |
+| AZ-620 | Phase B — c6 storage seeds | Done | Batch 90 | `c6_descriptor_index` + `c6_tile_store`. Reads `config.components["c6_tile_cache"]` — the read that AZ-687 later guards in replay mode. |
+| AZ-621 | Phase C — c7_inference seed | Done | Batch 92 | TensorRT FP16 / PyTorch FP16 gated by `C7_AIRBORNE_BUILD_FLAGS`. |
+| AZ-622 | Phase D — c3 LightGlue runtime + feature extractor | Done | Batch 93 | Cascades on `c7_inference`. |
+| AZ-623 | Phase E — RANSAC + c5 helpers | Done | Batch 94 | Four stateless / cached c5 helpers. |
+| AZ-625 | Phase E.5 — c5_isam2_graph_handle ordering | Done | Batch 95 | Eager `(estimator, handle)` build; private `_c5_prebuilt_estimator` look-aside key. |
+| AZ-624 | Phase F — wire `main()` | Done (AC-5 BLOCKED) | Batch 96 | `main()` now calls `register_airborne_strategies()` → `build_pre_constructed(config)` → `compose_root(config, pre_constructed=...)`. AC-1..AC-4 covered locally; **AC-5 BLOCKED on Jetson Tier-2 evidence**. |
+| AZ-687 | replay-mode guard for `build_pre_constructed` | Done (AC-687-3 BLOCKED) | Batch 97 | Cross-cutting follow-up surfaced by AZ-624's Jetson Tier-2 run (terminal log: `_docs/03_implementation/jetson_runs/2026-05-19_az618_tier2_run.txt`). Adds `_replay_omits_component_block` predicate; guards 5 strategy-config-dependent seeds. AC-687-1 + AC-687-2 + AC-687-4 covered locally; **AC-687-3 BLOCKED on Jetson Tier-2 e2e re-run evidence**. |
+
+### Updated counts
+
+- **Tasks audited** (this gate's scope): 107 + AZ-591 + AZ-619..AZ-625 + AZ-687 = **116 product tasks** in `_docs/02_tasks/done/`.
+- **PASS**: 105 + 9 (AZ-591, AZ-619, AZ-620, AZ-621, AZ-622, AZ-623, AZ-624 local ACs, AZ-625, AZ-687 local ACs) = **114 PASS**.
+- **BLOCKED-with-named-Tier-2-handle**: AZ-332 → AZ-592 (backlog/); AZ-333 → AZ-593 (backlog/); AZ-624 (AC-5) and AZ-687 (AC-687-3) → out-of-band Jetson Tier-2 evidence files under `_docs/03_implementation/jetson_runs/` (no Jira follow-up needed; the same physical run clears both ACs). **4 BLOCKED entries** total, 2 of which share a single hardware artifact.
+- **FAIL**: **0**.
+
+### Tier-2 evidence files outstanding
+
+These files live outside this dev host's reach. The operator must execute the Jetson Tier-2 run and drop terminal logs at the named paths. Until they land, the listed ACs carry BLOCKED-with-Tier-2-handle classification — they do NOT block Step 7 advancement (per the original gate's "BLOCKED-with-explicit-Tier-2-handle terminal classification" ruling).
+
+| File | Clears AC(s) | Status |
+|------|-------------|--------|
+| `_docs/03_implementation/jetson_runs/2026-05-19_az618_tier2_run.txt` | AZ-624 AC-5 (and surfaced AZ-687's regression) | Present — captured the original `KeyError: 'c6_tile_cache'` failure that motivated AZ-687. |
+| `_docs/03_implementation/jetson_runs/2026-05-19_az687_tier2_run.txt` | AZ-687 AC-687-3 (which transitively re-confirms AZ-624 AC-5 once the guard fix is in place) | Pending — must capture both `replay.compose_root.ready` AND `replay.input.frame_emitted` log lines on AC-1, AC-2, AC-5, AC-6 of `tests/e2e/replay/test_derkachi_1min.py`. JetPack 6.2.2+b24, L4T R36.5.0. |
+
+### Revised Gate Decision
+
+Per the original gate's "BLOCKED-with-explicit-Tier-2-handle terminal classification" ruling (which applied to AZ-332 / AZ-333 → AZ-592 / AZ-593): Step 7 is CLEARED to advance.
+
+- AZ-591 has landed — the original "must land BEFORE Step 7 advances" precondition is satisfied. `compose_root()` can now reach takeoff on the airborne binary.
+- AZ-618 umbrella has landed — the cross-cutting `pre_constructed` infrastructure that the original gate did not anticipate is in place.
+- AZ-624's AC-5 and AZ-687's AC-687-3 are BLOCKED-with-Tier-2-handle — exactly the terminal classification the original gate permits.
+- AZ-687 itself is the regression fix for AC-5; once `2026-05-19_az687_tier2_run.txt` lands and clears AC-687-3, both AZ-624 AC-5 and AZ-687 AC-687-3 close simultaneously.
+
+**State**: Step 7 (Implement) → **completed**. Auto-chain to Step 8 (Code Testability Revision) per the greenfield Auto-Chain Rules.
+
+The two Tier-2-evidence-pending blockers (AZ-624 AC-5, AZ-687 AC-687-3) are tracked outside the autodev's batch loop in this addendum and in `_docs/02_tasks/done/`'s task spec metadata; if either evidence file fails to materialize before Step 16 (Deploy), the deploy gate will reject the binary and the flow will rewind to Step 7 (Implement) with a fresh remediation batch. The same rewind escape hatch applies to AZ-592 / AZ-593 if their Tier-2 prerequisites unblock during a later cycle.
+
 End of report.
diff --git a/_docs/_autodev_state.md b/_docs/_autodev_state.md
index 8d24388..b2fb4ec 100644
--- a/_docs/_autodev_state.md
+++ b/_docs/_autodev_state.md
@@ -6,9 +6,9 @@ step: 7
 name: Implement
 status: in_progress
 sub_step:
-  phase: 16
-  name: batch-loop
-  detail: "Batch 97 landed: AZ-687 (2pt) replay-mode guard in build_pre_constructed; spec moved to done/, code-review PASS (batch_97_review.md), Tier-1 suite green (2153 pass). AZ-687 transitioned to In Testing pending out-of-band Jetson Tier-2 e2e re-run (AC-687-3 evidence: _docs/03_implementation/jetson_runs/2026-05-19_az687_tier2_run.txt — to be collected by user)."
+  phase: 17
+  name: completeness-gate-rerun
+  detail: "todo/ empty; re-running gate to add AZ-687 (BLOCKED-on-Tier-2 evidence, AZ-624 AC-5 precedent)"
 retry_count: 0
 cycle: 1
 tracker: jira