dsh-history-fold

LIMITATIONS

Known limitations

- Tuned and measured against DeepSeek Harness on Windows with a 1,000,000-token context window. The mechanism is adapter-agnostic; the shipped absolute fallbacks are not — which is what the ratios are for. When the window resolves, the thresholds scale with it. - **Whether `ctx.llm` is really reachable from this plugin's context has not been confirmed against a live DSH.** The lookup mirrors `resolveMeter()` (direct property, then `ctx.reflect.get`, then the agent's own composed context) and never throws, but if no path works in your build the plugin logs `triggerSource: "default"` and behaves exactly as it did before this feature existed. - Token counts come from DSH's `tokenMeter`. If it is unavailable the plugin does nothing — by design. - Folding reduces what the model sees. The archive keeps it recoverable, but reading it back costs a `rg` round-trip. - It does not (yet) coordinate with `dsh-compaction-basic`; it simply stays below its trigger.