lsm / neokai / 28213873679

82%

Build Type

push

github

Committed by web-flow

Commit Message

fix: auto-compact + continue on 'prompt is too long' overflow (#2179)

* fix: compact-then-continue recovery on 'prompt is too long' overflow

Worker/node sessions that overflow their context window receive a terminal
'prompt_too_long' result that the idle sweep treated as a safe terminal point
and skipped, leaving the execution stuck forever with no recovery.

Reactive recovery (core):
- New prompt-too-long-recovery.ts: isPromptTooLongResult() detects the
  terminal_reason / errors signature; buildPromptTooLongContinueNag() +
  MAX_PROMPT_TOO_LONG_RECOVERY_ATTEMPTS (2).
- SpaceRuntime.handleNonTerminalIdleExecutions now intercepts a prompt-too-long
  terminal result BEFORE the terminal skip and runs compact-then-continue:
  inject /compact (reuses the messageQueue primitive), then once the last
  message is no longer an overflow result (context shrank below the limit),
  inject a 'resume your work' nag. The continue nag only fires after compaction
  proves effective, so it never re-hits the same wall. Bounded by attempt cap;
  escalates execution+run to 'blocked' when compaction cannot help.

Preventive:
- buildProviderSettings() no longer returns {autoCompactEnabled:false} for a
  non-native provider with an unknown context window (a dead zone with no
  compaction path). Returns undefined so the SDK's built-in auto-compact
  (enabled by default) runs. Kimi's explicit disable + NeoKai fallback is
  unchanged.

* fix: harden prompt-too-long recovery against stalls (review P1/P3)

Address review feedback on the compact-then-continue state machine:

P1 — fresh overflow after /compact no longer stalls: track the injected
/compact's dbId (awaitingContinueAfterDbId). When the last message advances past
it, the wait clears and a fresh prompt-too-long result is re-evaluated (re-compact
or escalate) instead of being mistaken for the pre-compact result.

P1 — failed /compact injection no longer leaks awaitingContinue: only set
awaitingContinue (and record the ... (continued)

Coverage Stats

11368 of 16392 branches covered (69.35%)

Branch coverage included in aggregate %.

41 of 423 new or added lines in 3 files covered. (9.69%)

26 existing lines in 2 files now uncovered.

95513 of 114165 relevant lines covered (83.66%)

299.87 hits per line