skynet/claude-foundations
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: end-session — log, gac token correction in CLAUDE.md, FUTURE offload targets

Browse Source 
Claude-Session: https://claude.ai/code/session_01Ku87DDWwbJkTx6SuV3sQDc
This commit is contained in:
Paul O'Reilly
2026-09-11 13:56:44 +12:00
parent df243cd953
commit b6c976a00b
3 changed files with 35 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
FUTURE.md
View File

@@ -13,6 +13,15 @@ Backlog of improvement ideas not on the active roadmap.
---
## Next MiniMax offload targets (after review + CI triage)
- **Problem:** Fable/Opus sessions still burn tokens on remaining bulk work: `/reflect-logs` extraction, test authoring from specs, `/end-session`/`/housekeeping` doc summarisation, transcript processing.
- **Idea:** Extend the shipped 2026-09-11 pattern (wrapper materialises inputs, MiniMax gets `Read,Glob,Grep,Write` only, strict result gate, operator adjudicates): a `/reflect-logs --minimax` draft mode producing topic-file diffs for approval, and an `mm-test-task`-style spec→tests generator (verifiable — the tests must run).
- **Open questions:** Observed invented-findings rate from `/review-minimax` in real use? Does reflect-logs drafting keep topic-file voice consistent? Where does test generation need the frozen-fixture skeleton (M27) first?
- **Depends on:** Usage data from `/review-minimax` and `/ci-triage-minimax` on real agent branches
---
## Standing Deployment Authorization in CLAUDE.md
- **Problem:** Claude has all the tooling needed to run deployment steps (sops, ansible-playbook, kubectl, docker, git push) but must ask for confirmation every time because these are irreversible, shared-infrastructure operations. This makes multi-step milestone deployments slow and interactive.