conductor(archive): move 39 completed tracks (2026-05 to 2026-06) to archive/

This commit is contained in:
ed
2026-06-03 00:09:52 -04:00
parent 0ffeccc7d3
commit 594f14f943
160 changed files with 94 additions and 21 deletions
@@ -0,0 +1,4 @@
# Track: Context Snapshotting per "Take"
- [Specification](./spec.md)
- [Plan](./plan.md)
@@ -0,0 +1,5 @@
{
"id": "context_snapshotting_takes_20260510",
"title": "Context Snapshotting per 'Take'",
"status": "planned"
}
@@ -0,0 +1,9 @@
# Implementation Plan: Context Snapshotting per "Take"
## Phase 1: Snapshot Model
- [x] Update `HistoryManager` and the `Take` model to store a `context_snapshot` (list of serialized file items). (Implemented via Discussion dict in project file).
## Phase 2: Save and Restore
- [x] Modify `AppController` to save the current context state when a new Take is created.
- [x] Modify the "Switch Take" logic in `AppController` to restore the context state from the `context_snapshot`.
- [x] Ensure UI automatically refreshes the Context Panel upon Take switch. (Automatically handled via attribute delegation).
@@ -0,0 +1,8 @@
# Specification: Context Snapshotting per "Take"
## Overview
When branching a discussion using the "Takes" system, snapshot the exact state of the Context Panel (active files, their aggregation flags, and RAG status). When switching between Takes, the UI must visually restore this context state so the user knows exactly what the agent "saw" during that timeline branch.
## Acceptance Criteria
- [ ] Modifying context (adding/removing files, changing AST/summary flags) creates a context delta tied to the active Take.
- [ ] Switching Takes updates the Context panel to reflect the file list and states exactly as they were in that timeline branch.