[benperkins]

🔎 Previews:

• Fork PRs need a Clerk team member to authorize the Vercel deploy, so there's no preview link yet. The pages are /docs/reference/backend/enterprise-connections/create-enterprise-connection-test-run, /docs/reference/backend/enterprise-connections/get-enterprise-connection-test-run-list and the five /docs/reference/backend/types/backend-enterprise-connection-test-run* type pages.

What does this solve? What changed?

• Adds reference pages for the two @clerk/backend methods added in feat(backend): add enterprise connection test run methods javascript#10332, createEnterpriseConnectionTestRun() and getEnterpriseConnectionTestRunList(), and for the types they return: EnterpriseConnectionTestRun, EnterpriseConnectionTestRunLog, EnterpriseConnectionTestRunOauthPayload, EnterpriseConnectionTestRunParsedUserInfo and EnterpriseConnectionTestRunSamlPayload.
• Each page follows the existing enterprise connection pages: a <Typedoc /> include for the generated content, plus usage and the BAPI endpoint for the methods. The manifest entries sit next to their siblings.
• The <Typedoc /> sources don't exist in clerk-typedoc/ until feat(backend): add enterprise connection test run methods javascript#10332 is merged and released, so these pages depend on that PR. feat(backend): add enterprise connection test run methods javascript#10332 also registers the five type pages in its Typedoc link replacements, which is what links to them.

Deadline

• No rush. This should land after feat(backend): add enterprise connection test run methods javascript#10332 is released.

Other resources

• feat(backend): add enterprise connection test run methods javascript#10332

[github-actions]

Thanks for contributing! A quick heads-up on how external contributions work: Clerk's docs are maintained in Clerk's internal monorepo, and this public repo is its read-only mirror — nothing merges here directly, and there are no preview deployments on this repo. Nothing is needed from you. A Clerk maintainer will review this PR, and if it's accepted, they'll bring your change into the monorepo with your commits and authorship preserved — it then goes live on clerk.com/docs shortly after. See Contributing to Clerk's documentation for the full picture.

The failing Block merges check on this PR is expected — merging is disabled in this repo on purpose.