ghosty-acp 0.0.70 → 0.0.72

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ghosty-acp",
3
- "version": "0.0.70",
3
+ "version": "0.0.72",
4
4
  "description": "Conecta tu editor a un agente ACP remoto. Puente entre entrada/salida estándar y WebSocket, sin dependencias.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -5,7 +5,7 @@ license: MIT
5
5
  compatibility: Needs Node 22+ (for npx @ghostystudio/cli) or curl, and network access to https://www.ghosty.studio
6
6
  metadata:
7
7
  author: ghosty-studio
8
- version: "1.101"
8
+ version: "1.103"
9
9
  ---
10
10
 
11
11
  # Configure a Ghosty Studio agent
@@ -175,6 +175,7 @@ legacy and always `true`.)
175
175
  | "are images being metered / how much do images cost on Free" | staff only: `ghosty usage --images --plan free --since 7d [--by user]` — charges vs images agents delivered (far more deliveries than charges = the meter isn't reporting) and stored cost vs the table |
176
176
  | "did the push reach them / did the announcement go out" | staff only: `ghosty push log --user <email> --since 2d` (announcements show as `novedad`); `ghosty novedades ls` shows delivered/rejected per announcement |
177
177
  | "my site is paused / will pause", "keep my page online", "pin my site", "reactivate my page" | `ghosty sites ls` (state: pinned, paused, pauses on…), then `ghosty sites pin <slug>` — «Sitios fijos»: $49 USD/yr or $5 USD/mo ($990 / $99 MXN), includes up to 3 sites; never pauses, no banner. With a free slot it pins at once; otherwise it prints a card-payment link to hand over as is; `needs_pack` = all slots used: ask, then `--add-pack`. `--interval month`, `--currency mxn`. `ghosty sites unpin <slug>` frees a slot; `ghosty sites pins [--cancel]` |
178
+ | "how is my app", "is it awake", "what variables / tasks / files does it have" | `ghosty sites show <slug> --json` (status `site.wake.phase`: ready/starting/asleep/failed, never wakes it; variable NAMES only). Change: `ghosty sites env set <slug> NAME=value` · `env rm <slug> NAME`; tasks `ghosty sites cron ls|pause|resume|rm <slug> [id]`; files `ghosty sites files ls|rm <slug> [id]`. Errors (server + browser, grouped): `ghosty sites errors <slug> [--since 6h] [--req-id ID]`. The person sees the same at `/c/sitios/<slug>` (tabs `?tab=datos` etc.) |
178
179
  | "put my domain on my app", "use reservas.midominio.com", "custom domain" | `ghosty sites domain add <slug> <domain>` prints the DNS record (CNAME to `<slug>.ghosty.page` for a subdomain, A to the printed IP for the root); hand it over in one line. After they add it: `ghosty sites domain verify <slug> <domain>` (DNS can take minutes to a couple of hours; Cloudflare proxy off). Verified = the app answers at `https://<domain>`, HTTPS issued on the first visit. Apps with a backend only. `ghosty sites domain ls <slug>`, `rm <slug> <domain>` |
179
180
  | "I have a coupon", "redeem HACK2026", "create a coupon for the event" (staff) | `ghosty coupons redeem <CODE>` (one per account; adds balance and may lend a plan until a date). Or the link `https://www.ghosty.studio/canjear?codigo=<CODE>`. Staff: `ghosty coupons create <CODE> --credit 50 [--plan pro --until ISO] [--max N]` is born a draft; `ghosty coupons set <CODE> --on` turns it on; `ghosty coupons ls`; a lent plan that starts later: `--from ISO --redeem-by ISO --convert-promo STRIPE_CODE`; who redeemed and converted: `ghosty coupons show <CODE> --json` |
180
181
  | "sign in with Google in my app", "login with Google" | No Google console: the app copies `https://www.ghosty.studio/apps/auth/ghosty-login.mjs` (no deps), sends the button to `loginUrl({ returnTo, state })` and on the callback calls `verifyLogin(id_token)` → `{ sub, email, name, picture }`. `returnTo` must be `<slug>.ghosty.page` or a verified custom domain. Docs: /docs/apps |
@@ -219,7 +220,7 @@ legacy and always `true`.)
219
220
  | "the run is escalated, what do I pick?", "a or b", "merge it as it is" | `ghosty factory runs choose <n> --workspace <slug>` lists the 2–3 paths @check left (a/b/c with their action); `ghosty factory runs choose <n> <letter> --yes` applies one and the choice reaches the next role word for word. `merge_as_is` merges with red CI that the PR did not cause (logged as `merge_override`): confirm with the user first. `fix_main` opens a separate run that fixes the main branch (it waits for the owner's signature); the escalated run then shows «Waiting for the main fix (#N)» and resumes on its own when that fix merges |
220
221
  | "how is the factory doing?", "cost per merged PR", "merge rate" | `ghosty factory runs stats --since 30d [--repo owner/repo] --workspace <slug> --json` |
221
222
  | "connect this repo to the factory", "create a factory room", "set up the factory for <repo>" | `ghosty factory rooms connect owner/repo --room <name> --create --workspace <slug> --json` (checks the GitHub App sees it; returns `readiness` = what's missing); `ghosty factory rooms ls --workspace <slug>`; `rooms disconnect … --yes` |
222
- | "hand this to the factory", "let the factory build it", "delegate this PR", "send it to @plan" | `ghosty factory run "<goal, why, how we know it's done>" --repo owner/repo --wait --workspace <slug> --json` → it returns at `plan_review` with `next` (the commands). Show the user the plan (`runs show <n> --full`) and ask before `runs approve <n> --plan-version N --yes`; then `runs watch <n>` until `pr_review` and ask before `runs merge <n> --yes`. `runs changes <n> --note "…"` sends it back; `runs card <n>` brings the live card down. More in the `ghosty-factory` skill |
223
+ | "hand this to the factory", "let the factory build it", "delegate this PR", "send it to @plan" | `ghosty factory run "<goal, why, how we know it's done>" --repo owner/repo --wait --workspace <slug> --json` → it returns at `plan_review` with `next` (the commands). Show the user the plan (`runs show <n> --full`) and ask before `runs approve <n> --plan-version N --yes`; then `runs watch <n>` until `pr_review` and ask before `runs merge <n> --yes`. `runs changes <n> --note "…"` sends it back; `runs card <n>` brings the live card down. A run that stopped moving: ask, then `runs resume <n> --yes` (`runs stop|cancel <n>` too). More in the `ghosty-factory` skill |
223
224
  | "list / show / rename a factory run", "who is @build?" | `ghosty factory runs ls --workspace <slug> [--room R]` (with time and cost), `ghosty factory runs show <n> --workspace <slug> [--full]`, `ghosty factory runs rename <n> "Title" --workspace <slug> --dry-run` then `--yes`; `ghosty agents ls --handle build [--workspace <slug>]` |
224
225
  | "clean up the board / archive test cards" | `ghosty cards archive <id> --integration X \| --column X \| --before 30d --dry-run` first, then with `--yes` after the user confirms (reversible) |
225
226
  | "which conversations does it have?" | `ghosty conversations ls <id> --json`; read one with `ghosty conversations show <id> <conv-id> --json` (`messages[]` with `role`, `text`); continue one with `ghosty chat <id> "…" --conversation <conv-id>` |
@@ -5,7 +5,7 @@ license: MIT
5
5
  compatibility: Any git repository hosted on GitHub. Network access to https://www.ghosty.studio for the docs.
6
6
  metadata:
7
7
  author: ghosty-studio
8
- version: "1.2"
8
+ version: "1.3"
9
9
  ---
10
10
 
11
11
  # Get a repo ready for the Ghosty Software Factory
@@ -117,6 +117,10 @@ back-and-forth with the user, it's a few lines, or you're still figuring out wha
117
117
  5. Show the PR and **ask before merging**: `ghosty factory runs merge <n> --yes`. If CI is still
118
118
  running it queues and goes in when it passes.
119
119
 
120
+ If a run stopped moving (nobody working, the card says «Not moving»), ask the user and then
121
+ `ghosty factory runs resume <n> --yes`; `runs stop <n>` stops a running turn and `runs cancel <n>`
122
+ closes the run.
123
+
120
124
  Exit code 1 from `--wait`/`watch` only means the timeout ran out; run `watch` again. The user can
121
125
  always follow along in the room; `ghosty factory runs card <n>` brings the live card down.
122
126