Clarify authenticator requirement outcome

[masnwilliams]

summary

• describe totp_required without inferring whether the attached credential contains a TOTP secret
• align the public recovery table with the deployed, provider-agnostic managed-auth outcome

validation

• bunx mintlify broken-links

---

Note

Low Risk
Documentation-only wording change with no runtime or API impact.

Overview
Updates the totp_required row in the connection lifecycle failure-code table so it describes the observed outcome (reauth needed an authenticator code Kernel could not supply automatically) instead of implying the linked credential is missing a TOTP secret.

This keeps public docs aligned with provider-agnostic managed-auth behavior and avoids misleading readers when TOTP is present but still not usable in unattended reauth.

^{Reviewed by Cursor Bugbot for commit 626d354. 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 31, 2026, 1:35 AM

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

[cursor]

Risk assessment: Very Low

Verdict: Approve.

This PR changes one sentence in auth/connection-lifecycle.mdx. The totp_required row in the connection-lifecycle failure-code table is reworded from implying a missing TOTP secret to describing the observed outcome (an authenticator code Kernel could not supply automatically).

Why Very Low

• Documentation-only: one file, one line, no code, config, or infrastructure changes
• No production logic, API surface, auth implementation, or shared systems modified
• Blast radius is limited to public docs copy for an existing failure code
• No CODEOWNERS file in this repo, so code-owner review is not required
• No prior approval to re-evaluate

Safe to approve.

  

_{Sent by Cursor Automation: Assign PR reviewers}