From 5a25ac4fea11898b58db7e99d40476de27c64329 Mon Sep 17 00:00:00 2001 From: Sean Goodwin Date: Wed, 14 Oct 2026 00:57:22 -0700 Subject: [PATCH 1/2] fix(builders): name trustshell 1.6.1, and read the checked version from the doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit npm now serves @hyperdag/trustshell 1.6.1. check:builders hardcoded 1.6.0 twice, so it FAILS on main today (measured locally) and the blocking "BUILDERS.md matches published trustshell" job would turn the next PR in this repo red for a reason unrelated to it. main last ran CI on 10-12, before 1.6.1 shipped. - check-builders.mjs reads the version BUILDERS.md names (exactly one "PUBLISHED — `x.y.z`") and compares THAT with npm. A publish still turns CI red until the doc is updated, but the checker never needs editing again. - BUILDERS.md names 1.6.1. Re-measured on 1.6.1 2026-10-14: `trustshell verify` exits 0 / 1 / 2 for PASS / VETO / NOT_CHECKED, ethers is still an optional peer, the other packages still 404, the six-interface kernel still not on main, and the section 1a curl still returns pass. - section 1a documents the `votes` field the live classify reply now carries. Checker: VERIFIED as committed; FAILED when the doc names 1.6.0; FAILED when it names two versions. Co-Authored-By: Claude Opus 5.5 --- BUILDERS.md | 9 +++++---- scripts/check-builders.mjs | 19 +++++++++++-------- 2 files changed, 16 insertions(+), 12 deletions(-) diff --git a/BUILDERS.md b/BUILDERS.md index 15beea6c..ba58d44c 100644 --- a/BUILDERS.md +++ b/BUILDERS.md @@ -18,7 +18,7 @@ publish X without touching this file. | Thing | State | How to check | |---|---|---| -| **`@hyperdag/trustshell`** | **PUBLISHED — `1.6.0`** (measured 2026-10-05; was `1.4.0` on 2026-10-04). The one package to install. | `npm view @hyperdag/trustshell version` | +| **`@hyperdag/trustshell`** | **PUBLISHED — `1.6.1`** (measured 2026-10-14; was 1.6.0 on 2026-10-05 and 1.4.0 on 2026-10-04). The one package to install. | `npm view @hyperdag/trustshell version` | | `@hyperdag/protocol` | **NOT published** (404) | `npm view @hyperdag/protocol version` | | `@hyperdag/identity-erc8004`, `@hyperdag/reputation-zkp` | **NOT published** (404) | same | | `IdentityRegistry` on Base Sepolia (84532) | **LIVE** — `0x8004A818BFB912233c491871b3d84c89A494BD9e` | any RPC client, or basescan | @@ -31,7 +31,7 @@ publish X without touching this file. npm badge for `@hyperdag/protocol`, a package that does not exist; it misled one of our own agents on 2026-09-08 and was removed on 2026-10-04. -**Published 1.6.0, measured from the tarball on 2026-10-05.** `trustshell verify` +**Published 1.6.1, re-measured 2026-10-14 (first measured on the 1.6.0 tarball, 2026-10-05).** `trustshell verify` exits 0 on PASS or FLAG, 1 on VETO, and 2 when HAL did not decide (NOT_CHECKED, never a pass). Exit 3 is a runtime error and 4 means the command is waiting for a person to answer (ASK). `ethers` (`^6`) is an optional peer: a plain install does not include it. The package uses it @@ -63,8 +63,9 @@ curl -s -X POST https://repid-engine-production.up.railway.app/api/v1/classify \ - **In:** `{text, labels}`. `labels` is optional; if present it must be exactly the three. - **Out:** `{label, latency_ms, by}`, where `label` is `pass`, `veto` or `not-checked` and `by` says what decided (`arithmetic`, `votes`, or `skipped` when nothing was sent). When models voted - it also carries `voters` (every host the text reached) and `deciders` (the two whose answers made - the label), and, only when the operator has questions switched on, a `question`. Read `label`; + it also carries `voters` (every host the text reached), `deciders` (the two whose answers made + the label), `votes` (one `{voter, family, verdict}` per host that answered, measured + 2026-10-14), and, only when the operator has questions switched on, a `question`. Read `label`; the other fields are for showing your user who checked. - **What decides:** a whole-text arithmetic equation is evaluated locally. Prose up to 1,500 characters goes to **two independent free models, which must agree**: both true diff --git a/scripts/check-builders.mjs b/scripts/check-builders.mjs index a7a43b50..77d1c586 100644 --- a/scripts/check-builders.mjs +++ b/scripts/check-builders.mjs @@ -27,12 +27,15 @@ function notChecked(why) { process.exit(2); } -if (!builders.includes('PUBLISHED — `1.6.0`')) { - fail('BUILDERS.md does not name published @hyperdag/trustshell 1.6.0'); -} -if (/PUBLISHED — `1\.4\.0`/.test(builders)) { - fail('BUILDERS.md still names 1.4.0 as the published package'); +// The version is read FROM the doc, not written here. This file used to hardcode `1.6.0` twice, +// so publishing 1.6.1 turned every PR in this repo red until someone edited the CHECKER, which is +// the wrong file: the doc is what an outsider reads. Now a publish still turns CI red until +// BUILDERS.md names the new version, and the check itself never needs touching. +const named = [...builders.matchAll(/PUBLISHED — `(\d+\.\d+\.\d+)`/g)].map((m) => m[1]); +if (named.length !== 1) { + fail(`BUILDERS.md must name exactly one published @hyperdag/trustshell version; it names ${named.length}`); } +const documented = named[0]; if (!builders.includes('exits 0 on PASS or FLAG, 1 on VETO, and 2 when HAL did not decide (NOT_CHECKED, never a pass)')) { fail('BUILDERS.md does not say NOT_CHECKED exits 2 and is never a pass'); } @@ -57,9 +60,9 @@ try { } catch (err) { notChecked(`npm view did not answer: ${String(err?.message ?? err).split('\n')[0]}`); } -if (version !== '1.6.0') { - fail(`npm view @hyperdag/trustshell version is ${version}, and BUILDERS.md says 1.6.0`); +if (version !== documented) { + fail(`npm view @hyperdag/trustshell version is ${version}, and BUILDERS.md says ${documented}`); } console.log('check:builders — VERIFIED'); -console.log(' BUILDERS.md names 1.6.0, exit 2 on NOT_CHECKED, and the optional ethers peer'); +console.log(` BUILDERS.md names ${documented} (= npm), exit 2 on NOT_CHECKED, and the optional ethers peer`); From d0b88e0b8fc4ca19570257c7d398b07125e70f95 Mon Sep 17 00:00:00 2001 From: Sean Goodwin Date: Wed, 14 Oct 2026 00:58:36 -0700 Subject: [PATCH 2/2] docs: stop pinning strangers to trustshell 1.6.0 README told an outside builder to `npm i -g @hyperdag/trustshell@1.6.0` in two places, which installs the old release (no my_job, no kernel client) now that npm serves 1.6.1. The install commands are unpinned: a pinned install goes stale on every publish, which is how this happened. The measured version lives in BUILDERS.md, under check:builders. CLAUDE.md and CONTRIBUTING.md now say 1.6.1 (measured 2026-10-14). Co-Authored-By: Claude Opus 5.5 --- CLAUDE.md | 4 ++-- CONTRIBUTING.md | 2 +- README.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 1d605cc8..9928a471 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -61,8 +61,8 @@ on npm"*. It is **not published** — `npm view @hyperdag/protocol` returns 404, the top of `README.md` without running the query, while the README's own *"Known broken / not live"* table three screens below said plainly that it 404s. **A badge is a link, not a measurement** — same class as reading `-stub` in a filename as evidence about production. -The package an outside builder should install is **`@hyperdag/trustshell`** (`1.6.0` on npm, -MEASURED 2026-10-06; it was 1.3.0 when this line was first written). Two others are published +The package an outside builder should install is **`@hyperdag/trustshell`** (`1.6.1` on npm, +MEASURED 2026-10-14; 1.6.0 on 2026-10-06, 1.3.0 when this line was first written). Two others are published and are not the entry point: `@hyperdag/proof-verifier` (0.2.0, bundled inside trustshell) and `@hyperdag/trustshell-mcp` (1.0.0 from 2026-07-08, older than the `trustshell-mcp` bin that ships inside trustshell itself). See `BUILDERS.md`. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f2a9141b..37e3e348 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -18,7 +18,7 @@ The stranger-facing product is [`@hyperdag/trustshell`](https://github.com/DealA 1. Fork. Branch from `main`. 2. Tests for code you add. `npm ci` then the jobs in `.github/workflows/ci.yml`. 3. No `package.json` version bump unless Sean asked. No `npm publish`. No prod SQL. -4. No “MVP launched.” Published npm is `@hyperdag/trustshell@1.6.0` (2026-10-05). +4. No “MVP launched.” Published npm is `@hyperdag/trustshell@1.6.1` (measured 2026-10-14; `BUILDERS.md` is where this is checked). 5. Open the pull request. MERGE_POLICY: agents may squash-merge when checks are green and the PR is not publish / DDL / secrets. Security: [SECURITY.md](SECURITY.md). Ecosystem map: [BUILDERS.md → How the pieces fit](BUILDERS.md#how-the-pieces-fit). diff --git a/README.md b/README.md index 2431dd57..9b77082c 100644 --- a/README.md +++ b/README.md @@ -165,7 +165,7 @@ install — see **[`@hyperdag/trustshell`](https://github.com/DealAppSeo/trustsh **For an AI tool (Claude Desktop, Cursor, Claude Code).** The checks are also an MCP server: the `trustshell-mcp` bin inside `@hyperdag/trustshell`. Install the package globally, then point the tool's config at the bin: ```bash -npm i -g @hyperdag/trustshell@1.6.0 +npm i -g @hyperdag/trustshell ``` ```json @@ -181,7 +181,7 @@ The separate npm package `@hyperdag/trustshell-mcp` is older (1.0.0, 2026-07-08) | If you're… | Install | What you get | |---|---|---| | A developer building an agent/app **in code** | `npm install @hyperdag/trustshell` | The SDK — HAL verification + ERC-8004 RepID + x402 payments, in your TypeScript/JS | -| Using an **AI tool** (Claude Desktop, Cursor, Claude Code), **no code** | `npm i -g @hyperdag/trustshell@1.6.0`, then the `trustshell-mcp` bin (above) | The checks as AI-callable tools | +| Using an **AI tool** (Claude Desktop, Cursor, Claude Code), **no code** | `npm i -g @hyperdag/trustshell`, then the `trustshell-mcp` bin (above) | The checks as AI-callable tools | | Only verifying **ZK proofs** client-side | `npm install @hyperdag/proof-verifier` | Standalone Plonky3 proof checking (usually bundled with trustshell — rarely installed directly) | **Most people want `@hyperdag/trustshell`. The SDK, the CLI and the MCP server are all in that one package. `proof-verifier` is a building block that ships inside trustshell.**