@kolisachint/hoocode-agent 0.5.44 → 0.5.45
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 +21 -0
- package/examples/extensions/custom-provider-anthropic/package.json +1 -1
- package/examples/extensions/custom-provider-gitlab-duo/package.json +1 -1
- package/examples/extensions/sandbox/package.json +1 -1
- package/examples/extensions/with-deps/package.json +1 -1
- package/package.json +4 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.5.45] - 2026-08-31
|
|
4
|
+
|
|
3
5
|
## [0.5.44] - 2026-08-31
|
|
4
6
|
|
|
5
7
|
### Added
|
|
@@ -38,6 +40,25 @@
|
|
|
38
40
|
already in context, and it is the number `maxResults` is tuned against. It
|
|
39
41
|
was being parsed into the result details and then dropped at render.
|
|
40
42
|
|
|
43
|
+
### Fixed
|
|
44
|
+
|
|
45
|
+
- The agent-selection gold set covers `code-review` and `security-review`.
|
|
46
|
+
|
|
47
|
+
0.5.42 added both agents without cases for them, and the eval's coverage
|
|
48
|
+
assertion — every agent in the roster is expected by at least one case — has
|
|
49
|
+
failed on `main` ever since, so every branch cut from it inherits a red
|
|
50
|
+
`bun-test (coding-agent)`. The assertion earns its keep: an agent no case asks
|
|
51
|
+
for scores as a permanent miss, so a roster can grow agents nobody selects
|
|
52
|
+
while the eval reads as though the descriptions got worse.
|
|
53
|
+
|
|
54
|
+
Three cases each, plus one more `expect: null` — review phrasing over a diff
|
|
55
|
+
already pasted into the conversation, where a subagent that cannot see it is
|
|
56
|
+
strictly worse. All authored from how the ask is actually phrased rather than
|
|
57
|
+
from the agent descriptions, per the fixture's own circularity note. The two
|
|
58
|
+
review agents ship with identical tools, isolation, background flag and cost,
|
|
59
|
+
so like `explore`/`plan` they are separated on the ask itself: is this
|
|
60
|
+
correct, versus can this be attacked.
|
|
61
|
+
|
|
41
62
|
## [0.5.43] - 2026-08-31
|
|
42
63
|
|
|
43
64
|
### Added
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@kolisachint/hoocode-agent",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.45",
|
|
4
4
|
"description": "Coding agent CLI with read, bash, edit, write tools and session management",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"hoocodeConfig": {
|
|
@@ -50,9 +50,9 @@
|
|
|
50
50
|
"prepublishOnly": "npm run clean && npm run build"
|
|
51
51
|
},
|
|
52
52
|
"dependencies": {
|
|
53
|
-
"@kolisachint/hoocode-agent-core": "^0.5.
|
|
54
|
-
"@kolisachint/hoocode-ai": "^0.5.
|
|
55
|
-
"@kolisachint/hoocode-tui": "^0.5.
|
|
53
|
+
"@kolisachint/hoocode-agent-core": "^0.5.45",
|
|
54
|
+
"@kolisachint/hoocode-ai": "^0.5.45",
|
|
55
|
+
"@kolisachint/hoocode-tui": "^0.5.45",
|
|
56
56
|
"@silvia-odwyer/photon-node": "^0.3.4",
|
|
57
57
|
"chalk": "^5.5.0",
|
|
58
58
|
"cli-highlight": "^2.1.11",
|