jeopi-cli 16.2.24 → 16.2.26

package/CHANGELOG.md

@@ -2,6 +2,25 @@
 
 ## [Unreleased]
 
+## [16.2.26] - 2026-07-05
+
+### Added
+
+- `AgentSession`'s auto-retry now degrades once on a `reasoning_extraction` classifier refusal (`stopDetails.category === "reasoning_extraction"`, e.g. Anthropic's "seems to violate Anthropic's Terms of Service … reverse engineering or duplicating model outputs"): it strips unsigned `thinking`/`redactedThinking` blocks from active context and resends immediately on the *same* model, ahead of the generic fallback-model pin and refusal backoff ladder. `reasoning_extraction` is payload-shape-bound — resending the identical batch predictably re-refuses (the advisor already degrades this way for its own transcript; the main turn previously only backed off or switched models, both of which retry the unchanged, re-refusing payload).
+
+### Fixed
+
+- Reworded the `interrupted-thinking` continuity notice (shown after a user-interrupted turn) to drop explicit "reasoning transcript" framing (`type="interrupted-thinking"`, "while you were thinking", "treat the preserved reasoning as internal continuity context") and instruct the model not to quote/repeat the injected content — the labeling amplified the reasoning-extraction classifier signal on top of the raw replayed thinking text.
+- Reworded the advisor system prompt's transcript-framing line ("You receive the agent's transcript incrementally, including their thoughts") to drop the explicit "their thoughts" framing around the primary agent's replayed thinking blocks — defense-in-depth alongside the existing runtime one-shot thinking-strip degrade on refusal.
+
+## [16.2.25] - 2026-07-05
+
+### Added
+
+- `resume` on a target that finished entirely on its own (not `paused`) now requires an explicit `message`; only a `paused` target can resume without one (continues with a default nudge, since the caller already knows why it stopped) — this is the exact distinction the canonical gajae-code `subagent` tool draws.
+- Added `priority` to the builtin slash-command spec (ported from gajae-code's `SlashCommand.priority`): the bare `/` autocomplete menu ties every command's match score at 1, and previously fell back to raw registry-array order under the stable sort — `priority` now breaks that tie (higher first), so `/new`(96), `/resume`(92), `/session`(88), `/goal`(84), `/compact`(72), `/retry`(70), `/copy`(55), `/dump`(54), `/export`(50), and `/settings`(40) surface in the same relative order as the canonical tool. Priority never overrides an actual text match — it only decides ties within the same fuzzy-match score tier, so typing a query still ranks by relevance first.
+- Fixed a latent OOM: `buildSessionContext`'s leaf→root parent-chain walk had no cycle guard, unlike the two sibling walks in `session-manager.ts` (`pathTo`) and `session-loader.ts` (`collectActiveBranchIds`) — a corrupt/cyclic `parentId` chain (two entries pointing at each other) would loop forever and grow the collected path unbounded instead of terminating. Ported from gajae-code's #1193/#1195 parent/child tree-walk cycle guards.
+
 ## [16.2.24] - 2026-07-03
 
 ### Breaking Changes