fimo 2.3.2-staging.2 → 2.4.0-staging.1

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

@@ -8,7 +8,7 @@
 
 Before deploying, Fimo fast-forwards a clean checkout that is behind and stops on dirty-behind or diverged branches. This syncs the whole branch, including config commits from Studio or locale commands.
 
-> **Just need the current preview URL?** That's `fimo preview url` — no commit or push. A cold sandbox can still take time to resolve. See `references/preview.md`. `fimo deploy` is only for pushing code changes.
+> **Just need the current preview URL?** That's `fimo preview url` — no commit or push. It waits if the hosted generation is still building. See `references/preview.md`.
 
 ## Commands
 
@@ -19,7 +19,7 @@ fimo deploy --no-restart                     # skip dev-server restart (HMR-safe
 fimo deploy -m "<commit message>" --publish  # also publish a new live version
 ```
 
-- **`fimo deploy`** — commits pending changes, pushes to the current Branch, syncs that Branch's preview sandbox, and links to the Preview and Fimo dashboard.
+- **`fimo deploy`** — commits pending changes, pushes to the current Branch, syncs that Branch's preview sandbox, and links to Fimo Studio.
 - **`fimo deploy --publish`** — same as above, then triggers a live publish and prints the live URL. Runs from the configured Production source Branch only. **Only use `--publish` when the user signals "ship it"** — first-time site completion, or an explicit "publish" / "go live" request. Otherwise stick to plain `fimo deploy`. (For a _versioned_ prod release, use `fimo publish` instead — see below.)
 - **`-m`** is the commit message used when there are uncommitted local changes; required in non-interactive shells. Omit if the working tree is already clean.
 - **`--no-restart`** — tells the sandbox to skip the dev-server restart and let Vite HMR pick up the change. Shaves ~3s per deploy. See "Skipping the dev-server restart" below for when it's safe.
@@ -35,16 +35,13 @@ fimo deploy -m "<commit message>" --publish --json
 
 Read these fields from `data`:
 
-| Field                | Destination                                                      |
-| -------------------- | ---------------------------------------------------------------- |
-| `preview_url`        | Stable, authenticated full-screen viewer for project members.    |
-| `sandbox_url`        | Short-lived raw site URL for agents, curl, and screenshot tools. |
-| `sandbox_expires_at` | Expiry of the raw sandbox URL.                                   |
-| `studio_url`         | Stable, authenticated Fimo Studio project and Branch page.       |
-| `dashboard_url`      | Deprecated compatibility alias for `studio_url`.                 |
-| `app_url`            | Public live site, returned after a successful `--publish`.       |
+| Field           | Destination                                                |
+| --------------- | ---------------------------------------------------------- |
+| `studio_url`    | Stable Fimo Studio project and Branch page.                |
+| `dashboard_url` | Deprecated compatibility alias for `studio_url`.           |
+| `app_url`       | Public live site, returned after a successful `--publish`. |
 
-When reporting the result, open `preview_url` for a person and use `sandbox_url` for machine reads. If no code changed and you only need fresh destinations, use `fimo preview url --json` instead of deploying again.
+When reporting the result, give the user `studio_url`. If a person or tool needs the hosted site itself, run `fimo preview url` after deploy.
 
 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`.
 

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

@@ -165,7 +165,7 @@ Whenever `fimo init` created or scaffolded a new project — including a Studio-
 fimo deploy -m "chore: first preview" --json
 ```
 
-`-m` is required because you run non-interactively; the deploy validates, commits pending changes, pushes, and syncs the hosted preview. It is also the sandbox warm-up — never run a separate warm-up deploy on this path. Read `data.preview_url` and `data.studio_url` from the envelope and return both links. `data.dashboard_url` remains a deprecated compatibility alias for `data.studio_url`. If the initiating request described a concrete site, build a minimal meaningful first screen before this single deploy; otherwise deploy the scaffolded site as-is and then ask what to build.
+`-m` is required because you run non-interactively; the deploy validates, commits pending changes, pushes, and syncs the preview sandbox. Return `data.studio_url` from the envelope. Run `fimo preview url --json` only when the hosted site URL itself is needed. If the initiating request described a concrete site, build a minimal meaningful first screen before this single deploy; otherwise deploy the scaffolded site as-is and then ask what to build.
 
 This first deploy creates a preview only — never add `--publish`, and treat every later deploy as offer-then-confirm. The rule does not apply when `init` cloned a project with existing code or when the work is a migration; those paths keep their normal deployment approval rules.
 

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

@@ -228,4 +228,4 @@ Visual/content QA before publish:
 fimo integrations run firecrawl scrape --url "$(fimo preview url)" --formats markdown,links --json
 ```
 
-Because command substitution captures stdout, `fimo preview url` emits the raw `sandbox_url` in this example. For JSON workflows, pass `data.sandbox_url` to Firecrawl and refresh it after `data.sandbox_expires_at`. The stable `data.preview_url` is an authenticated browser viewer and is not the Firecrawl destination.
+`fimo preview url` emits the hosted deployment URL in this example. In JSON workflows, pass `data.preview_url` to Firecrawl.

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

@@ -1,27 +1,19 @@
-# Preview URL (without deploying)
+# Hosted preview URL
 
-**Use `fimo preview url` whenever you need the current hosted preview — to open it, screenshot it, hand it to another tool, or verify a change you already deployed. Never trigger `fimo deploy` just to retrieve a URL.**
-
-`fimo deploy` commits, pushes, and syncs the sandbox before it prints destinations. `fimo preview url` skips those deployment steps and only resolves the current Branch's preview destinations.
-
-## Commands
+Use `fimo preview url` to get the current Branch's hosted preview without committing or pushing.
 
 ```bash
-fimo preview url                                      # current Branch (from git)
-fimo --branch feat/redesign preview url              # specific Branch
-fimo preview url --branch main --json                # structured output for agents / scripts
-fimo preview url --all                               # print every destination as named raw URLs
-curl -L "$(fimo preview url)"                        # fetch the raw sandbox preview
+fimo preview url
+fimo --branch feat/redesign preview url
+fimo preview url --branch main --json
+curl -L "$(fimo preview url)"
 ```
 
-`--env <name>` is rejected as a Branch selector; use `--branch <name>`. The JSON envelope carries the canonical `branch` field and may include a deprecated `env` compatibility duplicate. Studio deep links still use the `/env/` path, which redirects to `/branch/`.
+The command returns the hosted deployment URL in every output mode, whatever the project's Preview setting says: every live Branch except production owns a hosted build.
 
-## Human and machine behavior
+If the current generation is queued or building, the command waits up to five minutes, polling with a backoff. It stops at once — without waiting — on a state waiting cannot change: a build that failed, and a Branch with no hosted preview (production, or a Branch nothing has changed yet). Every failure returns `PREVIEW_URL_FAILED`; read `error.message` for which one it was and `error.hint` for the next step. Only the timeout is worth retrying.
 
-- **Interactive terminal:** shows the stable `preview_url` and `studio_url` as named links. `preview_url` opens a full-screen Fimo viewer and requires a logged-in user with access to the project.
-- **Piped or captured output:** prints only the short-lived `sandbox_url`. This preserves commands such as `curl -L "$(fimo preview url)"` and gives browsers, screenshot tools, and crawlers the directly fetchable site.
-- **`--all`:** prints `preview_url`, `studio_url`, `sandbox_url`, and `sandbox_expires_at` as named raw values for a person inspecting every destination.
-- **JSON mode** (or `FIMO_OUTPUT=json`): returns both destinations explicitly:
+JSON output contains only the Branch identity and hosted URL:
 
 ```json
 {
@@ -32,33 +24,11 @@ curl -L "$(fimo preview url)"                        # fetch the raw sandbox pre
     "project_id": "prj_abc",
     "branch": "main",
     "env": "main",
-    "preview_url": "https://fimo.ai/preview/prj_abc/main",
-    "sandbox_url": "https://preview.provider.example/session",
-    "sandbox_expires_at": "2026-08-20T18:42:00.000Z",
-    "studio_url": "https://fimo.ai/app/projects/prj_abc/branch/main/preview",
-    "dashboard_url": "https://fimo.ai/app/projects/prj_abc/branch/main/preview"
+    "preview_url": "https://fimo-preview-example.vercel.app"
   }
 }
 ```
 
-Agents must use `data.sandbox_url` for curl, Firecrawl, screenshots, and other machine reads. Use `data.preview_url` for the authenticated full-screen viewer and `data.studio_url` for the Branch inside Fimo Studio. `data.dashboard_url` is a deprecated compatibility alias for `data.studio_url`. The raw sandbox URL expires; resolve it again when `sandbox_expires_at` is near or has passed. The stable human URLs do not need to be regenerated.
-
-## When to use it
-
-- **You deployed a change and want to inspect it** — open the interactive `preview_url`.
-- **An agent or tool needs to read the site** — pipe the command or use `data.sandbox_url` from JSON.
-- **The raw URL expired** — run `fimo preview url` again; do not redeploy.
-
-## When NOT to use it
-
-- **You changed code and want it on the preview** — use `fimo deploy`. This command only retrieves destinations.
-- **You need the live published URL** — use `fimo deploy --publish` or `fimo publish`; see `references/deploy.md` and `references/domains.md`.
-
-## Cold sandbox case
-
-Resolving `sandbox_url` may take roughly 60–90 seconds when an idle sandbox must be provisioned or restarted. The stable `preview_url` performs the same authenticated resolution when a project member opens it.
-
-## See also
+Use `fimo deploy` when code still needs to be pushed. Use `fimo deploy --publish` or `fimo publish` only when the site should go live.
 
-- `references/deploy.md` — when you need to push code.
-- `references/branches.md` — Branch semantics and the global `--branch <name>` flag.
+See `references/deploy.md` for deployment and `references/branches.md` for Branch selection.

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-09-04T17:10:48.597Z",
+  "bundledAt": "2026-09-04T20:24:57.392Z",
   "cliVersion": "2.3.1",
   "external": [
     "oxc-parser",