opencode-harness-kit 0.5.1 → 0.5.4

package/CHANGELOG.md

@@ -12,6 +12,109 @@ is not happening.
 
 ---
 
+## [0.5.4] — 2026-10-21
+
+Published. The tag is what cut it: `git tag v0.5.4 && git push origin main
+v0.5.4`, and the publish job watches for exactly that.
+
+A patch, and the patch is the publish path. 0.5.3 was the first release to
+reach the registry since the rename, and it reached it through trusted
+publishing with a signed provenance statement - so the path works, and this
+release is the one that says so where a reader will look for it.
+
+### Changed
+
+- **The npm trusted publisher is configured for
+  `pham-canh/opencode-harness-kit`**: `ci.yml`, no environment, publish and
+  stage. It is the one thing that was missing when 0.5.2 was refused, and it
+  is set now. The re-point is an account change on npm, so it needed the
+  account's second factor - and a rename is not a thing npm does for you.
+
+- **The publish token secret is gone.** The job can publish with a token
+  when there is one, and the secret was set while 0.5.3 was cut, because a
+  release that cannot publish is not a release. It is removed now that the
+  OIDC path is proven: a long-lived token in the repository is a secret to
+  rotate for a path that is not being used, and npm is restricting the
+  tokens that bypass two-factor authentication for direct publishing in
+  January 2027, so the token path was on its way out anyway.
+
+## [0.5.3] — 2026-10-21
+
+Published. The tag is what cut it: `git tag v0.5.3 && git push origin main
+v0.5.3`, and the publish job watches for exactly that.
+
+This is the release that carries the rename, because 0.5.2 - the release the
+rename was written for - never reached the registry.
+
+### Changed
+
+- **The repository is now `pham-canh/opencode-harness-kit`**, renamed from
+  `pham-canh/space-harness`. The npm package has been
+  `opencode-harness-kit` since 0.4.0, and the README's title with it; the
+  repository was the last one still carrying the old name, and a reader who
+  installed the package and followed the link landed somewhere that did not
+  look like the thing they had installed. GitHub redirects the old URL, so
+  the links that already exist keep working.
+
+  The npm page showed the old name until this release, and the reason is
+  worth writing down, because nothing about the rename explains it: the page
+  reads the `repository` and `homepage` out of the manifest of the LATEST
+  PUBLISHED version, and the latest published version was 0.5.1, whose
+  manifest was written before the rename. The manifest names the new
+  repository now, and this is the release that carries it.
+
+### Fixed
+
+- **The publish job now checks the OIDC claim against `package.json` before
+  it publishes.** npm matches the trusted publisher's repository against the
+  claim, and the claim names the repository the workflow ran in - so a
+  renamed repository stops publishing, with an exchange error that does not
+  name the field that was wrong. The gate says which side is which and
+  prints the command that fixes it.
+
+- **The installer no longer says "installed" when it replaced nothing.**
+  `existsSync` follows a symlink, so a link whose target no longer exists
+  reads as "not there" - and the branch that replaces what the installer put
+  there was never reached. `symlinkSync` then threw EEXIST over the link
+  that was already there, the warning was printed where nobody reads it, and
+  the install carried on. After the rename that is exactly the state a kit
+  installed from the old path was in: the skills, the prompts and GLOBAL.md
+  kept pointing at a directory that had moved, and `verify` then found
+  seventeen broken paths. `lstat` does not follow the link, and it is what
+  decides whether there is something to replace.
+
+### Removed
+
+- **The coverage report is no longer committed.** 131 files of it, four
+  megabytes, changing on every run, and nobody reads a diff of it. It is
+  ignored now and produced on demand.
+
+- **The two shell scripts are gone from the repository**: the demo setup
+  helper, which pointed at copies of two tools that live one directory up
+  with their own history, and the take script that filmed the published
+  demo, which is a shell file with one machine's paths in it and goes stale
+  the moment the thing it films changes. The recording guide is on the
+  machine that records.
+
+## [0.5.2] — 2026-10-21
+
+**Not published.** The tag was cut and pushed, the publish job ran, and npm
+refused the publish - so there is no 0.5.2 on the registry. The changes
+written for it shipped in 0.5.3.
+
+What npm said was `OIDC token exchange error - package not found`, which
+reads like a missing package. The package was there. The trusted publisher
+was not: npm reports no trusted publisher configured for this package, and
+the repository had been renamed, so a publisher that named the old
+repository would not have matched the claim the runner presents either. The
+package's name is in the error, and the field that was wrong is not.
+
+The entry this release was going to carry said that "the npm trusted
+publisher was re-pointed at the new name". It had not been. The re-point is
+an account change on npm and it needs the account's second factor, and
+nothing had done it. A changelog that says a thing has been done that has
+not been done is worse than one that says nothing.
+
 ## [0.5.1] — 2026-10-21
 
 Published. The tag is what cut it: `git tag v0.5.1 && git push origin main
@@ -1130,20 +1233,27 @@ silent in the worst way:
 
 ---
 
-[Unreleased]: https://github.com/pham-canh/space-harness/compare/v0.4.3...HEAD
-[0.4.4]: https://github.com/pham-canh/space-harness/compare/v0.4.3...v0.4.4
-[0.4.3]: https://github.com/pham-canh/space-harness/compare/v0.4.2...v0.4.3
-[0.4.2]: https://github.com/pham-canh/space-harness/compare/v0.4.1...v0.4.2
-[0.4.1]: https://github.com/pham-canh/space-harness/compare/v0.4.0...v0.4.1
-[0.4.0]: https://github.com/pham-canh/space-harness/compare/v0.3.9...v0.4.0
-[0.3.9]: https://github.com/pham-canh/space-harness/compare/v0.3.8...v0.3.9
-[0.3.8]: https://github.com/pham-canh/space-harness/compare/v0.3.7...v0.3.8
-[0.3.7]: https://github.com/pham-canh/space-harness/compare/v0.3.6...v0.3.7
-[0.3.6]: https://github.com/pham-canh/space-harness/compare/v0.3.5...v0.3.6
-[0.3.5]: https://github.com/pham-canh/space-harness/compare/v0.3.4...v0.3.5
-[0.3.4]: https://github.com/pham-canh/space-harness/compare/v0.3.1...v0.3.4
-[0.3.1]: https://github.com/pham-canh/space-harness/compare/v0.3.0...v0.3.1
-[0.3.0]: https://github.com/pham-canh/space-harness/compare/v0.2.1...v0.3.0
-[0.2.1]: https://github.com/pham-canh/space-harness/compare/v0.2.0...v0.2.1
-[0.2.0]: https://github.com/pham-canh/space-harness/compare/v0.1.0...v0.2.0
-[0.1.0]: https://github.com/pham-canh/space-harness/releases/tag/v0.1.0
+[Unreleased]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.4...HEAD
+[0.5.4]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.3...v0.5.4
+[0.5.3]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.2...v0.5.3
+[0.5.2]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.1...v0.5.2
+[0.5.1]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.5.0...v0.5.1
+[0.5.0]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.4.6...v0.5.0
+[0.4.6]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.4.5...v0.4.6
+[0.4.5]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.4.4...v0.4.5
+[0.4.4]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.4.3...v0.4.4
+[0.4.3]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.4.2...v0.4.3
+[0.4.2]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.4.1...v0.4.2
+[0.4.1]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.4.0...v0.4.1
+[0.4.0]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.9...v0.4.0
+[0.3.9]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.8...v0.3.9
+[0.3.8]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.7...v0.3.8
+[0.3.7]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.6...v0.3.7
+[0.3.6]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.5...v0.3.6
+[0.3.5]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.4...v0.3.5
+[0.3.4]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.1...v0.3.4
+[0.3.1]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.3.0...v0.3.1
+[0.3.0]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.2.1...v0.3.0
+[0.2.1]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.2.0...v0.2.1
+[0.2.0]: https://github.com/pham-canh/opencode-harness-kit/compare/v0.1.0...v0.2.0
+[0.1.0]: https://github.com/pham-canh/opencode-harness-kit/releases/tag/v0.1.0

package/CONTRIBUTING.md

@@ -139,7 +139,7 @@ repository secret to a granular token scoped to `opencode-harness-kit` with
 if it is absent the job uses OIDC.
 
 ```bash
-gh secret set NPM_TOKEN --repo pham-canh/space-harness
+gh secret set NPM_TOKEN --repo pham-canh/opencode-harness-kit
 ```
 
 > **`gh secret set` takes the secret NAME as its first argument**, and the
@@ -213,7 +213,7 @@ To set it without the script, the command is:
 ```bash
 npm trust github opencode-harness-kit \
   --file ci.yml \
-  --repo pham-canh/space-harness \
+  --repo pham-canh/opencode-harness-kit \
   --allow-publish --allow-stage-publish -y
 ```
 
@@ -222,7 +222,7 @@ The configuration it writes is:
 | field | value |
 |---|---|
 | Organization or user | `pham-canh` |
-| Repository | `space-harness` |
+| Repository | `opencode-harness-kit` |
 | Workflow filename | `ci.yml` (the filename only, not a path) |
 | Environment name | **empty** |
 | Allowed actions | `npm publish` and `npm stage publish` |
@@ -236,7 +236,7 @@ The workflow is the one in `.github/workflows/ci.yml`, and the claims it
 presents are printed by the publish job before it tries:
 
 ```
-repository    pham-canh/space-harness
+repository    pham-canh/opencode-harness-kit
 workflow file ci.yml
 environment   (absent) - the trusted publisher must name NO environment
 owner         pham-canh

package/README.md

@@ -1,6 +1,6 @@
 # opencode-harness-kit
 
-[![CI](https://github.com/pham-canh/space-harness/actions/workflows/ci.yml/badge.svg)](https://github.com/pham-canh/space-harness/actions/workflows/ci.yml)
+[![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)
 [![npm](https://img.shields.io/npm/v/opencode-harness-kit.svg)](https://www.npmjs.com/package/opencode-harness-kit)
 
 <p align="center">
@@ -8,9 +8,9 @@
 </p>
 
 *Four minutes forty-seven seconds, recorded live from a real terminal and
-narrated. The take script and the voiceover are in [`video/`](video/), and
-rebuilding it is documented there — including the two mistakes that cost the
-most time, so the next person does not repeat them.*
+narrated — every command on screen is typed and executed while the camera
+runs. The voiceover is in [`video/`](video/), along with what it took to
+record it and the two mistakes that cost the most time.*
 
 *It was recorded against an earlier version of the kit: the numbers it names
 are the ones from then, and the ones below are the ones now.*
@@ -31,7 +31,7 @@ your side — `npx` only downloads the published kit. Prefer git? The same three
 steps from a checkout (see [Install](#install)):
 
 ```bash
-git clone https://github.com/pham-canh/space-harness.git
+git clone https://github.com/pham-canh/opencode-harness-kit.git
 ./bin/oc-harness.mjs init
 ```
 
@@ -67,6 +67,33 @@ src/                         ← no model name anywhere in here
 Same plugin source, twelve shipped profiles, twelve different behaviours. The
 test suite asserts that rather than taking it on faith.
 
+### How a request travels
+
+```mermaid
+flowchart LR
+  P[profile JSON<br/>model, effort, fallback, retention] --> C[oc-harness use<br/>compiles the profile]
+  C --> CFG[~/.config/opencode/opencode.jsonc<br/>agent.&lt;lane&gt;.model]
+  CFG --> PL[the plugin: guard, prune, router, telemetry]
+  PL --> LANES[10 lanes<br/>each on the model built for it]
+  LANES --> PR[prune: old tool output<br/>becomes a stub]
+  LANES --> GD[guard: denied commands<br/>and writes outside the project]
+  LANES --> RT[router: a spent route<br/>moves to the next rung]
+  LANES --> TL[telemetry: what each lane<br/>actually cost]
+```
+
+Four things happen to a request, and they are four separate files:
+
+| | |
+|---|---|
+| `src/guard.ts` | refuses the commands the kit never allows, and any write outside the project |
+| `src/prune.ts` | replaces old tool output with a one-line stub, so the window holds the work and not the noise |
+| `src/router.ts` | when a route is spent, moves the lane to the next rung of its own chain |
+| `src/telemetry.ts` | records what each lane actually cost, so `oc-harness lanes` can say which ones earn their place |
+
+The model for a lane is in the **config**, not in a prompt and not in a file
+the agent reads. That is the whole design: the answers are data, and a data
+edit is reviewable.
+
 ## A fleet, not a model
 
 The default profile is a **fleet**: ten jobs, ten free models, one session.
@@ -690,8 +717,8 @@ Without registry access, the checkout path works identically:
 
 ```bash
 pkg install nodejs git
-git clone https://github.com/pham-canh/space-harness.git
-./space-harness/bin/oc-harness.mjs init
+git clone https://github.com/pham-canh/opencode-harness-kit.git
+./opencode-harness-kit/bin/oc-harness.mjs init
 ```
 
 The kit writes to `$HOME/.config/opencode` like everywhere else, so there is
@@ -863,6 +890,38 @@ session, so switching happens at the next session, not mid-flight. What a
 plugin *can* do is move a lane to the next rung of its chain before the
 session starts.
 
+## What is next, and what is not measured yet
+
+The claims this project makes are measured, and where a measurement has not
+happened the claim is written down as a gap rather than as a fact. These are
+the open ones.
+
+**The pruner's rule was measured on one task.** Keeping the newest copy of
+each distinct tool output instead of a window on recent calls cut the input
+tokens by 69% and the wall time by 60% on the long-task A/B. One task is one
+workload. It needs the same treatment on a repository that is not this one,
+and on a session that runs for hours rather than minutes.
+
+**The reviewer's "you never fix" is an instruction, not a boundary.** The
+measurement of it came out even: the kit's reviewer lane and a default agent
+behaved the same on a review task, and a task that says "fix it" overrode
+the lane. The kit's own loop keeps the line by never asking a reviewer to
+fix anything. A guard that cannot be overridden by a task is worth having,
+and that is not built yet.
+
+**The nightly A/B needs a provider key on the repository.** The workflow
+exists, it runs, and it is skipped until the key is set — the variable
+`HAS_OPENCODE_KEY` says the secret is there. The numbers in
+[eval/RESULTS.md](eval/RESULTS.md) are the ones taken by hand.
+
+**The TypeScript pilot is one public repository.** It is now a real one
+(`typesense-js`, pinned by commit) rather than a private tree, which is what
+made it checkable. Two languages are not a survey.
+
+**The lanes are ten because ten models were available.** That is a
+hypothesis about the tier, not a number. `oc-harness lanes` counts the
+requests and says which lanes were never used; cutting them is a data edit.
+
 ## Development
 
 ```bash
@@ -907,9 +966,15 @@ and the measurements behind each choice.
 
 [`CHANGELOG.md`](CHANGELOG.md) records what each release changed and, for the
 releases before this one, what was broken in it — the silent failures that a
-config could look correct through. [`MIGRATION.md`](MIGRATION.md) covers
-0.2.x → 0.3.0: the profile ids changed, the config layout changed, and the
-telemetry file now means something different.
+config could look correct through. [`MIGRATION.md`](MIGRATION.md) covers the
+two upgrades that ask something of you: 0.2.x → 0.3.0 (the profile ids
+changed, the config layout changed, the telemetry file now means something
+different) and 0.3.x → 0.4.x (the guard started refusing in code what it used
+to only suggest, and the pre-commit hook started running your project's
+tests instead of the kit's).
+
+[`docs/EXIT-CODES.md`](docs/EXIT-CODES.md) lists what every command returns
+when it fails, so a script can tell "the kit says no" from "the kit broke".
 
 ## Contributing
 

package/SECURITY.md

@@ -12,7 +12,7 @@
 ## Reporting a vulnerability
 
 Please report privately through GitHub's
-[private vulnerability reporting](https://github.com/pham-canh/space-harness/security/advisories/new)
+[private vulnerability reporting](https://github.com/pham-canh/opencode-harness-kit/security/advisories/new)
 rather than opening a public issue.
 
 Include the affected version, a reproduction, and the expected behaviour.
@@ -21,7 +21,7 @@ plan within 7 days.
 
 ## Scope
 
-`space-harness` runs agent subprocesses and reads harness config. Reports
+`opencode-harness-kit` runs agent subprocesses and reads harness config. Reports
 that are in scope include path traversal when resolving a capability
 profile, command injection through harness config values, and any way a
 harness writes outside its configured working directory.

package/bin/oc-harness.mjs

@@ -706,19 +706,32 @@ function linkOne(src, dest) {
   }
   if (ours) return
 
-  if (existsSync(dest)) {
+  if (isLink) {
+    // A symlink is a symlink whether or not its target exists, and a
+    // DANGLING one is still this installer's to replace.
+    //
+    // `existsSync` follows the link, so it says false for a link whose
+    // source has moved - the repository was renamed, or the kit was
+    // reinstalled somewhere else. The old code asked `existsSync` whether
+    // the destination was taken, got "no", and then tried to create a link
+    // over an existing one: EEXIST, printed as a warning nobody reads, and
+    // the install reported success. Every skill, prompt and rule kept
+    // pointing at a directory that is no longer there, and `verify` found
+    // seventeen broken paths afterwards.
+    //
+    // The test that decides whether to replace something is `lstat`, which
+    // does not follow the link.
+    rmSync(dest, { force: true })
+  } else if (existsSync(dest)) {
     // Replace only what this installer put there. The old code treated "not
     // already our link" as "safe to delete" and called `rmSync` with
     // `recursive: false`, which succeeds on a plain file: a hand-written
     // agent was deleted and replaced by a symlink without a word. A real
     // directory is left alone too -- unlinking it is not this installer's
     // call to make.
-    if (!isLink) {
-      const kind = lstatSync(dest).isDirectory() ? "directory" : "file"
-      console.log(`  ${yellow("!")} ${stamp(`left alone: ${dest} is a real ${kind} and was not ours to replace`)}`)
-      return
-    }
-    rmSync(dest, { force: true })
+    const kind = lstatSync(dest).isDirectory() ? "directory" : "file"
+    console.log(`  ${yellow("!")} ${stamp(`left alone: ${dest} is a real ${kind} and was not ours to replace`)}`)
+    return
   }
 
   try {

package/eval/RESULTS.md

@@ -146,6 +146,115 @@ That is the mechanism the whole kit rests on, and it is the one thing the
 correlation in Results 1 and 2 could not show. The kit does not shrink what it
 costs; it shrinks what the agent drags along behind it.
 
+## The A/B on this repository, 10 reps per arm
+
+    node eval/prepare.mjs --repo . --ref <sha> --name self
+    node eval/ab.mjs --target <scratch>/self --suite eval/tasks-self.json --reps 10
+
+**The subject is this repository at a pinned commit**, so the run is
+reproducible: `git clone && git checkout <sha>` and the same command. The
+previous suite ran against a private repository, which meant a result nobody
+else could check.
+
+Six tasks, ten reps per arm, 120 agent runs: four lookups and two edits. The
+lookups are graded on the `file:line` the agent cited, read out of the
+snapshot; the edits are graded on the file after the run.
+
+**Both arms ran on the same model**, `opencode/minimax-m3.1-flash-free`, and
+the report prints it. The kit-off arm used to run with an empty config, so
+opencode picked its own default: not the model the kit-on arm was on, and
+not a model that answered - four kit-off runs hit the 600-second ceiling
+with no output at all, and a timed-out run has zero tools and zero context,
+so it entered the medians as a fast, empty, wrong answer.
+
+| metric (median) | kit on | kit off |
+| --- | --- | --- |
+| **correct** | **54/60** | **55/60** |
+| tool calls | 12.5 | 8 |
+| read calls | 3 | 2 |
+| narrow reads | 66.7% | 66.7% |
+| grep/glob calls | 3 | 2 |
+| steps | 9 | 6 |
+| input tokens | 56,205 | 10,540 |
+| final context | 39,928 | 12,718 |
+| wall seconds | 43 | 21 |
+| paths written outside the target | 0 | 0 |
+
+| per task | kit on | kit off |
+| --- | --- | --- |
+| `read-control` | 10/10 | 10/10 |
+| `read-multi-denylist` | 8/10 | 8/10 |
+| `read-multi-gate` | 6/10 | 7/10 |
+| `read-two-files` | 10/10 | 10/10 |
+| `edit-rename` | 10/10 | 10/10 |
+| `edit-multi` | 10/10 | 10/10 |
+
+### What this says
+
+**On correctness, the kit is a tie.** 54 against 55, on sixty runs a side.
+That is inside the noise of a single task flipping, and it is the opposite
+of what the previous version of this file said. A second run of the same
+120 runs - same subject, same suite, same model, a different day of model
+traffic - gave **55/60 against 54/60**, the other way. Two measurements
+put the tie on either side of zero, which is what a tie looks like from
+both ends.
+
+**On everything else, the kit is a cost.** It spends **5.3x the input
+tokens** and takes **twice as long**, and it makes **more** tool calls.
+Those are the honest numbers.
+
+**The previous conclusion was the grader's fault, and it is worth writing
+down.** The earlier run said 52/60 against 59/59 - the kit looked clearly
+worse - and the reason was that the grader could not read a citation
+written as two markdown fields:
+
+    **File:** `src/profile.js`
+    **Line:** 105
+
+The old pattern stopped at the newline, so the file and the number were
+never paired, the citation was lost, and the answer was scored wrong. The
+kit's own instructions tell the agent to cite a file and a line, and the
+shape the kit produces is the shape the grader could not read. The kit-off
+arm had no such instructions, answered in prose, and was graded by a
+pattern that handled prose.
+
+Re-scoring the EARLIER run with the fixed grader - the same 120 agent runs,
+the same answers, only the grader changed - gives **34/40 against 30/40** on
+the four lookup tasks, the kit ahead. A harness that measures the harness
+is worse than one that measures nothing.
+
+### What this does not say
+
+It does not say the kit is not worth it. It says the kit's value is **not in
+short lookups**, and this suite only contains short lookups and two small
+edits. The value it does have is in two places this suite cannot see:
+
+- **Long sessions.** The pruner removes **65-80% of the context** across real
+  sessions, depending on which sessions it is measured over
+  (`npm run measure:prune`), and a task that fits in one read never gets
+  near the point where pruning matters. The long-task A/B below is the
+  measurement of that.
+- **Process.** A `reviewer` that reviews and does not edit, a `verify` that
+  runs the checks and does not fix them, a `space-finish` that hands the
+  publish decision to a human. Those are behaviours, not accuracy, and a
+  grader that counts correct answers cannot see them. The process section
+  below measures what it can - and what it found is that the lane and the
+  default agent behave the same, and that a task saying "fix it" overrides
+  the lane.
+
+The honest position is a trade, and it is now a trade with a number on it:
+**the kit costs about five times the input tokens on a small task, gets the
+answer right about as often, and buys process discipline and an 80% smaller
+context on a long one.** Whether that is worth it depends on whether the
+work is long. A repo of one-file lookups should not install this.
+
+The narrow-read share is worth one more line. The kit's instructions say
+*locate before you read*, and the share of reads that were bounded was
+**the same on both sides, 66.7%** - the rule is followed, and on a
+one-file question following it is waste either way. A fleet that routes
+each job to the model built for it is the other half of what the kit
+offers, and this suite uses one model on both sides, so it cannot see that.
+
 ## The A/B on TypeScript, against a PUBLIC subject
 
     node eval/prepare.mjs --clone https://github.com/typesense/typesense-js \

package/lanes.schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://github.com/pham-canh/space-harness/lanes.schema.json",
+  "$id": "https://github.com/pham-canh/opencode-harness-kit/lanes.schema.json",
   "title": "OpenCode harness lane table",
   "description": "The jobs a fleet can hand out. A lane says what it is for and nothing about models: a profile says which lanes it enables and which model serves each one. The lane table is the single list of lane names in the kit; `src/profile.js` reads it, `src/config.js` compiles it into the generated config, and `profiles/schema.json` must name the same lanes.",
   "type": "object",

package/package.json

@@ -1,15 +1,15 @@
 {
   "name": "opencode-harness-kit",
-  "version": "0.5.1",
+  "version": "0.5.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.",
   "license": "MIT",
-  "homepage": "https://github.com/pham-canh/space-harness#readme",
+  "homepage": "https://github.com/pham-canh/opencode-harness-kit#readme",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/pham-canh/space-harness.git"
+    "url": "git+https://github.com/pham-canh/opencode-harness-kit.git"
   },
   "bugs": {
-    "url": "https://github.com/pham-canh/space-harness/issues"
+    "url": "https://github.com/pham-canh/opencode-harness-kit/issues"
   },
   "type": "module",
   "main": "./dist/index.js",

package/profiles/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://github.com/pham-canh/space-harness/profiles/schema.json",
+  "$id": "https://github.com/pham-canh/opencode-harness-kit/profiles/schema.json",
   "title": "OpenCode harness profile",
   "description": "Everything that changes when you change model. Plugins read this file and contain no model names of their own.",
   "type": "object",