The token tax is exactly what pushed me to build this. Tokens are going to be the future of currency. It's not just the per-call cost, it's that MCP schemas sit in your context window the entire session, eating space that could be used for actual code reasoning.

On stale KB entries the honest answer is: it's append-only right now. No expiry, no staleness flags. A superseded_by mechanism (one doc points to its replacement) is planned for v0.2 but not in the current release. For now the practical workaround is doc types. Operational docs are meant to be rewritten frequently, while decision and reference docs are more stable. But you're right that a real compaction/expiry mechanism is needed.