Repository navigation
agent harness v0.8.1
v0.8.1
A patch release of @judgment-pack/harness, as an attested package asset and a Go module tagged by the release workflow. Two changes, no contract change.
Install the tarball from this release and pin it by the digest in checksums.txt; the Go module by go get github.com/Judgment-Pack/judgment-pack-agent/go@v0.8.1 with go.sum committed.
What v0.8.1 holds
- The packed harness resolves every import inside its own package (#139, pull request #141). The v0.8.0 tarball's
dist/corpus.jsimported the corpus-entry schema by a path that leaves the installed package, so a consumer's bundler could not resolve it. The schema and the one test vector the emitted code reads now ship as package-local copies, held byte-equal to their repository originals by a test. A packed-tarball smoke check installs the tarball into an empty project outside the repository, bundles every supported entrypoint (the five named ones and the modules the./*export exposes) with esbuild, walks the archive's file closure, and fails when a schema is removed. - The Gemini fallback request's model path is encoded the same way in TypeScript and Go (#136, pull request #140): the model id is one path segment, percent-encoded per RFC 3986 with the unreserved set left bare, held by a shared vector file and a mutation row that catches a return to the built-in encoders.
The supported way to consume the package
Through a bundler (the Desk's Vite, esbuild, Vitest). Importing the package directly with Node's ESM loader does not work yet, because the emitted files carry extensionless relative imports; that is tracked as #143 and is not part of this release.
Unchanged
The wire contract, the policy table, every ADR of v0.8.0, the Go module. A consumer pinned to v0.8.0 that bundles the package needs this release; the Go module's only change is the model-path encoder of #136.