---
name: m6-shipped-v010
description: "M6 done — v0.1.0 public release shipped 2026-06-05; spt-releases public, Pages live, release procedure in RELEASE-RUNBOOK.md; don't re-plan M6"
metadata: 
  node_type: memory
  type: project
  originSessionId: 42dd3aac-a463-4e08-ba67-3a5a9ffb614b
---

M6 (stage-setting) DELIVERED and v0.1.0 SHIPPED 2026-06-05, same day as the grill.
`SaberMage/spt-releases` is PUBLIC: signed release live, Pages at
https://sabermage.github.io/spt-releases (permanent canonical URL).

**Why:** future sessions must not re-plan or re-execute M6; releases follow the
established procedure.

**How to apply:**
- Release procedure = `docs/RELEASE-RUNBOOK.md` (CI builds draft on tag; user runs
  `xtask release-publish` locally with the primary seed; keys never in CI).
- Embedded trust anchor: rel-primary-2026 + rel-recovery-2026 in BUILTIN_RELEASE_KEYS;
  seeds custodied by user off-machine (password manager). Recovery key real-verified once.
- spt-releases repo-face (README/licenses) truth lives in spt-core `releases-repo/`,
  auto-synced by docs-publish — never edit on spt-releases directly.
- Docs truth = `docs-site/`; generated pieces via `cargo run -p xtask -- gen` (drift-gated).
- Next horizon: [[spt-claude-code-scoping]] (separate downstream repo, v1 acceptance proof).