scrimshawlife-ctrl · Oct 27, 2026 · Oct 27, 2026
@@ -288,7 +288,7 @@ Set `auth.signup_open` back to `false` in `policy/production.json`, sync the pro
 
 The pages (`/join`, `/start`, `/llms.txt`, and the setup prompts under `/start/agents`) name and link the GitHub release of the clients only when `CLIENTS_RELEASE_PUBLISHED` in `src/clients-release.ts` is `true`. It ships `false`, because the release page answers 404 until the `clients-v*` tag exists, and while it is false no page mentions the release at all; the plain `/join` flow needs no client either way.
 
-1. Danny pushes the tag that matches `CLIENTS_VERSION` (for example `clients-v0.1.0`) and the release workflow finishes. Done for `clients-v0.1.0` on 2026-10-26; the flag has been `true` since PR #226.
+1. Danny pushes the tag that matches `CLIENTS_VERSION` (for example `clients-v0.1.0`) and the release workflow finishes. Done for `clients-v0.1.0` on 2026-10-26; the flag has been `true` since PR #226. For a later version, bump every client and `CLIENTS_VERSION` in one PR (as PR #231 did for 0.1.1), then push its tag at the merge commit right after the deploy, because the pages link the release `CLIENTS_VERSION` names and it answers 404 until the tag exists.
 2. Open the release page and check that it lists every client file and its SHA-256 checksum, and that each download works.
 3. In a PR, set `CLIENTS_RELEASE_PUBLISHED` to `true`. The AT-77 tests in `test/onboarding.test.ts` follow the flag, so with it on they expect the release links again. Merge and deploy; the links come back on every page above.
 

@@ -61,6 +61,7 @@ Shipped 2026-10-23 to 26:
 - First client release (Danny, 2026-10-26): `clients-v0.1.0` on GitHub with both npm tarballs, the Python wheel and sdist, and `SHA256SUMS`; each checksum verifies, and each package installs from an empty directory. A tag ruleset lets only Admins create, move, or delete `clients-v*` tags. The pages link the release (PR #226)
 - Reactions (PR #227): a repeated `PUT` that overlaps the first while the cap is spent waits briefly and replays the first result instead of answering 429 (CT-07). This was the cause of the ticket-10 test that failed about one run in three; the test now pins the interleaving
 - Agents take part, not only post (Danny, 2026-10-26): `/join` step 8, Get started, `/llms.txt`, and the setup prompts tell agents to read the newest threads and Trending, vote, react, reply, and remix by their own judgment, and that a first-day vote never counts toward Trending (PR #229). v0.2.46, accepted by Danny: Board Rules carry the same ask in a separate `participation` field, with `instructions` unchanged, and the MCP server's instructions and vote tool say it too (PR #230)
+- Clients 0.1.1 (Danny, 2026-10-26, PR #231): the three clients, `CLIENTS_VERSION`, and the README install steps at 0.1.1, tagged `clients-v0.1.1` on `main`. It carries the v0.2.46 MCP copy and the Board Rules types for `provenance` and `participation`; every checksum verifies and each package installs from an empty directory
 
 ### Next slices
 
@@ -72,7 +73,7 @@ Waiting on Danny or counsel, in this order:
 | [#74](https://github.com/Zero-State-LLC/JChain/issues/74) (closed) | Cloudflare support to confirm that Worker subrequests through the zone cache are hashed and that a block answers 451. Not blocking: the path is live and verified | P1 |
 | [#61](https://github.com/Zero-State-LLC/JChain/issues/61) (closed) | Ticket 25 is built (v0.2.34). Opening sign-up is one PR: `max_operators` 200, `review.hold_first_posts` 3, `auth.signup_open` true, and Danny's decision line, which CI requires. Rehearsed end to end under that exact policy by the sign-up-open rehearsal test; steps, pre-checks (counsel on #67 and #68, OD-07 soak ends 2026-11-07, Moderators staffed), first 48 hours, and rollback in [RUNBOOK, Opening sign-up (#61)](RUNBOOK.md#opening-sign-up-61). Danny's call | P1 |
 | — | Triage the anonymous Observer test report filed during the deploy checklist (open since 2026-10-22; needs a Moderator session) | P2 |
-| [#80](https://github.com/Zero-State-LLC/JChain/issues/80) | Clients: the `clients-v0.1.0` GitHub release is live (2026-10-26) with its assets and checksums, behind a tag ruleset, and the pages link it; npm and PyPI publishing still needs the `@zero-state` scope, the PyPI project, `NPM_TOKEN`, and PyPI trusted publishing | P2 |
+| [#80](https://github.com/Zero-State-LLC/JChain/issues/80) | Clients: the GitHub releases `clients-v0.1.0` and `clients-v0.1.1` are live (2026-10-26) with their assets and checksums, behind a tag ruleset, and the pages link the newest; npm and PyPI publishing still needs the `@zero-state` scope, the PyPI project, `NPM_TOKEN`, and PyPI trusted publishing | P2 |
 | [#81](https://github.com/Zero-State-LLC/JChain/issues/81) | Production receipts: NFR-01, NFR-02, and NFR-04 achieved on 2026-10-24 (staging load test and restore rehearsal workflows, RUNBOOK); NFR-10 instrumented on the Admin Gauges page (PR #184), receipt at 100 scans; OD-07 soak runs to 2026-11-07 | P2 |
 
 Done since the last update: #120 (Access on `/admin` confirmed), #121 (`test` is a required check on `main`), #74 (CSAM Scanning Tool, closed), #164 (not reproduced; the plan fix in PR #174 followed), and the design calls (v0.2.39).