diff --git a/conductor/tracks.md b/conductor/tracks.md
index 88ba460e..382bdb8f 100644
--- a/conductor/tracks.md
+++ b/conductor/tracks.md
@@ -152,8 +152,11 @@ User review surfaced five outstanding UI issues, each previously attempted witho
 0. [ ] **Track: Sloppy.py Startup Speedup**
    *Status: 2026-06-05 — Surfaced during regression_fixes_20260605 root-cause analysis. `sloppy.py --enable-test-hooks` startup latency has crept up; live_gui fixtures time out at `wait_for_server(timeout=15)`. Hypothesized cause: too much init work on the main thread (FastAPI hook server bring-up, log pruner retry loops, MCT startup). Plan: profile startup, move heavy init off the main thread to the controller's background thread pool, defer non-critical subsystems to lazy-init on first use. Spec/plan to follow.*
 
-0a. [ ] **Track: prior_session_test_harden_20260605**
-   *Status: 2026-06-05 — Surfaced during live_gui_fragility_fixes_20260605 execution. `test_prior_session_no_pop_imbalance::test_no_extraneous_pop_when_prior_session_renders` is more under-mocked than expected: the imscope.window tuple-unpack error at `src/gui_2.py:2333` was the first of many un-mocked dependencies; fixing it revealed `imgui.begin` returning bool where 2-tuple expected at `src/gui_2.py:4496` (`render_theme_panel`). The test calls `render_main_interface` which is a kitchen-sink function requiring 50+ mocks. Plan: either (a) add the missing 50+ mocks (heavy lift), or (b) refactor the test to exercise a narrow prior-session render path instead of `render_main_interface` (lighter lift; preserves the test's intent of verifying push/pop balance in the prior-session render path). Spec/plan to follow.*
+0b. [ ] **Track: rag_phase4_stress_test_flake_20260606**
+   *Status: 2026-06-06 — Surfaced during post-v2 verification test run. `test_rag_phase4_stress.py::test_rag_large_codebase_verification_sim` passes in isolation (14.83s) but fails in the full batched run (24.56s) with `AssertionError: Modified context not found in discussion`. Pattern: 50 dummy files indexed, 1 modified, RAG re-indexed successfully, but the modified content doesn't appear in the AI's discussion context. Hypothesized causes: (a) test-ordering flake with the session-scoped live_gui fixture (most likely), (b) timing issue with the RAG retrieval into the AI context, (c) real bug in the RAG->AI context pipeline that only surfaces with 50+ files. Plan: investigate determinism first (run with different batch orders), then check the RAG->context assembly code path. Spec/plan to follow.*
+
+0a. [ ] **Track: prior_session_test_harden_20260605** [superseded by live_gui_test_hardening_v2_20260605]
+   *Status: 2026-06-05 — Surfaced during live_gui_fragility_fixes_20260605 execution. `test_prior_session_no_pop_imbalance::test_no_extraneous_pop_when_prior_session_renders` is more under-mocked than expected. Completed as part of live_gui_test_hardening_v2_20260605: test refactored to call narrow render_prior_session_view (50+ mocks -> 20, runtime 5.79s -> 0.08s). Commit 26e0ced4.*
 
 1. [ ] **Track: Bootstrap gencpp Python Bindings**
    *Link: [./tracks/gencpp_python_bindings_20260308/](./tracks/gencpp_python_bindings_20260308/)*