conductor(plan): Add session restoration hardening to plan

This commit is contained in:
2026-03-08 21:17:46 -04:00
parent bbe0209403
commit a6f7f82f02

View File

@@ -17,8 +17,9 @@
- [ ] Implement logic to load all related logs (comms, mma, tools) for that session. - [ ] Implement logic to load all related logs (comms, mma, tools) for that session.
- [ ] Ensure that for entries referencing external files (scripts/outputs), the content is loaded on-demand or during the restoration process. - [ ] Ensure that for entries referencing external files (scripts/outputs), the content is loaded on-demand or during the restoration process.
- [x] Task: Implement "Historical Replay" UI mode. 1b3fc5b - [x] Task: Implement "Historical Replay" UI mode. 1b3fc5b
- [ ] In `src/gui_2.py`, implement logic to tint the UI (as already partially done for comms) when `is_viewing_prior_session` is True. - [x] In `src/gui_2.py`, implement logic to tint the UI (as already partially done for comms) when `is_viewing_prior_session` is True.
- [ ] Populate `disc_entries`, `_comms_log`, and MMA Dashboard states from the loaded session logs. - [x] Populate `disc_entries`, `_comms_log`, and MMA Dashboard states from the loaded session logs.
- [x] Harden `cb_load_prior_log` for legacy compatibility and reference resolution. bbe0209
- [ ] Task: Conductor - User Manual Verification 'Phase 2: Session-Level Restoration' (Protocol in workflow.md) - [ ] Task: Conductor - User Manual Verification 'Phase 2: Session-Level Restoration' (Protocol in workflow.md)
## Phase 3: Diagnostic Log & Discussion Cleanup ## Phase 3: Diagnostic Log & Discussion Cleanup