release: v1.14.16 — raise context limit to 80%

[ranxianglei]

release: v1.14.16 — Raise context limit to 80%

Summary

Raises the default compress.maxContextLimit from "55%" to "80%" so
compression waits until context exceeds 80% of the model window before firing the
strong "over-limit" nudge.

Problem

The strong nudge fired at 55% context usage. Even after pinning nudge growth to a
fixed 50K (v1.14.15), compression still engaged relatively early, leaving usable
context unused.

Change

lib/config.ts default compress block — one line:

-        maxContextLimit: "55%",
+        maxContextLimit: "80%",

minContextLimit: "45%" is unchanged — it is tone-only (see semantics below).

Semantics — why minContextLimit is left at 45%

The nudge decision (context-compress-algorithms computeShouldNudge) is:

shouldNudge = growthSinceLastNudge >= nudgeGrowthTokens || overMaxLimit

overMinLimit only selects the tipsVariant tone ("minLimit" vs "maxLimit")
once a nudge is already firing — it never triggers a nudge on its own. So
minContextLimit does not cause early compression; maxContextLimit is the
load-bearing threshold.

Backstops unchanged: emergencyThresholdPercent: "98%", nudgeGrowthTokens: 50000.
Users can override via compress.maxContextLimit in their config.

Verification

• typecheck (tsc --noEmit): clean
• tests (node --import tsx --test tests/*.test.ts): 976 pass / 0 fail
• build (tsup && tsc --emitDeclarationOnly): success
• scripts/ci/check-pr.sh: all checks pass

Merge → auto-publish

Merging triggers release.yml, which detects the 2026-08-12_release-v* branch,
tags v1.14.16, and publishes to npm latest. PR merge is human-only.