Vendor the API client into the CLI, drop the planetscale-go dependency

[no-itsbackpack]

Problem:

Every API change in the CLI required touching two repos. You had to add the new endpoint to planetscale-go, get that PR merged, tag a release, bump the version in the CLI's go.mod, and only then start the actual CLI work. The CLI is the only thing here that consumes planetscale-go, so this release dance added overhead to every feature without buying us anything.

Solution:

Copy the API client from planetscale-go (v0.175.0, the exact version we were pinned to) into this repo at internal/planetscale/ and remove the module dependency. Adding or changing an endpoint is now a normal change in this repo, done in the same PR as the feature that needs it.

Details:

• The client code is byte-for-byte the v0.175.0 release, including its tests. Only the import path changed, plus the User-Agent handling below.
• All ~290 files that imported github.com/planetscale/planetscale-go/planetscale now import github.com/planetscale/cli/internal/planetscale. The package name is unchanged so no call sites moved.
• The User-Agent header is now just pscale-cli/<version>. The old second token (planetscale-go/<version>) no longer means anything since the client version is the CLI version.
• doc/api-client.md explains the new workflow for contributors and coding agents, and AGENTS.md links to it so nobody reintroduces the two-repo process out of habit.

The planetscale-go repo itself is not touched by this PR. It still exists for external users of the Go SDK; its future is a separate conversation.

---

Security impact:

None expected. No new dependencies, no auth changes, no behavior changes to requests other than the User-Agent string.

---

Testing:

• go build ./... and the full go test ./... suite pass, including the vendored client's own tests.
• Built the binary and confirmed it runs.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit fe792c9. Configure here.}

[cursor]

Mirror skips PR after push

Low Severity

When the mirror branch already exists on planetscale-go, the commit step exits successfully and later steps skip opening a pull request. A rerun after a failed gh pr create (or push without PR) leaves the mirror updated on the remote branch with no PR and no recovery path in the workflow.

 

^{Reviewed by Cursor Bugbot for commit fe792c9. Configure here.}