@nomad-e/bluma-cli 0.18.0 → 0.20.0

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.
@@ -37,7 +37,7 @@ Always read `factorai.sh.json` in the project root before editing a deployed app
37
37
  2. edit_tool / file_write under ./my-app/ using shadcn components + semantic Tailwind (bg-background, etc.)
38
38
  3. Avoid npm run build before deploy (.next inflates ZIP); optional npx tsc --noEmit
39
39
  4. factorai.sh.deploy_app({ projectDir: "./my-app", name: "my-app" })
40
- 5. Poll get_app_status until ready (see Polling)
40
+ 5. factorai.sh.get_app_status({ appId, wait: true }) until ready or failed (see Polling)
41
41
  6. message(result) with factor-sh-url-app from manifest after ready
42
42
  ```
43
43
 
@@ -53,7 +53,7 @@ Always read `factorai.sh.json` in the project root before editing a deployed app
53
53
  ],
54
54
  deploy: true,
55
55
  })
56
- 4. Poll until building ready
56
+ 4. get_app_status({ appId, wait: true }) until ready or failed
57
57
  5. message(result) with factor-sh-url-app from manifest after ready
58
58
  ```
59
59
 
@@ -67,9 +67,9 @@ Always read `factorai.sh.json` in the project root before editing a deployed app
67
67
 
68
68
  ## Polling checklist
69
69
 
70
- 1. Call `factorai.sh.get_app_status({ appId })` every 5–10s
71
- 2. Require seeing `building` after apply/deploy before trusting `ready`
72
- 3. Verify the live route from `appContext.appUrl` (absolute URL); reject `Service Unavailable` JSON as "not live yet"
70
+ 1. Prefer `factorai.sh.get_app_status({ appId, wait: true })` blocks until `ready` or `failed`
71
+ 2. On `failed`: read `data.typescriptErrors`, `data.buildLogTail`, `data.summary` — fix code, retry apply/deploy
72
+ 3. Do not report live URL until `data.success === true` and `data.status === "ready"`
73
73
  4. Typical rebuild: 30–90 seconds
74
74
 
75
75
  ## Tool reference