v0.1.42

Highlights

• 🗄️ The vault keeps the conversation lean. Before each step of a long task, the tool results in the conversation are measured against a budget (about 90,000 characters for an API model, 40,000 for a local one; HYDRA_TOOL_CONTEXT_CHARS overrides it). Over budget, the oldest results already in the vault are replaced by a one-line stub that says how to read them again; the last two rounds are always kept. Nothing is lost, and a research task no longer grows until the model chokes.
• 📝 vault_note: findings that survive. The agent can write down a figure, a quote or a conclusion (with the document it comes from) as it works; the notes are kept with the task and repeated to it on every step, so compaction never takes the facts it needs for the final answer. "Show steps" lists them as "Noting: …".
• 🗺️ A plan's reading carries over. When you approve a /plan, the task that carries it out starts with the documents the agent read while planning, numbered as before and listed in its context, instead of fetching them again.
• 🔧 Three tools called in parallel could receive the same vault number and overwrite each other's file; fixed.

What's Changed

• vault: old tool results are compacted per round, findings survive with vault_note, and a plan's documents carry over to its execution by @TraX22 in #100

Full Changelog: v0.1.41...v0.1.42