[aicayzer]

Summary

Bring the guides into line with Marfa v0.0.21 and publish its release notes. Owners can find the shipped console operations without mistaking summary access for content access or an archive restore for a guaranteed upgrade path.

Changes

• Describe owner summaries and trash, app-access reductions, webhook inspection and retries, recorded actors, live settings, profile pictures, folder reports, and Needs attention.
• Correct folder push recovery and foreign frontmatter handling, private-socket boundaries, and unused custom-type deletion.
• Preserve existing page rewrites and release history. The v0.0.21 entry covers its immutable tag and excludes later bulk-page work and unreleased Swift SDK APIs.
• Retain the database-schema refusal, unchanged old database, and requirement to test archive restoration on fresh storage before switching builds.

Testing

• Frozen pnpm install, docs build with prerender, status build, and both TypeScript checks passed.
• Content lint: 47 tests passed. git diff --check passed.
• Read every page named by the release staleness report against the contract and API description, changing only stale claims.
• Existing changed command examples were exercised against an isolated instance, including configuration, audit, owner trash, connector reporting, and export/restore. A separate old-build trial verified schema refusal without modifying the old database and successful fresh restoration of the tested archive contents. This is not a cross-build compatibility guarantee.
• Personally inspected all 17 changed pages in the built-in browser, including phone-width dark release/upgrade warnings, the expanded database-refusal help, and interactive folder steps. The built docs worker passed the folder-page check without browser errors.
• No full local test suite or manual deployment was run for this prose change. CI builds and publishes the site.

Notes for reviewers

Check the owner-versus-credential boundaries, archive warning, and release scope. Generated reference files are unchanged. The core Swift binding change is described only as a core binding change, not as a released Swift SDK API.

Checklist

• The title is a scoped Conventional Commit.
• New behavior has a test that was seen failing first, or no test was needed and the reason is above.
• Docs, comments and the contract still say what is true after this change.

[aicayzer]

Review: ready to merge

Summary. The release entry and guides describe the shipped console and preserve the owner-content boundary and archive-restoration limitations.

First draft: 4/5. One consequential prose ambiguity in connector source actions was corrected in d367f6e; no outstanding finding remains.

Checked.

• Untrue against marfa: changed claims checked against the v0.0.21 contract and source, including owner authority, narrowing, live settings, provenance, schema refusal and the immutable release range.
• Generated file edited: no generated reference files changed.
• Private detail committed: no private hostnames, paths or credentials in the diff.
• Page not wired: existing pages and links retained; all 17 changed pages inspected in the browser, with representative phone-width and dark views.

Found.

• Connector source actions. Clearing an older registration also clears its successor's source state, while removing an older registration preserves successor endpoints and deliveries. The guide now states both effects, matching the contract. Fixed in d367f6e. Untrue against marfa

Quick fixes. One prose correction applied by the reviewer. Content lint passed all 47 tests.

---

Reviewed by withmarfa-reviewer on GPT-6-Sol. This review may contain mistakes.