The auto-improve reviewer only loads `_rules/`/`procedures/` page bodies,
and its recent-page context is a recency-ordered, one-line-per-page list
drawn from the shared project briefing. That list is dominated by
`sessions/` pages, so durable pages in `decisions/`/`gotchas/` outside
`_rules/` are effectively invisible to the reviewer, which causes
duplicate proposals.
Filter `sessions/` pages out of the recent-page list the reviewer builds
its prompt, patchable set, and existing-page index from. This is scoped
to the auto-improve reviewer only: it operates on the already-fetched
`briefing.recent_pages` and does not touch the shared
`briefing_for_project` reader, so the SessionStart briefing and
`memory_briefing` — where session pages legitimately belong — are
unchanged.
Also document the reviewer's context limits in
docs/auto-improvement-loop.md, with configurable patchable prefixes and
embedding-nearest dedup called out as deferred future work.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MDbhmszrjG9s5MrPrTuNtm
