docs: reconcile published releases and acceptance gates

[BunsDev]

Outcome

Refs #195, #196, #239, #31, #197, #199.

Reconcile public delivery and acceptance documentation against live records as
of 2026-09-06. Owner-authorized; documentation and documentation contract tests
only. No release, repository-setting, product behavior, or support-status change.
Keep this PR in draft for independent review.

Confirmed drift and correction

Surface	Evidence	Correction
Release availability	The v0.0.2 release was published on 2026-08-31 with two macOS DMGs and checksums; run 33311851717 completed desktop publication and skipped iOS upload	Remove the incorrect unreleased-candidate claim without inferring operator acceptance or TestFlight availability
Source identity	Verified signed tag object 87e23c17b3fcff38d33e37a70f56679c475edd43 resolves to a4546f45bb0ee05cfbb388a0fc5f9e951596be51	Distinguish release source from the dispatch workflow SHA 63667f300bbdccea4dfede4e9e19fedb90876356
Homebrew	Pinned Cask source still selects v0.0.1	Do not mistake a successful tap notification for a Cask update or v0.0.2 upgrade acceptance
Main governance	#31 correction, PR #351 (23cace08), and a live read of ruleset 21729943 show no bypass actors, zero required approving reviews, and required thread resolution	Replace the obsolete named-owner bypass procedure; preserve administrator enforcement, exact-head checks, and independent R3/R4 review
Stabilization tracking	PR #350 quoted closing syntax while reporting no new acceptance evidence; #239 remains incomplete	With owner authorization, #196 was reopened with an evidence note; avoid closing-keyword phrasing when only describing gates
Delivery progress	PRs #354-#359 delivered the source harness; PRs #362, #366, #369-#373 delivered early desktop decomposition	Distinguish delivered source work from the still-missing packaged operator observations; remove the false inventory-only/no-open-PR snapshot

The six public/canonical documents now agree. Existing documentation tests
assert the corrected release, governance, and evidence boundaries rather than
enforcing the stale snapshot.

Exact-head evidence

• Base: 81a9c7547002407b00447839d6962ce884c4f67a
• Signed documentation head: ab68f26d30118ff8b72f563b0dccede3e915f6fc
• pnpm exec vitest run __tests__/postReleaseExecutionDocs.test.ts __tests__/releaseDocs.test.ts __tests__/communityHealthContract.test.ts __tests__/agentRepositoryContract.test.ts --reporter=dot — 53 passed.
• pnpm run typecheck:tests — passed.
• node scripts/check-public-docs-focus.mjs — 86/86 passed.
• git diff --check — passed.
• Focused documentation assertions first reproduced the stale claims before the corrections.

An independent read-only review of PR #372's original head
141a31e57a212afae9252e1554af9460eb229282 reported no findings. That review does
not cover this documentation PR or PR #373.

Explicit proof gaps and boundaries

• The existing private acceptance manifest was not available at a usable linked
  location. The 15-digest/incomplete state is the latest owning-issue report,
  not a new verification of those files.
• The owner explicitly deferred GUI acceptance until providing the manifest and
  a disposable GUI context. No live application was launched, terminated, or
  altered.
• No operator case, support transition, upgrade path, full-volume failure, or
  physical-device/TestFlight result is claimed.
• No generated Beads mirror or Beads source was changed.
• The documentation work used an isolated worktree; concurrent product work
  remained untouched. PRs refactor(desktop): give the initial-workspace finish its own function #372 and refactor(desktop): give the publication sequence its own function #373 were merged by another actor.
• This is a source/documentation gate, not full release or packaged acceptance.

Rollback

Revert the documentation commit if necessary. This does not change a release
artifact, repository setting, or product behavior. Keep #196 open unless its
owning acceptance evidence supports a different state.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
psyche-build-docs	Ready	Preview	Sep 9, 2026 9:39am UTC

[Copilot]

🟢 Approval recommended

The changes consistently update documentation and its contract tests to match verified release/governance records without expanding support or acceptance claims.

Pull request overview

Reconciles the repository’s public delivery/acceptance documentation and doc-contract tests to reflect the published v0.0.2 artifacts while preserving the distinction between publication, Homebrew install state, and operator acceptance gates (#196/#239).

Changes:

• Update public-facing docs to record v0.0.2 publication (tag source SHA, release run) without implying acceptance, Homebrew upgrade, or TestFlight availability.
• Correct/clarify post-release governance language to reflect the current bypass-free main ruleset (per #31 correction / PR #351).
• Adjust documentation contract tests to assert the updated release/governance boundaries across the canonical doc set.

File summaries

File	Description
README.md	Adds v0.0.2 publication note and explicitly separates it from Homebrew selection and acceptance evidence.
docs/README.md	Mirrors the v0.0.2 publication/acceptance separation in the docs landing page.
docs/SUPPORT-MATRIX.md	Clarifies applicability across accepted v0.0.1, published v0.0.2, and current source; adds a dedicated “publication vs acceptance” section.
docs/ROADMAP.md	Updates reconciliation date; replaces stale v0.0.2 “unreleased candidate” claim with publication facts; updates governance text and delivered-slice inventory.
docs/RELEASE-ACCEPTANCE.md	Records v0.0.2 publication as separate from acceptance; updates governance row and harness/acceptance distinctions; clarifies closure wording to avoid accidental closing syntax.
docs/POST-RELEASE-EXECUTION.md	Updates reconciliation date; aligns sequencing narrative with v0.0.2 publication and current governance policy; records reopened #196 context and delivered #197 slices.
tests/postReleaseExecutionDocs.test.ts	Updates doc-contract assertions to enforce the corrected publication/governance boundaries across the canonical documents.

Review details

• Files reviewed: 7/7 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.