---
name: v0150-public-docs-update
description: "v0.15.0 release-phase deliverable (operator-directed 2026-06-24): update GitHub Pages docs-site — integration-checklist + api + messaging — with direction for every v0.15.0 feature. Publish via docs-publish.yml WITH the release."
metadata: 
  node_type: memory
  type: project
  originSessionId: 16842a97-6889-4f10-b3ac-07f857482143
---

**v0.15.0 PUBLIC DOCS-SITE UPDATE (GitHub Pages) — operator-directed 2026-06-24, MUST ride the release.** The per-wave `xtask gen` only regenerates `docs-site/src/cli/reference.md` (generated). The hand-authored PROSE pages need direction for the v0.15.0 features. doyle authors (design-owned surfaces); publish via `gh workflow run docs-publish.yml --ref main` ([[adapter-tips-published-docs]]); VERSION numbers, NO internal M#/W#/REQ codes ([[public-docs-version-not-milestone]], [[cli-command-docs-drift]]).

**GAPS (grounded vs the live docs-site):**
1. **`harness-contract/integration-checklist.md` (operator-flagged PRIORITY):** the checklist covers `api boundary` (identity/spool/history SURVIVE a reset) but has NO resume-context PULL — the new `spt api psyche-download` SessionStart step is MISSING entirely. ADD a Group-2 (Recommended) row: `api psyche-download <id>` → "the agent's durable two-tier mind (role/live/project) + any not-yet-synthesized commune/signoff injected on resume; the SessionStart hook pulls stdout as additionalContext" (RUN/BOUNDARY). UPDATE the claude-code worked example (SessionStart calls `api psyche-download`, not just `api seed`/`listen`). ADD an "Am I done?" floor item (resume-context pull wired). Note: commune/signoff DROP is already in Group 4 (the write side); psyche-download is the missing READ-back-in side.
2. **`harness-contract/api.md`:** ADD the `psyche-download` verb — signature `spt api psyche-download <id> [--session-id <sid>]`, auth-gated, stdout = role/live/project slices + `<pending-commune>`/`<pending-signoff>`, NO-CONTEXT:<id> on stderr when empty.
3. **`messaging/overview.md` + `quickstart/messaging.md`:** ADD the three send axes — window (`--idle-only`/`--active-only`), channel (`--prefer-native`/`--force-native`), persistence (`--ephemeral`) — + `--json-payload` (opaque adapter-parsed `json=""` metadata; the receiving adapter parses it). Sender-facing direction + the ephemeral-partial caveat (v0.15.0 = spt-hosted-binary + TTL legs; harness-relay-carrier leg deferred, mirror CONTEXT.md §persistence).
4. **`cli/reference.md`:** already auto-regenerated per-wave (xtask gen) — just VERIFY the new flags + verb render with no internal codes.

CONSOLE-WINDOW fix = internal, no public-docs needed.

**SEQUENCING:** AFTER the `!!checkpoint!!` strip follow-up lands (docs describe the final feature) + WITH the release publish. NOT a code wave — a docs deliverable. Tag [doc->REQ-DOCS-2] (harness checklist) / messaging doc REQ. Related: [[v0150-w5-resume-context-pull]], [[v0150-w1-activity-gated-delivery]].

**STATUS: ✅ DONE — docs committed @582e5d1** (messaging/overview axes+json, api.md psyche-download verb, integration-checklist Group-2 row + claude-code example + floor item; REQ title amended for both strip points; W6 plan note). traceable EXIT0 + xtask OK. quickstart/messaging.md left as-is (minimal basics tutorial, no send-modifier flags — axes belong in the overview). doyle signaled DOCS-READY → deployah cutting v0.15.0 (bump-in-PR, counter expect 34, doyle CHANGELOG-vets); docs-publish.yml rides WITH the release. perri validates real CC post-publish.