mirror of
https://github.com/affaan-m/ECC.git
synced 2026-08-31 04:09:51 +02:00
Tanelandhaelyra
ecdd517765
The context signal always rendered "N% of <window> window", including when the window size was the assumed 200k default rather than a detected value. On a 1M session whose transcript carries no [1m] marker, that produced lines like: [StrategicCompact] Context ~194k tokens (97% of 200k window) while actual usage was ~19%. The user compacts on a false alarm, loses context, and the resulting quality drop reads as a model regression. The gap is structural: the context threshold defaults to 80% of the window (160k on 200k), so the signal fires precisely in the 160k-200k band where the size cannot be determined — above 200k the observed-tokens fallback correctly infers 1M, and below 160k nothing fires. Model id alone cannot close this. A tier may ship both a 200k and a 1M variant under one id, so neither the known-family table nor a new entry can distinguish them, and the transcript records no window field. So stop asserting what isn't known: resolveContextWindow() now reports whether the size was detected (env override, [1m] marker, known family, or observed tokens > 200k) or assumed, and the hook omits the percentage and window label when it was assumed. The token count, threshold, and firing behaviour are unchanged. resolveContextWindowTokens() keeps its existing signature and semantics. Note: 3 pre-existing failures in tests/hooks/suggest-compact.test.js reproduce identically on unmodified main and are untouched here.