[aicayzer]

Summary

Explain instance display names and the separate owner and delegated profile updates in Marfa v0.0.13. Add matching Marfa and Swift SDK changelog entries, including the folder handover repair and Swift's preservation of explicit null in optional nullable fields.

Changes

• Update Access, Permissions, Authenticate, Settings, CLI and key guidance against the merged Marfa release cut.
• Explain that owner email changes require recent browser authentication or private machine authority; delegated profile writes can change only name and avatar.
• Correct the Settings example's PORT lower bound and Deploy's explanation of database refusal exit status 78.
• Preserve the v0.0.12 counts, export and passkey documentation without describing those features as changes in v0.0.13.

Testing

• Reviewed all nine unique pages named by the staleness report between the v0.0.12 sync and merged v0.0.13 sync. Five needed updates; four remain accurate. Also updated the CLI, Permissions and Changelog pages for the release.
• Passed 33 live checks against Marfa commit c00e0cf2fc267e90b9a758bc7c46acd38ab2578c on Node 22: exact CLI and HTTP examples, Unicode names, configuration replacement, owner updates, existing access, profile permissions, invalid mixed updates and startup diagnostics. The isolated server was stopped and removed.
• Both site builds and both-target type checking passed. Rebuilt the docs after correcting the content checks below.
• Full Vitest suite: 350 tests passed and two content checks found an invalid contract anchor and a glossary term. Corrected both; all 95 tests in the affected files passed on rerun.
• Inspected rendered HTML for all eight changed pages and both generated profile operation links. git diff --check passed.
• No new tests were needed because this change updates prose; the existing checks and real-instance examples cover the changed content.

Notes for reviewers

This follows the generated v0.0.13 sync in #506. Review public behavior claims against Marfa's immutable release cut above and Swift SDK pin 03e6d9c, including nullable generator correction 068cda5.

The Swift v0.0.21 changelog entry is prepared for publication. Do not merge until that release and its consumer checks are verified, and confirm its release date. The release session owns that verification and the final merge.

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: clean (5/5)

Summary. The instance-name, owner-update and delegated-profile guidance matches the release source; merging remains conditional on verifying the advertised Swift SDK v0.0.21 release and consumer checks.

Checked.

• Untrue against marfa: Read all eight changed pages against Marfa c00e0cf2fc267e90b9a758bc7c46acd38ab2578c, including instance/config-name-*, instance/root-name, instance/upgrade-* and instance-claim owner/profile rules, the route schemas and handlers, permission checks, CLI dispatch and folder handover implementation. Checked Swift 03e6d9c9c959554b4bf2d4036b9bd87d4e4f9c8c, its exact core pin, generated profile operations and nullable-field types and tests.
• Untrue against marfa: Reviewed the nine-page staleness assessment and the recorded 33 live checks, including their executable assertions. Read the build/type-check and focused content-test evidence; the pull request's Build and type-check check is green. Did not repeat the full local suite.
• Generated file edited / Generated text copied: The diff changes eight handwritten pages only; generated references remain included from their existing sources.
• Lost in the Markdown copy / Page not wired: The additions use existing Markdown, tables and code tabs; existing page paths and sidebar wiring remain intact.
• Publishing weakened / Worker route frozen / Private detail committed / Stale instructions: No publishing, route, instruction or generated-file changes, and no private details in the patch.

Found.

• Swift release announcement. Native codex review --base 1022ec772d01bc76268ab03371c4217f46c54253 reported that the prepared v0.0.21 entry must not publish before its release exists. The pull request already makes release publication, consumer verification and the release date explicit merge prerequisites. Keep that gate in force. No prose change is required if those checks pass before merging. Untrue against marfa

---

Reviewed by withmarfa-reviewer in Codex, with native review on GPT-6 Astra. This review may contain mistakes.