docs(integrations): cross-link to protoCLI repo for quickstart

[mabry1985]

Why

Today's session added protoCLI as the namesake first-class provider in protoLabs Studio (PRs #3625–#3632). Documentation lagged — the integrations docs still positioned Claude as the default and didn't reference protoCLI at all.

Per direction: don't duplicate the quickstart in protomaker's docs — link to the protoCLI repo where it actually lives. This keeps a single source of truth and avoids the maintenance drift problem.

Changes

docs/integrations/proto-cli.md — new short page. Says protoCLI is the default runtime, names the SDK + gateway + auth env vars, points at where the autodetect status lives in the app (Settings + Setup wizard), and routes the reader to the upstream repo for everything substantive (install, commands, skills, SDK API).

Intentionally short — anything that would duplicate github.com/protoLabsAI/protoCLI's README belongs there, not here.

docs/integrations/ai-providers.md — adds a "Default: protoCLI" section at the top, repositions the existing Claude / OpenAI / LiteLLM provider tables as "Alternative provider systems". Page intro is rewritten to reflect protoCLI as the default rather than positioning all three legacy systems equally.

Validation

• npm run docs:build — clean, 7.75s, no broken links
• prettier --check — passes on both touched files

Out of scope

• The protoCLI quickstart in the protoCLI repo itself (separate repo, not touched here)
• Retiring the Claude / Cursor / Codex / OpenCode integration pages — they still describe valid alternative provider paths. They get a refresh when each surface gets retired in the app.

[coderabbitai]

Warning

Review limit reached

@mabry1985, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 2 reviews/hour. Refill in 17 minutes and 23 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 695c62ad-1341-4ab8-9ada-97335651056a

📥 Commits

Reviewing files that changed from the base of the PR and between 0e3bf1f and c5d878a.

📒 Files selected for processing (2)

• docs/integrations/ai-providers.md
• docs/integrations/proto-cli.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/protocli-crosslink

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Code Review — ? finding(s)

Async review running parallel to CodeRabbit. Findings are advisory; not all are merge blockers.

protoLabs Code Review Report

• Generated: 2026-05-22T23:17:27Z
• Git head: 9b897170a257dfcabbd506bf7df8e02dae3ecaf8
• Features mapped: 3
• Findings: 0

No findings recorded.

[github-actions]

Docs preview: https://docs-protocli-crosslink.protolabs-docs.pages.dev

[protoquinn]

Auto-approved by Quinn: safe PR class (dependabot/renovate/promote/chore(deps)) with passing CI.