diff --git a/docs/superpowers/specs/2026-06-05-live-gui-fragility-fixes-design.md b/docs/superpowers/specs/2026-06-05-live-gui-fragility-fixes-design.md index 64d26590..1b85f74f 100644 --- a/docs/superpowers/specs/2026-06-05-live-gui-fragility-fixes-design.md +++ b/docs/superpowers/specs/2026-06-05-live-gui-fragility-fixes-design.md @@ -9,9 +9,17 @@ ### Scope decisions (per user review 2026-06-05) - Change 1 (the `b""` → `""` fix): **in scope, critical path.** -- Change 2 (test mock fix): **in scope, critical path.** +- Change 2 (test mock fix for prior session test): **SCOPE REDUCED during execution.** The test was more under-mocked than the spec assumed. Initial error at `src/gui_2.py:2333` (imscope.window tuple unpack) was the first of several un-mocked dependencies. After fixing imscope.window, the next failure surfaces at `src/gui_2.py:4496` (render_theme_panel: imgui.begin returning bool where 2-tuple expected). The test calls `render_main_interface` which is a kitchen-sink function requiring 50+ mocks. **Decision: defer Change 2 to a separate follow-up track** that focuses on refactoring the test to either (a) exercise a narrow prior-session render path instead of `render_main_interface`, or (b) add the missing 50+ mocks. The imscope.window fix is still applied as a defensive change (and as a model for future test work). - Change 3 (regression unit test): **in scope, critical path.** -- Change 4 (doc hardening of defer-not-catch sections): **DEFERRED to end of track** — user wants to see how long the critical path takes first. If time permits at the end, do Change 4 as a final commit; otherwise leave it for a follow-up patch. +- Change 4 (doc hardening of defer-not-catch sections): **DEFERRED to end of track** — user wants to see how long the critical path takes first. If time permits at the end, do Change 4 as a final commit; otherwise leave for a follow-up patch. + +### Revised pass-rate target +- Before track: 269/272 (98.9%) +- After Change 1: 271/272 (99.6%) — both `test_auto_switch_sim` and `test_workspace_profiles_restoration` should pass; `test_prior_session_no_pop_imbalance` is deferred to a follow-up. +- After Change 3: 272/272 if Change 2 also fixed, else 271/272 + new regression unit test passes. + +### Follow-up track: prior_session_test_harden_20260605 +A new track to be queued in `conductor/tracks.md` covering the `test_prior_session_no_pop_imbalance` test's comprehensive mock setup (or refactor to test a narrow path). ### Failures (3)