opencode-harness-kit 0.6.2 → 0.6.3

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.
Files changed (3) hide show
  1. package/CHANGELOG.md +71 -0
  2. package/README.md +0 -16
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -12,6 +12,77 @@ is not happening.
12
12
 
13
13
  ---
14
14
 
15
+ ## [0.6.3] — 2026-10-23
16
+
17
+ Nothing here changes the runtime. The plugin, the CLI and `dist/` are
18
+ byte-for-byte what 0.6.2 shipped; this release is the front page and the
19
+ packaging metadata catching up with decisions already made.
20
+
21
+ ### Removed
22
+
23
+ - **The demo media is gone from the repository.** `docs/demo/pitch.mp4`
24
+ (12.5 MB) and `docs/demo-loop.gif` are deleted, and the README no longer
25
+ embeds them. The recording lives on in the private
26
+ [`pham-canh/video`](https://github.com/pham-canh/video) repo. Two reasons
27
+ it had to leave this one: the `.mp4` was never shipped by npm (`files`
28
+ covers `docs/*.md` only), so the README rendered on npmjs.com carried a
29
+ `<video>` tag whose source could not exist — a 404 embed on the public
30
+ page; and a repo whose pitch is "the metadata is the truth" was weighting
31
+ its own checkout with twelve megabytes nobody could watch.
32
+
33
+ ### Fixed
34
+
35
+ - **The lockfile answered for a version two releases behind.**
36
+ `package-lock.json` still said `0.5.8` while `package.json` said `0.6.2`,
37
+ and carried a `peerDependencies` block the manifest no longer has. Both are
38
+ synced now, by hand rather than a regenerating `npm install`, so the locked
39
+ dependency versions are untouched.
40
+
41
+ ## [0.6.2] — 2026-10-23
42
+
43
+ Published. Tag `v0.6.2`.
44
+
45
+ ### Fixed
46
+
47
+ - **Transient catalogue errors stopped benching live routes.** When
48
+ `oc-harness doctor` or the router asked models.dev and the request failed
49
+ for a reason other than "this model is withdrawn" — a timeout, a rate
50
+ limit, a network blip — the failure was percolating into the route health
51
+ as if the model itself were dead, and a live route got benched on evidence
52
+ that was about the network, not the model. The distinction now matters:
53
+ transient errors are retried and reported as transient; only a confirmed
54
+ `status: "deprecated"` out of the catalogue marks a route unhealthy.
55
+
56
+ ## [0.6.1] — 2026-10-23
57
+
58
+ Published. Tag `v0.6.1`.
59
+
60
+ ### Added
61
+
62
+ - **A `flint-40b-free` profile, published with its retention verdict.** A
63
+ same-size free model beside the fleet's usual rungs, and the tenth free
64
+ model in the default fleet needed a lane to run in, so the build assigns
65
+ it.
66
+
67
+ ### Fixed
68
+
69
+ - **The fleet no longer routes through a withdrawn model.**
70
+ `minimax-m3.1-flash-free` was marked deprecated in the catalogue while the
71
+ default fleet still carried it in a lane; `flint-40b-free` takes its place
72
+ in the default chains.
73
+
74
+ - **`use` and `install` write their files atomically.** The config and the
75
+ health file are now written to a sibling temp file and renamed, so a
76
+ `install` interrupted mid-write can no longer leave a half-written config
77
+ behind. (A failure found its way through this when the code called
78
+ `renameSync` it had never imported; the import is there now.)
79
+
80
+ - **A publish job re-run against an already-published tag is green**, not a
81
+ red crash on E409.
82
+
83
+ - **eval's `padEnd` did not coerce its arguments to strings**, and died on a
84
+ numeric task id.
85
+
15
86
  ## [0.6.0] — 2026-10-22
16
87
 
17
88
  Published. The tag is what cut it: `git tag v0.6.0 && git push origin
package/README.md CHANGED
@@ -3,18 +3,6 @@
3
3
  [![CI](https://github.com/pham-canh/opencode-harness-kit/actions/workflows/ci.yml/badge.svg)](https://github.com/pham-canh/opencode-harness-kit/actions/workflows/ci.yml)
4
4
  [![npm](https://img.shields.io/npm/v/opencode-harness-kit.svg)](https://www.npmjs.com/package/opencode-harness-kit)
5
5
 
6
- <p align="center">
7
- <video src="docs/demo/pitch.mp4" width="720" controls></video>
8
- </p>
9
-
10
- *Four minutes forty-seven seconds, recorded live from a real terminal and
11
- narrated — every command on screen is typed and executed while the camera
12
- runs. The voiceover is in [`video/`](video/), along with what it took to
13
- record it and the two mistakes that cost the most time.*
14
-
15
- *It was recorded against an earlier version of the kit: the numbers it names
16
- are the ones from then, and the ones below are the ones now.*
17
-
18
6
  A harness kit for [OpenCode](https://opencode.ai) that is **model-agnostic by
19
7
  construction**. Switching models is a data edit, not a code change.
20
8
 
@@ -22,10 +10,6 @@ construction**. Switching models is a data edit, not a code change.
22
10
  npx -y opencode-harness-kit init # pick a free model, then install + verify
23
11
  ```
24
12
 
25
- <p align="center">
26
- <img src="docs/demo-loop.gif" width="760" alt="oc-harness list showing the model-agnostic profiles, then oc-harness verify reporting a consistent install">
27
- </p>
28
-
29
13
  then restart opencode. That is the whole quickstart. No npm account needed on
30
14
  your side — `npx` only downloads the published kit. Prefer git? The same three
31
15
  steps from a checkout (see [Install](#install)):
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-harness-kit",
3
- "version": "0.6.2",
3
+ "version": "0.6.3",
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",