VAP15-77 docs: add config as code (GitOps) page

[scott-lowe-vapi]

Description

Adds the public docs side of Vapi GitOps (VAP15-77). As agreed on the ticket, the page explains why to manage configuration as code and how to get started, then links out to the repository for the details, so the docs don't drift as the repository changes.

• New page: Config as code (GitOps) (fern/config-as-code.mdx), in Get started right after CLI quickstart. It covers:

  • why manage Vapi as code (dashboard vs config as code);
  • what the repository gives you: safe sync, references by name, multiple orgs, PR checks, agent instructions;
  • a four-step setup, with tabs for interactive and for non-interactive setup for coding agents and CI (key from the environment or a human-created env file, never a flag);
  • a copyable Set up Vapi GitOps prompt for Claude Code or Cursor;
  • development / staging / production with npm run promote, and test gating;
  • PR checks: the offline Validate resources check on every PR, and simulation checks (with a note that they use simulation minutes);
  • working alongside the dashboard and built-in versioning.

• Replaces "Enterprise environments (DEV/UAT/PROD)". That page described a hypothetical deployer: api.vendor.com, a kind: Assistant YAML schema, and PUT by name, none of which match Vapi. Its useful guidance (one org per environment, production writes from CI only, secrets out of git, how this relates to versioning) is now in the new page's environments section. /documentation/best-practices/enterprise-environments-dev-uat-prod redirects to /config-as-code#development-staging-and-production.

• "Already running Vapi in production?" For teams with existing orgs:

  • setup imports what is already live;
  • review the import with npm run audit;
  • preview the first deploy with npm run push -- <org> --dry-run, which should create and delete nothing (updates are expected, because a deploy re-sends every managed resource);
  • keep unmanaged resources out with .vapi-ignore.

  Teams already running several orgs are pointed to the promotion guide's one-time setup and its read-only plan. I verified the import claims against a test org (69 files): the dry run showed 0 creates, 66 updates and 0 deletes, and audit flagged two pairs of same-named simulations.

• Home page: Developer tools in the introduction now shows a GitOps card next to the CLI card.

• llms.txt, without replacing it. Fern can serve a hand-written llms.txt (agents.llms-txt in docs.yml), but that file would replace the auto-generated 450-line index and stop updating with the docs. Instead, this PR:

  • writes the new page's frontmatter description for agents. Fern turns it into the page's llms.txt line, which lands near the top of the index, right after the CLI, because the page is in Get started;
  • adds <llms-only> blocks, which appear only in the Markdown that agents read: setup steps and safety rules on the new page, and a pointer to GitOps on the introduction page, which is the first entry agents read.

  The trade-off: there's no separate ## Config as code section in llms.txt, as proposed on the ticket, because a custom section would mean hand-maintaining the whole file.

Merge after the GitOps stack lands (VapiAI/gitops#65 through #78). The guide links arrive in #70, the promotion test gate is #66, the .vapi-ignore cleanup protection is #73, and the Validate resources check is #76 and #77. The links 404 until #70 merges.

Testing Steps

• fern check (fern-api 5.112.0): 0 errors. All 14 warnings existed before this PR (API discriminators, accent contrast, and the redirect check, which needs fern login).
• Open the preview deployment and check:
  • /config-as-code: the steps, the tabs, the Set up Vapi GitOps prompt card with its copy and open-in buttons, and the cards under Learn more;
  • /quickstart/introduction#developer-tools: the CLI and GitOps cards side by side;
  • the old URL /documentation/best-practices/enterprise-environments-dev-uat-prod redirects to the environments section;
  • /config-as-code.md includes the <llms-only> agent steps, and the rendered page doesn't;
  • after deploy, /llms.txt lists Config as code (GitOps) with the new description.
• Not done: a local render. fern docs dev was still building the full API reference after several minutes, so I'm relying on the preview deployment.

🤖 Generated with Claude Code

[github-actions]

🌿 Preview your docs: https://vapi-preview-01a10f25-e2ac-75ed-b168-8fbccc24ecc3.docs.buildwithfern.com

[github-actions]

🌿 Preview your docs: https://vapi-preview-01a10f29-13a6-718e-80fe-4ad7afeddd0f.docs.buildwithfern.com

[github-actions]

🌿 Preview your docs: https://vapi-preview-01a10f2e-9c9a-7079-a13e-7002ea74dce4.docs.buildwithfern.com

[github-actions]

🌿 Preview your docs: https://vapi-preview-01a10f33-5f38-7452-9ed5-6af88bacfaad.docs.buildwithfern.com

[lightsage-app]

Lightsage docs evals

Lightsage could not queue docs evals for this PR.

Docs URL: https://vapi-preview-01a10f3d-a822-736e-9940-4fc6439a038e.docs.buildwithfern.com
Commit: 116b2bd
Reason: No custom evals are selected for GitHub PR evals. Open Lightsage > Custom Evals and enable the GitHub checkbox for at least one custom eval.

[github-actions]

🌿 Preview your docs: https://vapi-preview-01a10f3d-a822-736e-9940-4fc6439a038e.docs.buildwithfern.com