jeopi-cli 16.2.24 → 16.2.25
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +8 -0
- package/dist/cli.js +2637 -2637
- package/dist/types/slash-commands/types.d.ts +2 -0
- package/package.json +12 -12
- package/src/internal-urls/docs-index.generated.txt +1 -1
- package/src/prompts/tools/subagent.md +1 -1
- package/src/session/session-context.ts +8 -2
- package/src/slash-commands/builtin-registry.ts +10 -0
- package/src/slash-commands/types.ts +2 -0
- package/src/tools/subagent.test.ts +20 -0
- package/src/tools/subagent.ts +11 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,14 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [16.2.25] - 2026-07-05
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- `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.
|
|
10
|
+
- 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.
|
|
11
|
+
- 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.
|
|
12
|
+
|
|
5
13
|
## [16.2.24] - 2026-07-03
|
|
6
14
|
|
|
7
15
|
### Breaking Changes
|