fimo 2.3.1 → 2.3.2-staging.1

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

@@ -54,7 +54,14 @@ Use the publication ID returned by the failed command: run `fimo publish inspect
 
 ## 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 --cursor <cursor> --json` to fetch the preceding page, or use `--all-pages` to fetch every retained page. `--before` remains a compatibility alias. Do not recreate or replace the sandbox before collecting logs, because that can discard the failure evidence.
+A failed `fimo deploy --json` names the cause in `error.details.failure_code` and the phase in `error.details.phase`: `pull` (Git synchronization into the sandbox), `install` (dependency install), `restart` (dev-server start), or `readiness` (the final preview check); `acquire` and `sync-env` are the sandbox and environment steps before them. When the failed process produced output, the same error carries `error.details.exit_code` and a bounded, redacted `error.details.log_tail` (newest line last). Read that tail first: it is the failed process's own output, and a replacement sandbox that failed is discarded, so `fimo logs` shows the preview that is still serving rather than the attempt that failed. The top-level codes remain compatible:
+
+- `SANDBOX_SYNC_FAILED` — the revision never became ready. Fix what the tail reports (a manifest or lockfile for `install`, the Git state for `pull`), then deploy again. When `error.details.failure_code` is `install_policy_blocked`, follow the typed repair in `error.details.repair`.
+- `PREVIEW_NOT_READY` — the revision landed and the dev server never served the page. Fix what the tail reports; when there is no tail, read `fimo logs --json`.
+
+`--no-wait` skips only the final readiness check. Pull, install, and dev-server failures are still reported with the same fields.
+
+When there is no tail, 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 --cursor <cursor> --json` to fetch the preceding page, or use `--all-pages` to fetch every retained page. `--before` remains a compatibility alias. Do not recreate or replace the sandbox before collecting logs, because that can discard the failure evidence.
 
 When Preview reports blocked dependency build scripts, treat that as a project security-policy repair, not a transient sandbox failure. Review every named package before approving it, then use the package manager's narrow project-owned mechanism:
 

package/assets/skills/fimo-cli/references/integrations/firecrawl.md

@@ -13,25 +13,17 @@ fimo integrations info firecrawl --json
 fimo integrations status firecrawl --json
 ```
 
-Enable with Fimo credits when the user wants the built-in account. Bare enable is enough because Firecrawl's default
-auth path is Fimo credits:
+Firecrawl is built into Fimo. Fimo owns the Firecrawl account and bills the project in Fimo credits, so enabling it is
+the whole setup and it takes no API key:
 
 ```bash
 fimo integrations enable firecrawl
 ```
 
-Use `--auth fimo` only when the command should be explicit in a script.
+`fimo integrations connect firecrawl` is refused: there is nothing to connect. If the user wants their own Firecrawl
+account, add Firecrawl's own MCP server with `fimo mcp add`, which is the generic path for a server the user owns.
 
-Connect a Firecrawl API key when the user explicitly wants to use their own Firecrawl account:
-
-```bash
-fimo integrations connect firecrawl --name client-a --token-stdin
-fimo integrations enable firecrawl --connection client-a
-```
-
-`connect` creates or repairs an organization-level connection. `enable --connection <alias>` lets the current project use that connection. Teammates and agents can use the integration, but Fimo never prints the API key back.
-
-There is no fallback between auth choices. If a named connection is selected and its key is missing or broken, repair the connection. If `fimo` is selected and the backend is not configured, report that Firecrawl needs backend setup.
+If Firecrawl is enabled and the backend is not configured, report that Firecrawl needs backend setup.
 
 Firecrawl `monitor.*` tools monitor websites for changes. `monitor.list` shows the website change monitors available in the current project.
 
@@ -71,15 +63,6 @@ Request several formats:
 fimo integrations run firecrawl scrape --url https://example.com --formats markdown,summary,links
 ```
 
-Try a named connection for one run without changing the project default:
-
-```bash
-fimo integrations run firecrawl scrape --url https://example.com --connection client-b
-```
-
-This only works after a named Firecrawl connection already exists. The current CLI does not yet create Firecrawl API-key
-connections automatically for you; create one first with `fimo integrations connect firecrawl --name <name> --token-stdin`.
-
 Map URLs from a site:
 
 ```bash
@@ -196,9 +179,7 @@ fimo deploy
 2. Load `references/integrations.md` and this Firecrawl reference.
 3. Run `fimo integrations status firecrawl --json`.
 4. If Firecrawl is not enabled, ask before enabling unless the user already requested setup.
-5. Use bare `fimo integrations enable firecrawl` for the built-in account unless the user asks to bring their own key.
-   If they bring a key, run `fimo integrations connect firecrawl --name <name> --token-stdin`, then
-   `fimo integrations enable firecrawl --connection <name>`.
+5. Run `fimo integrations enable firecrawl`. That is the whole setup; there is no key to ask for.
 6. For one-off research, pick the smallest action that answers the question:
    - `search` to get query-relevant excerpts and source URLs.
    - `scrape` to read one known page when the excerpt lacks context or exact wording matters.
@@ -213,7 +194,6 @@ fimo deploy
 
 - `Integration 'firecrawl' is not enabled for this project.` Enable it first or ask the user.
 - `Fimo Firecrawl account is not configured on this backend.` Backend needs `FIRECRAWL_API_KEY`.
-- `Firecrawl API key is missing.` Repair the organization connection with `fimo integrations connect firecrawl --name <name> --token-stdin`.
 - Provider action errors. Retry only when the query, URL, timeout, or transient network state changed; otherwise report the provider error.
 
 ## Good Recipes

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

@@ -1,6 +1,6 @@
 # Integrations
 
-Use integrations to enable external services for a Fimo project. API keys are stored by Fimo and never printed back to the CLI. Teammates and agents receive access to the integration, not the underlying token.
+Use integrations to enable external services for a Fimo project. Firecrawl and Fal are built into Fimo: Fimo owns the provider account and bills the project in Fimo credits, so they take no API key at all. Every other credential (MCP servers, OAuth workspaces) is stored encrypted by Fimo and never printed back to the CLI. Teammates and agents receive access to the integration, not the underlying token.
 
 Start with `fimo integrations list` whenever the task could benefit from an external service. It is the project-scoped,
 runtime-truthful inventory; use `info` only for the relevant integration instead of loading every provider's tools into
@@ -14,7 +14,7 @@ fimo integrations info firecrawl
 fimo integrations status firecrawl
 ```
 
-`info` shows supported auth choices, required credentials, tools, and recipes. `status` shows the project-specific setup state.
+`info` shows supported auth choices, required credentials, tools, and recipes. For a built-in service the only auth choice is `fimo`. `status` shows the project-specific setup state.
 
 When running inside an autonomous agent session, `fimo integrations list` shows the effective integrations available to that agent runtime, scoped by `.fimo/agents/<name>/config.yaml`. It lists only usable tools, plus the auth column and the config path that granted access.
 
@@ -48,38 +48,23 @@ Load the integration reference when the user names a specific integration:
 
 ```bash
 fimo integrations enable firecrawl
-fimo integrations enable firecrawl --auth fimo
-fimo integrations connect firecrawl --name client-a --token-stdin
-fimo integrations enable firecrawl --connection client-a
+fimo integrations enable fal
+fimo integrations disable firecrawl
 ```
 
-Bare enable uses the integration's default auth path. For Firecrawl, that is "Use Fimo credits".
+Bare enable uses the integration's default auth path. For Firecrawl and Fal that is the only path: Fimo credits, no key,
+no connection, nothing to choose. `fimo integrations connect firecrawl` and `connect fal` are refused for that reason.
 
-If an integration has no safe default auth path, bare enable should stop with a repair command instead of guessing. API-key integrations point to
-`fimo integrations connect <integration> --name <name> --token-stdin`, then
-`fimo integrations enable <integration> --connection <name>`.
+If an integration has no safe default auth path, bare enable stops with a repair command instead of guessing.
 
-Enabling API-key auth directly (`--auth api-key`) fails with the same repair copy when the project has no key configured.
-Connect first, then enable with `--connection <name>`.
-
-`--auth fimo` explicitly means "Use Fimo credits". Use project credits; no API key is needed.
-
-Switch a project back to the built-in account later with:
-
-```bash
-fimo integrations auth use firecrawl fimo
-```
-
-There is no silent fallback. If a project is enabled with a named API-key connection and that connection is missing or broken, repair the connection instead of falling back to Fimo credits.
+To bring your own Firecrawl or Fal account, add it as an MCP server (`fimo mcp add`), which is the generic path for any
+server the user owns. It does not replace the built-in service.
 
 ## Connections
 
-```bash
-fimo integrations connect firecrawl --name client-a --token-stdin
-fimo integrations enable firecrawl --connection client-a
-```
-
-Use `connect` for provider accounts, workspaces, OAuth installs, and API-key accounts. Connections live at the organization level and are shared as capabilities, not as visible credentials. A project chooses one by enabling the integration with `--connection <alias>`.
+Use `connect` for provider accounts, workspaces, OAuth installs, and user-owned MCP servers. Connections live at the
+organization level and are shared as capabilities, not as visible credentials. A project chooses one by enabling the
+integration with `--connection <alias>`.
 
 Set up Slack from **Project Settings > Connections** in Fimo Studio. Slack app creation and workspace approval require an explicit organization app choice, so the CLI does not guess one.
 
@@ -88,7 +73,6 @@ Set up Slack from **Project Settings > Connections** in Fimo Studio. Slack app c
 ```bash
 fimo integrations run firecrawl scrape --url https://example.com
 fimo integrations run firecrawl scrape --url https://example.com --formats markdown,summary,links
-fimo integrations run firecrawl scrape --url https://example.com --connection client-b
 fimo integrations run firecrawl search --query "Example Domain" --max-results 3 --include-domains example.com
 fimo integrations run firecrawl map --url https://example.com --limit 20
 fimo integrations run firecrawl crawl --url https://example.com --limit 3 --formats markdown
@@ -102,8 +86,8 @@ Firecrawl search returns query-relevant excerpts by default. Use them for direct
 full context or exact wording is needed. Search can be narrowed with source, category, domain, freshness, location,
 and country options; see the Firecrawl reference for the full command shape.
 
-Use `--connection <alias>` only for one run when a named connection already exists. It does not change the project default
-integration setup.
+Use `--connection <alias>` only for one run of a connection-backed integration when a named connection already exists. It
+does not change the project default integration setup, and built-in services have no connection to name.
 
 Firecrawl `monitor.*` tools monitor websites for changes. `monitor.list` shows the website change monitors available in the current project. Fimo cleans up those monitors when the project is deleted.
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-09-03T14:59:29.211Z",
+  "bundledAt": "2026-09-04T06:00:52.813Z",
   "cliVersion": "2.3.1",
   "external": [
     "oxc-parser",