Document credential field labels

[masnwilliams]

summary

• document optional credential field label values and stable name semantics
• explain label validation, non-secret metadata behavior, exact field ordering, and unlabeled fallback
• update TypeScript, Python, and CLI examples to the ordered field array contract
• keep update examples keyed by stable field name

rollout

Publish after kernel/kernel#4214 and the corresponding SDK release are live.

validation

• rendered /vaults/credentials with a local Mintlify preview
• git diff --check

---

Note

Low Risk
Documentation-only changes with no runtime or security behavior in this repo.

Overview
Updates vault credential docs and snippets to match the ordered fields array contract (each entry has name, optional label, plus type/required/sensitive) instead of a keyed object map.

Adds guidance that name stays the stable key for state.fields, updates, and fill, while label is optional display metadata with validation and name fallback. Collection forms and custom UIs should preserve declaration order and show labels when set.

TypeScript, Python, and CLI creation examples are refreshed; value update samples still send changes keyed by field name.

^{Reviewed by Cursor Bugbot for commit 8329f3e. 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
Kernel	🟢 Ready	View Preview	Sep 18, 2026, 6:01 PM

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

[cursor]

Risk Assessment: Very Low

Decision: Approve

This PR only updates Mintlify documentation (vaults/credentials.mdx and snippets/collect-browser-credentials.mdx). The diff rewrites credential fields examples from a keyed object to an ordered array with name / optional label, and adds matching API-docs prose. There is no application code, config, CI, infrastructure, auth, or runtime logic in the change set.

Evidence

• 2 files, +104 / −32, both .mdx
• No CODEOWNERS file in the repo
• No production codepaths, shared libraries, or schema/infra changes

Risk factors

• Codepaths: docs pages and snippet examples only
• Blast radius: documentation site copy
• Complexity: mechanical example updates plus field-table/prose edits
• Infra / operational / security impact in this repo: none

No existing reviews on this PR. Approving as Very Low risk.

  

_{Sent by Cursor Automation: Assign PR reviewers}