Skip to content

docs: edit the guides for new readers and fix inaccuracies - #71

Open
scott-lowe-vapi wants to merge 1 commit into
docs/readme-restructurefrom
docs/guides-rewrite
Open

scott-lowe-vapi wants to merge 1 commit into
docs/readme-restructurefrom
docs/guides-rewrite

Conversation

@scott-lowe-vapi

@scott-lowe-vapi scott-lowe-vapi commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

Value

V.A.L.U.E. tier: small — docs only. It edits the guides that #70 moved, for readers who don't know the repo's history, and fixes inaccuracies. Not micro: more than 200 lines.

  • Problem:
    • Insider wording: the moved content read like a changelog ("used to spawn duplicates", "the CLI now refuses", "P0-1 regression suite").
    • Duplicates: some content still repeated itself.
    • Inaccuracies: a few statements were wrong, and two troubleshooting tips could make things worse.
  • What changes:
    • Workflows:
      • one section each for deploying (including scoped deploys), starting fresh, creating new resources, pulling, testing, recovering and cleaning up;
      • the AI-agent callout becomes a note for the user, since AGENTS.md already instructs agents.
    • Commands: one sentence per command, and the false claim that every command is interactive is fixed. migrate moves to "Upgrading from an older version".
    • Configuration: documents every setting users set: per-org .env values and generated bindings, precedence, the promotion and PR check secrets and variables, config files, and the CI and debug variables.
    • How it works: the stale project tree (a third of src/, 5 of 68 tests, internal labels) becomes a short "Where things live" table. The guide now says push deletes only with --force.
    • Troubleshooting:
      • it no longer advises deleting a state entry, which made the next deploy treat the file as new;
      • it no longer suggests quietly editing engine code. It points at audit's per-finding suggested fixes, and at opening an issue.

Evidence of value

Every changed claim was checked against the code:

  • apply forwards type and path arguments to pull and push, which share the parser that rejects bare IDs;
  • setup, apply, pull, push, cleanup and call are the only interactive commands;
  • environment variables beat .env files, and .env.<org>.local only fills gaps;
  • the EU base URL is https://api.eu.vapi.ai;
  • push prints "Deletions: Disabled (pass --force to enable)";
  • audit reports state-ghost and state-uuid-collision with a suggested action.

All links resolve and npm test passes, 496 tests.

Found while checking, not changed here: src/config.ts comments .env.<org>.local as "local overrides", but the loader reads it after .env.<org> and only fills unset variables, so it can't override anything. The guide documents the actual behaviour. Fixing the code or the comment is a separate change.

Testing plan

  • The link checker and npm test.
  • Not tested: the commands and workflows against a real org (this PR changes no commands).

Stacked on #70.

🤖 Generated with Claude Code

The previous change moved the README's long-form content into
docs/guides/ verbatim; this one edits it.

- workflows: merge the duplicated sections (pull without losing work
  appeared twice, pull by UUID three times, selective push separately
  from deploy), drop the old "How to Use This Repo" list now covered by
  the README, and turn the AI-agent callout into a note for the user
  (AGENTS.md already instructs agents).
- commands: one sentence per command; fix the claim that every command
  is interactive; move migrate to an "Upgrading from an older version"
  section.
- configuration: document every setting users actually set: per-org
  .env values and generated bindings, precedence, the promotion and PR
  check secrets and variables, config files, and CI/debug variables.
- how it works: replace the stale project tree (a third of src/, 5 of 68
  tests, internal labels) with a short "where things live" table; push
  deletes only with --force.
- troubleshooting: don't advise deleting state entries (that makes the
  next deploy treat the file as new) or silently editing engine code;
  point at audit's suggested fixes and an issue.
- Present-tense wording throughout (no "used to", "now refuses").

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant