[scott-lowe-vapi]

Value

V.A.L.U.E. tier: micro. It restores intended behavior in about 50 changed lines across 4 files, and a deterministic test proves it.

• Problem: in the interactive npm run setup wizard, choosing simulations fails with "Single-resource pull requires exactly one resource type". Setup stops before simulations, suites and evals are downloaded, and the org folder is left half set up. It happens to anyone whose org has simulations and who picks "All".
• Who it affects: new users connecting an org through the wizard, including everyone who runs npx create-vapi-app, which hands off to it. Non-interactive setup (npm run setup -- <org>) does one full pull and was never affected.

How it works

The wizard pulls what you pick one type at a time: pull.ts <org> --force --type <type> --id …. It passed the internal type name. But simulations is also the --type group alias for personalities, scenarios, simulations and simulationSuites, and a pull by --id refuses more than one type.

• src/resource-type-args.ts (new, config-free): the group and path alias maps and resolveResourceTypes move here from config.ts unchanged, so tests can import them. config.ts parses argv and exits on import, so tests couldn't. A new typeArgFor(type) returns the --type spelling that resolves to exactly that type; for simulations that's simulations/tests.
• src/setup.ts: the wizard's per-type pull passes typeArgFor(typeKey).
• tests/resource-type-args.test.ts: checks that every resource type comes back as exactly itself through typeArgFor, so a future type that collides with a group alias fails CI. It also checks that --type simulations still selects all four types for apply.

Verification

Before: on main, run the exact command the wizard builds against an org with simulations:

tsx src/pull.ts <org> --force --skip-bindings --type simulations --id <sim-id>
❌ Pull failed: Single-resource pull requires exactly one resource type.

After: run it with typeArgFor("simulations"), which gives --type simulations/tests:

Found 2 matching simulations in Vapi (requested 2)
✨ … -> resources/<org>/simulations/tests/….yml
simulations: 2 new, 0 updated

The wizard's per-type pulls for simulationSuites and evals also completed, scoped to the requested ids. Your run had never reached them. These were read-only pulls against a real org, into a throwaway copy of the repo.

npm run build passes, and npm test passes 584/584.

Not in this PR

Each per-type pull in the wizard prints the --force warning ("run npm run pull (no flag) first…") and waits 2 seconds. For an org with all 9 types, that's 9 warnings and about 18 seconds of waiting, for advice aimed at hand-run --force pulls. It could be a follow-up to suppress the warning for the wizard's own pulls.

🤖 Generated with Claude Code

[scott-lowe-vapi]

• fix(setup): pull simulations by their single-type alias in the wizard #92 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[scott-lowe-vapi]

Merge activity

• Nov 6, 9:09 PM UTC: @scott-lowe-vapi merged this pull request with Graphite.