From cc4e61756c6704f3797a336e82894979ab460795 Mon Sep 17 00:00:00 2001 From: Benjamin Borbe Date: Sun, 23 Aug 2026 19:28:30 +0200 Subject: [PATCH] feat: post-compact re-anchors on conventions via /recall pointer --- CHANGELOG.md | 4 ++++ commands/post-compact.md | 10 ++++++++++ 2 files changed, 14 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 28babd0..14f61c7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,10 @@ Please choose versions by [Semantic Versioning](http://semver.org/). * MINOR version when you add functionality in a backwards-compatible manner, and * PATCH version when you make backwards-compatible bug fixes. +## Unreleased + +- feat: post-compact re-anchors on conventions after re-arm — emits a one-line `📌 Conventions: run /recall if you feel drifted` pointer (full doc re-read skipped; CLAUDE.md re-injects each turn), skipped when drift risk is low + ## v0.114.7 - fix: sync-progress re-reads the daily note immediately before writing and merges — prevents a sibling session's concurrent write from being silently clobbered (lost entries never reach git history) diff --git a/commands/post-compact.md b/commands/post-compact.md index 0e6c399..8a153c7 100644 --- a/commands/post-compact.md +++ b/commands/post-compact.md @@ -57,6 +57,16 @@ Each check falls back to its `|| echo "..."` text when the tool is absent on the The fresh post-compact context lost track of background watchers / monitors that were running before compaction. From the resume block's `Live background:` line and the carry-over `background` items, re-establish anything still alive — restart the Monitor / background watch / watcher so completion and failure signals reach this session again. +## Re-anchor on conventions (optional, one line) + +Compaction restores *state* (carry-over items, watchers, next actions) but not *rule-awareness* — the summarized context is exactly the drift trigger `/recall` exists for. After the re-arm step, emit a single pointer line — never the full doc re-read (the harness already re-injects `CLAUDE.md` into context each turn, so a full recall mostly re-emphasizes rather than recovers): + +``` +📌 Conventions: run /recall if you feel drifted — re-reads global + project CLAUDE.md. +``` + +Skip this step entirely when the session's drift risk is low (nothing touched git, worktrees, or repo conventions during the resumed task). + ## Surface next actions Print the concrete next steps, sourced from the verified items: