Document durable resource lifecycle contracts

[IlyaasK]

Summary

• document profile rename behavior and active-session risk
• document proxy rename identity and ambiguity behavior
• define extension checksum byte semantics and legacy nullability
• document API-key self-deletion rejection

Why

These durable lifecycle contracts are merged and released but were not described precisely enough for operators using the API and SDKs.

Verification

• Mint broken-links
• git diff --check
• claims checked against kernel/kernel merged origin/main
• SDK response fields checked against Node, Python, and Go SDK v0.86.1

---

Note

Low Risk
Docs-only changes with no runtime, auth, or data-path modifications.

Overview
Documentation-only update that spells out operator-facing lifecycle behavior for profiles, proxies, extensions, and API keys—aligned with already-shipped API/SDK behavior.

Adds Rename a profile (profiles.update) with project-unique names and a warning about renaming while a session still references the old name and save_changes may fail to persist. Adds Rename a proxy (proxies.update by ID) and notes that proxy names are not unique, so updates must use ID when names collide.

Extensions metadata now documents optional lowercase hex SHA-256 checksum over uploaded archive bytes (not unpacked/normalized content), and when checksum may be null (legacy / repackaged Web Store extensions). API keys get a warning that a key cannot delete itself—use a different credential for delete requests.

^{Reviewed by Cursor Bugbot for commit e5157a6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Aug 6, 2026, 10:06 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Error		Aug 7, 2026 3:19pm

[cursor]

Risk assessment: Very Low

Verdict: Keep existing approval (risk unchanged)

Re-evaluation after synchronize

This automation previously approved commit e5157a6. Head is now 52dee86 ("Remove incorrect profile rename warning"). Re-assessed from the current full diff vs main.

Evidence (from diff only)

• 4 files changed (+46 / −1), all Mintlify .mdx documentation pages:
  • auth/profiles.mdx — documents profile rename via profiles.update and project-unique names (delta since last approval: removes a <Warning> block only)
  • proxies/overview.mdx — documents proxy rename via ID and non-unique names
  • browsers/extensions.mdx — documents optional SHA-256 checksum semantics and nullability
  • info/api-keys.mdx — documents that an API key cannot delete itself
• No application code, config, CI, infrastructure, schema, or auth/permission implementation changes
• Diff is documentation prose plus SDK usage examples (TypeScript / Python / Go)
• No CODEOWNERS file found

Why Very Low

Still a small, documentation-only surface with no production logic, shared systems, or infra impact. The follow-up commit only deletes incorrect warning prose; blast radius did not increase.

Action taken

• Risk remains Very Low → approval retained
• Did not re-approve (already approved by this automation)
• Did not dismiss approval (risk did not increase)

  

_{Sent by Cursor Automation: Assign PR reviewers}