W108 — Publish 0.11 Readiness

[The-Running-Dev]

W108 — Publish 0.11 Readiness

The release owner gets a public roadmap and exact checklist authorizing 0.11.0
as the next publication, while the actual publish remains a separate explicit action.

Done when

• W108.1 The canonical roadmap, README, generated public docs and landing page all identify
  0.11.0 as the next authorized publication and describe the same additive scope and
  compatibility claim.
• W108.2 The release checklist names the exact candidate commit/archive digest, required tag
  and package versions, changelog/release-note source, registry access, dry-run commands,
  post-publish verification, and rollback/deprecation procedure.
• W108.3 Every W93–W107 unit is complete with immutable evidence, or the checklist names the
  remaining blocker and does not claim readiness; no unchecked criterion is hidden by a
  summary status.
• W108.4 Package metadata, archive contents and public documentation agree on version,
  visibility, supported entry points, three shipped kinds, external content ownership,
  and the retired play surface.
• W108.5 The release workflow's tag/version and clean-build guards are exercised in a
  non-publishing validation path against the candidate and reject a mismatched tag or
  dirty/repacked artifact.
• W108.6 No npm publish, Git tag, GitHub release, deployment, DNS change, or external package
  release occurs in this unit; the final checklist states that publication requires a
  separate explicit user action.

---

Agent instructions

Run /slice W108.

• Scope and criteria: design/30-slices.md § W108 @ c2e427d
• Signatures: the repository's version/tag/release contract, W107's candidate report,
  and the public roadmap/release material reconciled by W105.
• Out of scope here: performing the publication, choosing credentials, deploying the site,
  announcing the release, or adding any feature/fix after the verified candidate.

Stop conditions and procedure: .claude/commands/slice.md. Not restated here.