Document the ElevenLabs, New Relic, Retool and Twingate sources

[aureliensibiril]

Docs for the four access-review connectors in getprobo/probo#1884.

Merge these together. The connectors set DocumentationURL, so the four
links in the Add Source dialog 404 until this deploys.

Pages

elevenlabs, new-relic, retool, twingate, plus a <LinkCard> each in
directory.mdx.

Every Collected Fields table is derived from the driver rather than the
vendor's docs, so a row marked Not supported is one the driver genuinely leaves
empty, and a row naming a provider field is one it actually reads.

Facts a reader hits, recorded because we hit them

• ElevenLabs refuses a bad key with 400 where most APIs answer 401.
• New Relic runs three regional endpoints (us, eu, jp) and refuses a
  key presented to the wrong one, so the page tells the reader that a connection
  refused after the key is accepted is usually the region. Listing users needs a
  Core or Full platform account and the Authentication Domain Manager role,
  not just the role.
• Twingate fails the connection outright on a network name that does not
  exist, rather than returning an empty campaign.
• Retool is Enterprise-gated. users:read is absent from the token dialog
  on Team and on Business, and a Business token holding every scope it can grant
  is still refused. Retool's pricing page reserves "full access to all API
  scopes" for Enterprise. The page says so and points a customer without it at a
  CSV source.

Review

Written from the connector code, then run through a humanizer pass, a
structure and credential audit, an accuracy judge that re-derived every table
row from the drivers, and an adversarial Codex pass. The last two caught the
New Relic account-type requirement, the jp region, Twingate's seven roles,
and that ElevenLabs keys are editable and can carry an expiry that would
silently kill a connector.

npm run build passes; no em or en dashes; no credentials or account
identifiers in the text.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JFFcusrDZo9AR42g5Te2wS

[aureliensibiril]

check was red for a reason unrelated to this PR

docs:check-reference regenerates environment-reference.mdx from a fresh checkout of getprobo/probo and fails if the committed file differs. The committed file was 736 lines behind probo main, and none of that drift comes from this branch (it touches nothing under docs/deployment/). The same failure already hit v2 directly when the Crisp guide landed, and since deploy.yaml runs the identical check, the site deploy was blocked too.

Added 0dd38ac to regenerate it. Split of the diff:

Source	Lines
Pre-existing drift vs probo main	736
Added by getprobo/probo#1884 (4 connectors x 5 PROBOD_CONNECTOR_*_ENDPOINT_*)	20

I generated against the probo#1884 branch, not plain main, so the file matches the state that exists after both PRs land. The consequence is that check here stays red until #1884 is on main — by construction.

Merge order matters: getprobo/probo#1884 first, then this one. The reverse order leaves the v2 deploy failing on the twenty connector rows, and the DocumentationURL links added here 404 until the console change ships.

npm run build passes locally (455 pages).

[aureliensibiril]

Traced the root cause. Regenerating the page at the parent of probo commit b995080d3 ("Connect Crisp by app install, not a pasted code") reproduces the file currently committed on v2 byte for byte, so that one commit is the entire cause.

It added no variable. It shifted pkg/bootstrap/builder.go by two lines, and every row here carries a builder.go#Lnnn "View usage" deep link, so ~368 rows went stale at once. That is also why the Crisp env vars (PROBOD_CONNECTOR_CRISP_PLUGIN_ID / _PLUGIN_TOKEN) look correct on v2 today: they are.

Worth noting the blast radius is already on trunk. The v2 deploy failed at this same check before the astro build, so the Crisp guide rewrite never reached the live site; production is still serving the "Optimize assets" build from 15:33.

Structural, not a one-off: any edit to builder.go invalidates these links and breaks the docs deploy, with nothing in the probo repo to warn you.