docs: record 0.1.1 as the published release status

AGENTS.md

@@ -26,7 +26,7 @@ subcommand that nudges idle panes from the content-free Inbox summary without co
 Messages (ADR-0008). The live launch is worktree-enabled, with per-Worker isolated Task
 worktrees (ADR-0015).
 
-`0.1.0` is published to npm. The first publish was a one-time manual `npm publish`
+The package is published to npm. The first publish was a one-time manual `npm publish`
 (npm OIDC Trusted Publishing can only attach to a package that already exists); from
 `0.1.1`, a published GitHub Release runs `.github/workflows/publish.yml` and publishes
 via OIDC with provenance — no long-lived npm secret ever enters CI. `docs/README.md`

CLAUDE.md

@@ -26,7 +26,7 @@ subcommand that nudges idle panes from the content-free Inbox summary without co
 Messages (ADR-0008). The live launch is worktree-enabled, with per-Worker isolated Task
 worktrees (ADR-0015).
 
-`0.1.0` is published to npm. The first publish was a one-time manual `npm publish`
+The package is published to npm. The first publish was a one-time manual `npm publish`
 (npm OIDC Trusted Publishing can only attach to a package that already exists); from
 `0.1.1`, a published GitHub Release runs `.github/workflows/publish.yml` and publishes
 via OIDC with provenance — no long-lived npm secret ever enters CI. `docs/README.md`

README.md

@@ -46,7 +46,7 @@ crew requires **Node.js `>=24.15`**. Its State Store — the single database fil
 keeps all shared state — uses the built-in `node:sqlite` module, which only ships with
 Node 24 and later.
 
-`0.1.0` is published to npm. Install it globally:
+crew is published to npm. Install it globally:
 
 ```sh
 npm install -g @dichovsky/crew

docs/README.md

@@ -59,10 +59,10 @@ the same plan), the live tmux Launcher and Relay with per-Worker isolated git wo
 concurrent use and security attacks, and the `crew ui` Console — a dashboard reachable
 only from your own computer, with live updates (SSE) and Operator actions.
 
-`0.1.0` is published to npm as the first release. Because npm's OIDC Trusted Publishing
-can only attach to a package that already exists, that first publish was a one-time
-manual `npm publish` (so `0.1.0` carries no CI provenance); from `0.1.1` onward,
-publishing a GitHub Release runs
+`0.1.1` is the current published release on npm and the first published through the OIDC
+pipeline, so it carries build provenance. `0.1.0` does not: npm's OIDC Trusted Publishing
+can only attach to a package that already exists, so the first publish was a one-time
+manual `npm publish`. From `0.1.1` onward, publishing a GitHub Release runs
 [`.github/workflows/publish.yml`](../.github/workflows/publish.yml), which publishes to
 npm via OIDC — no long-lived npm secret ever enters CI — with provenance. The canonical
 [release-gate table](./design/product-spec.md#release-gates) records the six gates that

docs/design/decisions.md

@@ -24,10 +24,11 @@ restate them.
 The executable is `crew`, the Workspace directory `.crew/`, and the State Store
 `.crew/state/crew.db`. The unscoped npm package name `crew` is taken, so the package
 publishes under the maintainer's namespace as `@dichovsky/crew`
-(`npm install -g @dichovsky/crew`; the installed command is still `crew`). `0.1.0` is
-published: the first publish was a one-time manual `npm publish` (npm OIDC Trusted
-Publishing can only attach to a package that already exists), and from `0.1.1` a
-published GitHub Release publishes via OIDC through `.github/workflows/publish.yml`.
+(`npm install -g @dichovsky/crew`; the installed command is still `crew`). The package is
+published to npm: the first publish (`0.1.0`) was a one-time manual `npm publish` (npm
+OIDC Trusted Publishing can only attach to a package that already exists), and from
+`0.1.1` a published GitHub Release publishes via OIDC through
+`.github/workflows/publish.yml`.
 (`1.0.0` is reserved for a later stability milestone.)
 
 ### DEC-8 — Runtime and build

docs/design/product-spec.md

@@ -105,11 +105,12 @@ requires one process that stays alive for as long as the tmux session does.
 ## Release gates
 
 This is the **canonical release-gate list**. Other documents reference it and must not keep a
-separate copy. The first publish (`0.1.0`) has shipped to npm. Because npm's OIDC Trusted Publishing
-can only attach to a package that already exists, `0.1.0` was published once by hand;
-from `0.1.1` on, a published GitHub Release runs `.github/workflows/publish.yml`, which
-publishes via OIDC with provenance and no stored npm secret (see
-[publishing.md](../release/publishing.md)). The
+separate copy; the **current published version** likewise lives only in
+[docs/README.md](../README.md). crew has shipped to npm. Because npm's OIDC Trusted
+Publishing can only attach to a package that already exists, the first release (`0.1.0`)
+was published once by hand; from `0.1.1` on, a published GitHub Release runs
+`.github/workflows/publish.yml`, which publishes via OIDC with provenance and no stored
+npm secret (see [publishing.md](../release/publishing.md)). The
 SQLite-stress and Security-review gates are closed, and the Relay-proof gate's full
 end-to-end test — a launch against real tmux with a fake Participant standing in for a real
 CLI — is in place. Every part of the remaining gates that a machine