Release status stale: 0.1.1 shipped but docs still record 0.1.0

[dichovsky]

0.1.1 is published (npm dist-tag latest is 0.1.1, git tag v0.1.1 exists, package.json says 0.1.1), but the docs still record 0.1.0 as the published state: README.md:47 ("0.1.0 is published to npm. Install it globally"), docs/README.md:62 — the self-declared "single source of truth for release status" — plus docs/design/decisions.md (DEC-7), docs/design/product-spec.md:107, and CLAUDE.md/AGENTS.md.

Impact: the designated single source of truth for release status no longer reflects the latest published release, and the surrounding docs echo the stale state.

Acceptance: docs/README.md's readiness section records that 0.1.1 shipped via the OIDC pipeline, and the echoing passages (README, decisions.md, product-spec.md, CLAUDE.md/AGENTS.md) are updated or reworded to not pin a version that rots.

[dichovsky]

Assessment: re-verified against main @ 97d7f88. Confirmed as-is, with one line-number delta.

Published state, checked directly rather than from the issue body:

• npm view @dichovsky/crew dist-tags → latest: 0.1.1; versions is ["0.1.0","0.1.1"], 0.1.1 published 2026-07-13T15:51:28Z.
• git tag -l 'v*' → v0.1.1 (the only tag). package.json version is 0.1.1. CHANGELOG.md:29-33 records [0.1.1] — 2026-07-13 as the first release through the OIDC pipeline.

Stale passages, all reproducing:

• docs/README.md:62-64 — "0.1.0 is published to npm as the first release." This is the section that declares itself "the single source of truth for release status" (:48-49).
• README.md:49 — "0.1.0 is published to npm. Install it globally:". Delta: the body cites README.md:47; the line is :49 (:45-47 is the Node-floor paragraph).
• CLAUDE.md:29 and AGENTS.md:29 — both open "0.1.0 is published to npm."
• docs/design/decisions.md:27-30 (DEC-7) — "0.1.0 is published: the first publish was a one-time manual npm publish …".
• docs/design/product-spec.md:108 — "The first publish (0.1.0) has shipped to npm", inside what :107 calls the canonical release-gate list.

Every one of these carries the 0.1.0-manual / 0.1.1-OIDC narrative correctly; what is wrong is that each also asserts 0.1.0 as the current published state. That is the rot the Acceptance targets.

Not touched by this, and correct as written — noting them so a reviewer does not expect them in the diff: docs/release/publishing.md, docs/release/live-smoke-checklist.md:76-77, and docs/design/testing-strategy.md:254-256 all name 0.1.0 and 0.1.1 in a purely historical frame ("0.1.0 was a one-time manual publish, 0.1.1+ publish from CI") and none claims a current version, so none rots.

Verdict: IMPLEMENT

• Blast radius — six Markdown files: docs/README.md, README.md, CLAUDE.md, AGENTS.md, docs/design/decisions.md, docs/design/product-spec.md. Nothing under src/, bin/, tests/, web/, or docs-site/. No module boundary in CLAUDE.md is engaged. The one automated guard that reads project facts, collectCommands in tests/unit/docs-facts.test.ts:82-92, takes the version from package.json, not from prose — docs-site/generated/facts.json:4 already reads 0.1.1, so no regeneration is possible or needed.

• Reversibility — high. Markdown only; nothing enters dist/, the npm artifact, or the State Store, so nothing becomes harder to undo after a release. package.json's version is not touched, so this cannot influence what a future npm publish does.

• Contract impact — none. product-spec.md and decisions.md sit outside the authority order in docs/README.md:9-12 (they are build-packet and index documents); the other four files are not contract documents at all. No ADR is amended, no FR-*/NFR-* is added, renumbered, or given new meaning, no CLI grammar rule, record type, error code, command, or flag moves, and CURRENT_SCHEMA_VERSION stays 7. The release-gate table at product-spec.md:124-131 is not edited — only the prose above it that states which version shipped.

Scope: docs/README.md is the one file that may name a concrete current version, because it is the declared source of truth for release status and is expected to move each release. The other five are reworded to state the durable 0.1.0-bootstrap / 0.1.1-onward-OIDC fact without pinning a "currently published" version. Explicitly out of scope: the release-gate table itself, per-version feature scope (CHANGELOG.md still has an [Unreleased] section, so the eight-Participant roster described in docs/README.md's readiness paragraph is ahead of 0.1.1 — a separate question this change does not answer), and the three historical passages listed above.

Implementation follows in a draft PR.

---

Generated by Claude Code