From 0efaca4897ff4ab03ee443f5c3d483e525e369a6 Mon Sep 17 00:00:00 2001 From: Mario Tarosso Date: Fri, 20 Nov 2026 08:31:07 +0000 Subject: [PATCH] Stop telling hosted builders to add an API key before publishing Co-Authored-By: Claude Fable 5.2 --- AGENT-INSTALL.md | 10 +++--- README.md | 7 ++-- claude-plugin/skills/next/SKILL.md | 3 +- src/cli.ts | 16 +++++---- src/go-live.ts | 52 ++++++++++++++++++++++-------- src/progress.ts | 5 ++- tests/go-live.test.ts | 29 +++++++++++++++-- tests/progress.test.ts | 2 +- 8 files changed, 87 insertions(+), 37 deletions(-) diff --git a/AGENT-INSTALL.md b/AGENT-INSTALL.md index ffb0f4cf..33feab93 100644 --- a/AGENT-INSTALL.md +++ b/AGENT-INSTALL.md @@ -89,7 +89,7 @@ Every command at a glance — what it does, whether it reads your source, what i | `next` | Say where the project stands and the one thing to do now: connect the account (with the link), or go live (with the same steps `go-live` prints, or asking where the app is hosted when the project does not say). Answers the "done" the summary ends on. | Reads the project files `guide` and `go-live` read | The connected note in `.patchstackrc.json`, when it changed | The site UUID, to the public claim page that says whether it is connected (skipped once `.patchstackrc.json` records that it is) | | `doctor [--url ]` | Check that everything Patchstack needs works, and print each problem with its fix: the install, the site, the account, the guard's wiring, its rules file, the read-only rules credential, the map link, the build steps, and whether the published app fetches its rules. A problem only the app's owner can fix (connecting the account, publishing) is marked as theirs. Exits 1 when it finds a problem. | Reads the project files `guide` and `protect --check` read | Nothing | The site UUID, to the public claim page that says whether it is connected (skipped once `.patchstackrc.json` records that it is); the read-only rules credential from the guard's rules file, and the site key when this machine holds one, each once to `monitor/pulse/token`, to check Patchstack accepts them; one GET with that token to `monitor/pulse/sync-status/`, which answers only when the published app (read-only credential) and a key-holding copy last fetched rules, and how many (doctor never fetches rules itself, which would be recorded as a fetch); with `--url`, two GET requests to that address: its page, and the same page with a test attack in a `file` parameter, which another firewall in front of the app may also flag | | `vulns` | Show what Patchstack found in this project's packages: vulnerabilities by severity and outdated packages, as counts, with the link that shows the details. Package names are shown in the dashboard once the site is connected. | No | Nothing | The site UUID, to the public claim page that returns the counts | -| `go-live [--host ]` | Show how to add the project's API key to its host and deploy, in three steps. The host is read from project files (`vercel.json`, `netlify.toml`, `wrangler.toml`, `fly.toml`, `render.yaml`, `railway.json`, `amplify.yml`, `Procfile`, `.replit`, a Lovable project's packages) or named with `--host`. The commands it prints read the key from `.patchstackrc.local.json` as they run; it never prints the key. | Reads those project files only | Nothing | Nothing | +| `go-live [--host ]` | Show how to deploy on the project's host. In a hosted builder (Lovable, Replit, Bolt) that is one step, the builder's own publish button, and no key is involved. On a host the person manages it is three steps: add the project's API key, commit, deploy. Adding the key is optional there: the live app gets protection rules without it, and with it what the app reports is verified. The host is read from project files (`vercel.json`, `netlify.toml`, `wrangler.toml`, `fly.toml`, `render.yaml`, `railway.json`, `amplify.yml`, `Procfile`, `.replit`, `.bolt`, a Lovable project's packages) or named with `--host`. The commands it prints read the key from `.patchstackrc.local.json` as they run; it never prints the key. | Reads those project files only | Nothing | Nothing | | `widget [--remove]` | Add the Patchstack Connector widget tag to the root page (in a workspace repo, the app package's root page), or take the tag Connect added out with `--remove` (a tag added by hand is left alone). Saves the choice as `"widget"` in `.patchstackrc.json`, which `scan` and `mark-build` follow; `setup --widget` saves the same choice. | Reads the root page to find where the tag goes | `.patchstackrc.json`; the widget `