opencode-harness-kit 0.5.6 → 0.5.7

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 CHANGED
@@ -12,6 +12,38 @@ is not happening.
12
12
 
13
13
  ---
14
14
 
15
+ ## [0.5.7] — 2026-10-21
16
+
17
+ Published. The tag is what cut it: `git tag v0.5.7 && git push origin main
18
+ v0.5.7`, and the publish job watches for exactly that.
19
+
20
+ A patch, and a small one: the shipped profiles are refreshed against the
21
+ live catalogue, and a test that pinned the catalogue's old answer stops
22
+ pinning it.
23
+
24
+ ### Changed
25
+
26
+ - **The profiles are refreshed against the live catalogue.**
27
+ `oc-harness refresh --all` is the kit's own command for this, and it had
28
+ not been run since the 19th. The catalogue now says that
29
+ `minimax-m3.1-flash-free` takes a temperature, and that
30
+ `longcat-2.5-preview-free` does not; the profiles said the opposite in one
31
+ case each. The `verified` date is the day the profile was last checked
32
+ against the catalogue, and leaving it stale after a check makes it a lie.
33
+
34
+ Nothing in the generated config changes: the kit sets no temperature at
35
+ all, so the profile's answer only decides what the header says.
36
+
37
+ ### Fixed
38
+
39
+ - **A test failed on a day when nothing in the kit had changed.** The test
40
+ for "temperature is only emitted for models that support it" asserted
41
+ that one particular model does not support one - a value the catalogue
42
+ owns and changes. The test now asks whether the rule holds: no config the
43
+ kit writes may carry a temperature, and every profile has to say whether
44
+ its model takes one. A test that pins a value the world owns fails for
45
+ the wrong reason.
46
+
15
47
  ## [0.5.6] — 2026-10-21
16
48
 
17
49
  Published. The tag is what cut it: `git tag v0.5.6 && git push origin main
@@ -1437,7 +1469,8 @@ silent in the worst way:
1437
1469
 
1438
1470
  ---
1439
1471
 
1440
- [Unreleased]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.6...HEAD
1472
+ [Unreleased]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.7...HEAD
1473
+ [0.5.7]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.6...v0.5.7
1441
1474
  [0.5.6]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.5...v0.5.6
1442
1475
  [0.5.5]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.4...v0.5.5
1443
1476
  [0.5.4]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.3...v0.5.4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-harness-kit",
3
- "version": "0.5.6",
3
+ "version": "0.5.7",
4
4
  "description": "Harness kit for OpenCode: capability profiles, a fleet of job lanes with one free model each, role-based reasoning effort, context pruning, and measured baselines.",
5
5
  "license": "MIT",
6
6
  "homepage": "https://github.com/pham-canh/opencode-harness-kit#readme",
@@ -5,7 +5,7 @@
5
5
  "provider": "opencode",
6
6
  "model": "minimax-m3.1-flash-free",
7
7
  "family": null,
8
- "verified": "2026-10-19",
8
+ "verified": "2026-10-21",
9
9
  "retention": "may-train",
10
10
  "maxRetention": "may-train",
11
11
  "notes": "Every lane gets the model built for it: beam plans, Nemotron 3 Ultra reviews, Lightning sweeps, MiMo sees, GLM audits, Super VL reasons with the effort turned off. Five of the ten providers state that collected data may be used to improve the model, or log the session, so the profile as a whole is may-train and the generated config says so in its header. Install it for public or throwaway repositories.",
@@ -15,7 +15,7 @@
15
15
  },
16
16
  "supports": {
17
17
  "reasoning": true,
18
- "temperature": false,
18
+ "temperature": true,
19
19
  "toolCall": true,
20
20
  "structuredOutput": false,
21
21
  "attachment": true
@@ -5,7 +5,7 @@
5
5
  "provider": "opencode",
6
6
  "model": "minimax-m3.1-flash-free",
7
7
  "family": null,
8
- "verified": "2026-10-19",
8
+ "verified": "2026-10-21",
9
9
  "retention": "zero-retention",
10
10
  "maxRetention": "zero-retention",
11
11
  "notes": "The default. Every lane resolves to a model whose provider states a zero-retention policy: no training, nothing kept. The cost is that six of the ten jobs run on a second-choice model - the planner loses beam (30-day retention) and the reviewer loses Nemotron 3 Ultra - so this is the floor, not the ceiling. The chains are ordered within the ceiling rather than copied from `fleet-all`: `locate` takes deepseek because it publishes a `low` effort level that longcat does not, and `vision` takes minimax because it reads an image in 7 seconds. `fleet-all` gives every lane the model built for it.",
@@ -15,7 +15,7 @@
15
15
  },
16
16
  "supports": {
17
17
  "reasoning": true,
18
- "temperature": false,
18
+ "temperature": true,
19
19
  "toolCall": true,
20
20
  "structuredOutput": false,
21
21
  "attachment": true
@@ -5,7 +5,7 @@
5
5
  "provider": "opencode",
6
6
  "model": "longcat-2.5-preview-free",
7
7
  "family": "longcat",
8
- "verified": "2026-10-19",
8
+ "verified": "2026-10-21",
9
9
  "retention": "zero-retention",
10
10
  "notes": "Meituan. 1M context with image input, and a reasoning toggle rather than a tier, so no variant is written. It read a screenshot correctly in a live call, which is what makes it the zero-retention fallback for the vision lane. Measured at 9.4-13.2s. A preview endpoint: it can be withdrawn without a rename.",
11
11
  "limits": {
@@ -14,7 +14,7 @@
14
14
  },
15
15
  "supports": {
16
16
  "reasoning": true,
17
- "temperature": true,
17
+ "temperature": false,
18
18
  "toolCall": true,
19
19
  "structuredOutput": false,
20
20
  "attachment": true
@@ -5,7 +5,7 @@
5
5
  "provider": "opencode",
6
6
  "model": "minimax-m3.1-flash-free",
7
7
  "family": "minimax",
8
- "verified": "2026-10-19",
8
+ "verified": "2026-10-21",
9
9
  "retention": "zero-retention",
10
10
  "notes": "Flagship coding and agent model on the free tier: 512k output tokens, the widest of any free route, and the fastest measured image reader at 7.7s. Tool calls are stable. It does not support temperature, and models.dev publishes no structured_output flag for it, so JSON output is requested in the prompt rather than negotiated with the API. Measured at 3.1s for a one-word reply.",
11
11
  "limits": {
@@ -14,7 +14,7 @@
14
14
  },
15
15
  "supports": {
16
16
  "reasoning": true,
17
- "temperature": false,
17
+ "temperature": true,
18
18
  "toolCall": true,
19
19
  "structuredOutput": false,
20
20
  "attachment": true