fimo 0.16.0-staging.7 → 0.16.0-staging.8

package/assets/skills/fimo-cli/SKILL.md

@@ -70,6 +70,8 @@ The working loop is local: run the app with the project's package-manager `dev`
 
 Keep `fimo validate --json` at the front of the project's `build` script, which is where the bundled templates put it. The hosted build runs that script, so validation runs on the exact code being published and a rejected build reports the failing rule instead of a generic build error. Removing it is the developer's call, but do not drop it while editing `package.json` for other reasons.
 
+**`fimo validate` does not type check.** Run the project's own `typecheck` or `check` script after changing code.
+
 ## Decision Tree
 
 Load the matching reference when the user's request fires its trigger. Recipes that involve writing code also need the `fimo-code` skill's package references — they're called out where relevant.

package/assets/skills/fimo-cli/references/agents.md

@@ -78,7 +78,7 @@ There is no all-capabilities wildcard; keeping the list explicit makes each agen
 | `webhooks:write`             | Create, modify, delete, or trigger webhooks | High         |
 | `schedules:read`             | Read schedule configs and run history       | Low          |
 | `schedules:write`            | Create, change, or trigger scheduled runs   | Critical     |
-| `fimo:logs:read`             | Read production logs                        | Low          |
+| `fimo:logs:read`             | Read project deployment logs                | Low          |
 | `fimo:analytics:read`        | Read analytics data                         | Low          |
 | `fimo:preview:read`          | Read a current preview URL                  | Low          |
 | `fimo:history:read`          | Read project restore points                 | Low          |
@@ -92,6 +92,9 @@ If a capability is missing, the related command is denied and the agent should c
 blocker. Add the capability to `capabilities.yaml`, run `fimo agents validate <name>`, deploy the bundle, and start a
 new run. A denied capability does not grant access to anything else.
 
+Studio chat and project-bound Slack turns receive `fimo:logs:read`. Autonomous agents receive it only when their
+`capabilities.yaml` declares it; use `fimo logs` with the deploy guidance when diagnosing a failed preview.
+
 Example for a content editor that can read and update entries but cannot change schemas:
 
 ```yaml

package/assets/skills/fimo-cli/references/deploy.md

@@ -48,6 +48,14 @@ When reporting the result, open `preview_url` for a person and use `sandbox_url`
 
 Public project variables managed with `fimo vars add` and `fimo vars update` are injected into preview/build/deploy runtimes. Project secrets are not injected into app builds; agents request secrets separately through their own config. See `references/project-vars-and-secrets.md`.
 
+## Diagnose a failed publication
+
+Use the publication ID returned by the failed command: run `fimo publish inspect <id> --json` for its durable status, then `fimo publish logs <id> --json` for a bounded build-log tail. Logs come from the hosting provider and may be unavailable after its deployment is reclaimed.
+
+## Diagnose a failed preview deploy
+
+If the sandbox fails to install dependencies or start the app, run `fimo logs --json` before retrying. Read the newest install and dev-server events first; when the response is truncated, use its `previousCursor` as `fimo logs --before <cursor> --json` to fetch the preceding page. Do not recreate or replace the sandbox before collecting logs, because that can discard the failure evidence.
+
 ## Framework hosting
 
 Fimo preview resolves `runtime.commands` override → package script → detected

package/assets/skills/fimo-migration/references/qa.md

@@ -112,6 +112,13 @@ Owned by the runtime lane; verified here read-only.
   unavailable in the report.
 - Deployment smoke is explicit owner opt-in; never run deploy or publish as a
   QA step.
+- When an approved publication fails, inspect its returned publication ID with
+  `fimo publish inspect <id> --json`, then read its build evidence with
+  `fimo publish logs <id> --json` before retrying. Provider logs may become
+  unavailable after the deployment is reclaimed.
+- When an approved preview deploy fails, capture `fimo logs --json` before
+  replacing or retrying the sandbox. Repair from that evidence, then make one
+  bounded retry.
 
 ## Behavior
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-21T13:03:13.526Z",
+  "bundledAt": "2026-08-21T16:01:52.520Z",
   "cliVersion": "0.15.0",
   "external": [
     "oxc-parser",