diff --git a/.kiro/specs/ha-term-safety/tasks.md b/.kiro/specs/ha-term-safety/tasks.md
index 3bc5792..d586b7b 100644
--- a/.kiro/specs/ha-term-safety/tasks.md
+++ b/.kiro/specs/ha-term-safety/tasks.md
@@ -144,7 +144,7 @@
   - Observable completion: controller test binary exits 0; ASAN clean; clean-failover and durability suites still green
   - _Requirements: 1.1, 2.3, 3.1, 4.1, 5.1, 6.1, 7.1_
   - _Depends: 5.1, 5.2, 5.4_
-  - _Blocked: depends on 5.2 + 5.4 (both blocked on bug-990). The controller-build + unit-suite-green-under-ASAN portion is independently runnable TODAY (174 Tests 0 Failures on the direct binary; bug-924 overlayfs caveat for the meson harness), but the "clean-failover suite green" acceptance requires 5.2. Run the build/unit gate after the live-send cutover lands._
+  - _Blocked (live portion only — build+unit gate CONFIRMED GREEN): with all of 2.4–4.3 + 3.4 + 5.1 + 5.3 landed, `/xce-build controller` COMPILES + LINKS and the controller_unit_test binary EXITS 0 with **175 Tests 0 Failures** on the reliable gate (`rm -rf /tmp/xce_*` then direct binary, ASAN detect_leaks=0). The `test_wal_catchup_*` FAIL prints (forked-child overlayfs `fdatasync` errno=-11/5) + the meson `test_demotion_replay` flake are the documented bug-924 overlayfs artifacts, present since iter-1, NOT regressions. The ONLY remaining 5.5 acceptance is "clean-failover suite green", which is the LIVE 5.2 harness — env-blocked here (real fs needed). Re-run `/xce-build controller` + the 5.2/5.4 STRICT_TERM harness on a real fs to fully close 5.5._
 
 ## Implementation Notes