alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync local pi changes

Browse Source
This commit is contained in:
alex wiesner
2026-04-09 23:14:57 +01:00
parent 18245c778e
commit ec378ebd28
128 changed files with 22510 additions and 3436 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
.pi/reviews/context-manager-task6-mode-fix-report.md Normal file
View File

@@ -0,0 +1,20 @@
# Context Manager Task 6 Mode Fix Report
- **Status:** DONE
- **Changes:**
- Updated `.pi/agent/extensions/context-manager/src/commands.ts` so a successful `/ctx-mode` immediately appends a serialized `context-manager.snapshot` entry after `runtime.setMode(...)`.
- Kept the public command contract stable: the command name is unchanged, the invalid-usage warning string is unchanged, and the existing `turn_end` snapshot persistence path is still active.
- Added an integration-style regression test in `.pi/agent/extensions/context-manager/src/extension.test.ts` that starts from a `balanced` snapshot, runs `/ctx-mode aggressive`, and verifies the branch immediately persists a new snapshot with `mode: "aggressive"` before any `turn_end`.
- Updated the existing `/ctx-mode` + `turn_end` test to assert both snapshots: the immediate command-path snapshot and the later `turn_end` snapshot with refreshed token pressure data.
- **Tests:**
- `cd /home/alex/dotfiles/.worktrees/context-manager-extension/.pi/agent/extensions/context-manager && npx tsx --test src/extension.test.ts` → 5 passed, 0 failed
- `cd /home/alex/dotfiles/.worktrees/context-manager-extension/.pi/agent/extensions/context-manager && npm test` → 40 passed, 0 failed
- **Files changed:**
- `.pi/agent/extensions/context-manager/src/commands.ts`
- `.pi/agent/extensions/context-manager/src/extension.test.ts`
- `.pi/reviews/context-manager-task6-mode-fix-report.md`
- **Self-review findings:**
- The fix is narrowly scoped to the `/ctx-mode` success path and reuses the existing snapshot serializer and append-entry persistence mechanism.
- The regression coverage exercises the actual command path instead of only verifying later `turn_end` behavior.
- `turn_end` persistence remains intact and now appends a fresh follow-up snapshot with updated token usage, which is explicitly covered by the adjusted integration test.
- **Concerns:** None.