v0.5.1 - Progressive Compression Fix

Bug Fixes

Progressive TOON compression was triggering unconditionally on every request despite progressive.enabled: true in user config.

Root Cause

resolveCompressionConfig() did not merge the progressive field from globalConfig/profileConfig, causing provider.ts routing logic to fall through to backward-compatible unconditional compression mode.

Fix

Added progressive: override.progressive ?? base.progressive to resolveCompressionConfig return value.

Impact

Users with progressive.enabled: true now correctly trigger compression only when:

1. Context size ≥ contextThreshold * contextWindow, OR
2. Time since last turn ≥ timeThreshold

Previously, compression triggered on every request after keepLastN threshold.

Verification

• ✅ Test: test/progressive-config-merge.test.ts — 5 passing scenarios
• ✅ Manual test guide: docs/MANUAL_TEST_GUIDE.md
• ✅ Session analyzer: scripts/test-progressive-compression.sh

Documentation

• docs/PROGRESSIVE_CONFIG_MERGE_FIX.md — root cause analysis + timeline
• docs/PROGRESSIVE_COMPRESSION_TEST_PLAN.md — comprehensive test scenarios

Upgrade

cd ~/.omp/agent/extensions/model-router
git pull
/reload  # in OMP

Or wait for auto-upgrade on next OMP session restart.

Full Changelog: v0.5.0...v0.5.1