reflect-logs: distill session logs into topic memory (2026-07 sweep)

This commit is contained in:
Paul O'Reilly
2026-07-02 16:05:43 +12:00
parent b76e56f750
commit a63f5a0f80
4 changed files with 53 additions and 0 deletions

View File

@@ -39,3 +39,11 @@ The Edit tool tracks which files have been explicitly read via the Read tool —
## `/context` "Memory files" aggregates two distinct systems
The "Memory files" category reported by `/context` combines project `CLAUDE.md` instructions and auto-memory `MEMORY.md`. They have different purposes (project conventions vs cross-session learnings) and live in different places. When auditing context size, check both rather than assuming a single source.
## Grep all consumers before removing or keeping a launcher field
Before keeping an interactive prompt or launcher-written env var, grep every consumer across the filesystem (`grep -r CLAUDE_TIME_HORIZON ~`). Two vars (`CLAUDE_TIME_HORIZON`, `CLAUDE_PROVIDER`) accumulated in `active-mode.env` unused; auditing consumers revealed the dead code and pointed to every downstream file needing a matching edit (skill templates, statusline).
## Resolved: claude-profile ↔ CLAUDE.md / statusline integration questions
Open questions from the 2026-04-12 design session are now resolved: (1) CLAUDE.md session-start reads `active-mode.env` and auto-selects the project from cwd or `CLAUDE_PROJECT`, skipping the interactive picker; (2) the status-line script is bash at `~/.claude/status/statusline.sh` (not in any git repo, changes are live immediately); (3) mode switching became the `/switch-mode` slash command / `switch-mode` skill, not a hook-matched literal phrase. Still open: MiniMax M2 agentic-CLI availability and the token-budget comparison for the inverted architecture (tracked in FUTURE.md, not memory).