Summarization offloads write conversation_history/ into the target repository

[blue-az]

When the summarization middleware triggers in deepagents, it offloads the conversation history to a conversation_history/ directory created in the target repository root.

This pollutes the workspace being documented: the directory can be swept into version control by accident, and subsequent OpenWiki update runs (or other agents working in the repo) can discover and read these history files, bloating context with stale transcript content.

Observed while running --init/--update cycles against a mid-size repository on the OpenRouter path with summarization triggering at a configured input-token cap.

Suggested fixes (either would resolve it):

1. Redirect the offload location outside the target repository — e.g. ~/.openwiki/<repo-hash>/conversation_history/ alongside the existing credential storage, or a temp path.
2. At minimum, add conversation_history/ to the prompt-level discovery/read exclusions so documentation runs never inspect it.

Related: I'm submitting a small opt-in hardening PR for the OpenRouter path (early-summarization token cap, subagent/fallback kill switches) — this issue is the remaining workspace-pollution item discovered during that testing.

[PrinceThummar011]

Hi! I'd like to take this issue. I'll trace how conversation_history/ is currently created, implement a clean fix that aligns with the project's architecture, add tests if needed, and open a PR once it's ready. Christian Bromann (@christian-bromann)

[blue-az]

Hi Prince (@PrinceThummar011) — thanks for the nudge on this one! I actually filed #49 while wrapping up a related PR (#312) and deliberately kept them separate rather than scope-creep that PR. I'd been holding off circling back while the surrounding backend was going through the #48 rewrite, and it sat longer than I meant it to.

Your comment prompted me to finally take a pass — I've got a fix implemented and tested (redirects /conversation_history writes to ~/.openwiki/conversation_history instead of the target repo, with backend changes + test coverage). Happy to open a PR with it, or if you'd rather run with your own approach, just say the word and I'll hold off. Didn't mean to step on your offer to take this one!

[PrinceThummar011]

Thanks for the update! Please go ahead and open the PR since you've already implemented and tested it. I appreciate you checking in. I'll keep an eye out for another issue to contribute to and learn from your implementation.