fix: emergency + nothing-to-compress emits /compact notice, not compress demands — issue #216 residual

[ranxianglei]

Problem

Incident ses_7fb5cbc8 (issue #37): user config set min/max context limits to 20%, making the session (55% actual) permanently emergency. inject.ts gated nudges with:

shouldInjectNudge = nudgeAllowed && (!nothingToCompress || emergencyOverride)

The emergencyOverride bypass demanded "Context limit reached — compress now" every turn even when nothingToCompress was true — no valid targets existed, so the model retried phantom ranges and every failure re-armed the nudge (~12 failed compressions in the incident). This is the residual of issue #216's loop surviving the v1.14.4 fix through the emergency path.

Fix

• emergencyNoTargets = emergencyOverride && nothingToCompress
• Regular nudges: shouldInjectNudge = nudgeAllowed && !nothingToCompress (emergency bypass removed)
• Notice: shouldInjectNotice = emergencyNoTargets && noticeCadenceMet instead of compress instructions
• Cadence reuses lastNudgeShownTokens + growthFloor — no per-turn nagging
• Emergency WITH compressible ranges → strong alert unchanged

Notice Text Evolution (3 revisions, evidence-driven)

v1: "/compact / new session / relax protections" — user-command steps
v2 (user feedback "这种是不是export比较好"): export-first ordering
v3 (commit 8baebd2, incident ses_7fb5c607): model-actionable framing. A headless opencode run model read the command steps as things IT should execute, looped 18 turns on retry-compare-reply, and died at 233K/262K context overflow. Slash commands are user-only in every mode — the model's ONLY viable action is informing the user. Notice now reads:

🚨 Context is critically full (N% of limit) and there is nothing left that can be safely compressed.
Do NOT retry compress on the same ranges — they will keep failing.
You cannot execute user commands yourself. Act now via your reply/message tool:
- Inform the user that context is full and compression is exhausted
- Recommend they run /acp export (archives compression summaries to a file), then /compact or start a new session
- Alternatively, ask them to relax protected-tool / preserve-recent settings so compression becomes possible
Then stop retrying and await the user's response.

Tests

• 4 new tests in inject.test.ts: notice content (incl. reply/message-tool framing), 3-turn cadence regression (§5.7.1), incident-shape phantom regression (sub-floor ranges), production-config preserve-recent zone (§5.7.1: preserveRecentMessages: 20)
• Replaced test asserting the old loop-driving behavior
• 2 assertions in model-switch-limits.test.ts updated
• Full suite: 1024 pass / 0 fail; §5.7.3 revert-check verified

Dual-Agent Review (both effectively APPROVE)

Oracle (3m20s): growthFloor math verified (22.5K @ 1M model); test config paths traced.

Explore (3v3m22s): all 4 emergency×compressibility combinations traced — no regression; all lastNudgeShownTokens consumers benign; "compress now" string only in gated paths; E2E detectNudge unaffected. Flagged §5.7.1 gap → addressed in cae3e94.

Stacked On

PR #325 — merge that first; this branch is based on its tip (5924c69).

Config Note

User's global config also updated: 20%/20% → 80%/80% (matches repo defaults).

[github-actions]

📦 Built Plugin Artifact

Branch: 2026-08-20_emergency-nothing-compressible (8baebd2)

Option A — Install from npm PR tag (recommended)

opencode plugin opencode-acp@pr-326 --global

Each push to this PR publishes a new version under the pr-326 npm tag.

Option B — Install from GitHub

opencode plugin "github:ranxianglei/opencode-acp#2026-08-20_emergency-nothing-compressible" --global

Option C — Download artifact

1. Download the artifact from the Actions run
2. Extract the tarball and install:

tar xzf opencode-acp-pr326.tgz
cp -r package/dist ~/.cache/opencode/packages/opencode-acp@latest/node_modules/opencode-acp/dist

3. Restart opencode to pick up changes.

---

This comment is automatically updated on each push.