fimo 2.1.0 → 2.2.0-staging.1

package/assets/agent-templates/content-translator/scripts/translate-entries.ts

@@ -38,7 +38,7 @@ async function translate(text: string, _to: string): Promise<string> {
 
 async function writeBack(_entry: Entry, _locale: string, _value: string): Promise<void> {
   // Stub — create/update the target locale entry via
-  // `/api/management/projects/:id/envs/:env/tenant/entries/:type`.
+  // `/api/tenant/:projectId/branches/:branch/entries/:type`.
 }
 
 async function main(): Promise<void> {

package/assets/agent-templates/post-deploy-check/scripts/check-logs.ts

@@ -17,7 +17,7 @@ async function main(): Promise<void> {
   const base = process.env.FIMO_API_URL ?? 'http://localhost:3000';
 
   const since = new Date(Date.now() - minutes * 60_000).toISOString();
-  const url = `${base}/api/management/projects/${projectId}/envs/${encodeURIComponent(env)}/logs?since=${encodeURIComponent(since)}&level=error`;
+  const url = `${base}/api/management/projects/${projectId}/branches/${encodeURIComponent(env)}/logs?since=${encodeURIComponent(since)}&level=error`;
 
   try {
     const res = await fetch(url, { credentials: 'include' });

package/assets/agent-templates/seo-audit/scripts/list-routes.ts

@@ -4,9 +4,9 @@
  * Enumerate every public route in the project via the Fimo management
  * API. Returns paths the audit walks one-by-one through `fetch-page`.
  *
- * Inputs (env):
+ * Inputs (branch):
  *   - FIMO_PROJECT_ID — provided by the runtime (M16 sandbox adapter)
- *   - FIMO_ENV        — provided by the runtime
+ *   - FIMO_ENV        — provided by the runtime (legacy runtime selector)
  *   - FIMO_API_URL    — provided by the runtime
  *
  * Outputs (stdout JSON):
@@ -28,7 +28,7 @@ async function main(): Promise<void> {
     process.exit(1);
   }
 
-  const url = `${base}/api/management/projects/${projectId}/envs/${encodeURIComponent(env)}/routes`;
+  const url = `${base}/api/management/projects/${projectId}/branches/${encodeURIComponent(env)}/routes`;
   const res = await fetch(url, { credentials: 'include' });
   if (!res.ok) {
     console.error(`Failed to list routes: ${res.status} ${res.statusText}`);

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

@@ -44,7 +44,7 @@ A Fimo project is identified by `.fimo/project.json`, written by `fimo init`. Th
 
 ## Critical: commands target the Branch matching the current git branch
 
-A project can have multiple **Branches** — each is a git branch _plus_ its own DB, sandbox, preview, and assets. Project-scoped commands (`deploy`, `status`, `entries`, `diff`, …) operate on the Branch matching the **current git branch**, and print a one-line banner saying which one. New projects start on `main`. Override for a single command with the canonical `--branch <name>` flag; the legacy `--env <name>` spelling remains a compatibility alias. Never edit the link file to switch. The full git-shaped workflow (`branch` / `checkout` / `switch` / `pull` / `diff` / `merge` / `status` / `publish`) lives in `references/branches.md`.
+A project can have multiple **Branches** — each is a git branch _plus_ its own DB, sandbox, preview, and assets. Project-scoped commands (`deploy`, `status`, `entries`, `diff`, …) operate on the Branch matching the **current git branch**, and print a one-line banner saying which one. New projects start on `main`. Override for a single command with the canonical `--branch <name>` flag; the legacy `--env <name>` spelling still works, but passing both with different values fails (`BRANCH_OPTION_CONFLICT`) instead of picking one. Never edit the link file to switch. The full git-shaped workflow (`branch` / `checkout` / `switch` / `pull` / `diff` / `merge` / `status` / `publish`) lives in `references/branches.md`.
 
 ## Quick Start
 

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

@@ -15,7 +15,7 @@ fimo --branch <name> <command>  # peek at another Branch for one command (does n
 ```
 
 - **`--branch <name>`** is the canonical global override. `fimo --branch main status` inspects `main` while you stay checked out on your feature Branch.
-- **`--env <name>`** remains a compatibility alias for `--branch`; it still carries the legacy `env` wire name.
+- **`--env <name>`** remains a deprecated alias for `--branch`. Passing both with **different** values fails with `BRANCH_OPTION_CONFLICT` rather than picking a winner; passing both with the same value is fine.
 - Git-changing commands use the current branch; cross-branch status only reports the mismatch.
 - If the git branch maps to no Fimo Branch, the CLI errors with a hint (`fimo branch` to list, `fimo branch <name>` to create) rather than guessing.
 - **`main`** is the default Branch and cannot be deleted.

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

@@ -14,7 +14,7 @@ fimo preview url --all                               # print every destination a
 curl -L "$(fimo preview url)"                        # fetch the raw sandbox preview
 ```
 
-`--env <name>` remains a compatibility alias for `--branch <name>`. The API and JSON response still use the legacy `env` field and `/env/` dashboard path.
+`--env <name>` remains a deprecated alias for `--branch <name>`; the two disagreeing is an error, not a precedence rule. The JSON envelope carries `branch` and keeps `env` as a duplicate of it. Studio deep links still use the `/env/` path, which redirects to `/branch/`.
 
 ## Human and machine behavior
 
@@ -30,12 +30,14 @@ curl -L "$(fimo preview url)"                        # fetch the raw sandbox pre
   "status": "ok",
   "data": {
     "project_id": "prj_abc",
+    "branch": "main",
+    "env": "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/env/main/preview",
-    "dashboard_url": "https://fimo.ai/app/projects/prj_abc/env/main/preview"
+    "studio_url": "https://fimo.ai/app/projects/prj_abc/branch/main/preview",
+    "dashboard_url": "https://fimo.ai/app/projects/prj_abc/branch/main/preview"
   }
 }
 ```

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

@@ -71,7 +71,7 @@ artifact, and record which one.
 
 Before workers start, the root process must establish a real Fimo project and
 environment, link the migration checkout to it, and prove the data plane is
-reachable with a read such as `fimo schemas list -C <target> --env <env>` using
+reachable with a read such as `fimo schemas list -C <target> --branch <branch>` using
 the selected pinned CLI. Give workers the project id, environment, exact CLI
 invocation, and verification command. Generated `.fimo` JSON without a
 successful platform read is not initialization.
@@ -79,8 +79,8 @@ successful platform read is not initialization.
 Pick the setup path from the evidence:
 
 - **Source-backed, same framework** — copy or `git worktree` the source into the
-  target directory first, then run `fimo link -C <target> --env <env>`
-  (`fimo link <project-id> -C <target> --env <env>` when the owner supplied an
+  target directory first, then run `fimo link -C <target> --branch <branch>`
+  (`fimo link <project-id> -C <target> --branch <branch>` when the owner supplied an
   id). Link creates or selects the project, keeps the source's code, framework,
   git history, and `origin`, initializes a repository when the copy has none,
   and adds only the Fimo dependency, `.fimo/project.json`, the `fimo` remote,

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-26T08:34:43.135Z",
+  "bundledAt": "2026-08-26T13:08:32.124Z",
   "cliVersion": "2.1.0",
   "external": [
     "oxc-parser",