fimo 0.20.0 → 0.21.0-staging.1

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

@@ -76,11 +76,20 @@ 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.
 
-For an existing non-empty application, reuse the CLI's real flow: create or
-select the Fimo project with `fimo init`, then run
-`fimo link <project-id> -C <target> --env <env>` and verify the data plane.
-`fimo migrate init <url> <dir>` is only usable when the target directory is
-empty or already linked.
+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
+  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,
+  and `.fimo/config.json#runtime.framework`. It never overlays a template, so
+  the target must already contain the source.
+- **Empty target, or an explicit framework conversion** — `fimo init` with the
+  chosen `--framework`, or `fimo migrate init <url> <dir>` for a URL crawl.
+  Both refuse a non-empty target and write nothing when they refuse.
+
 If authentication, organization selection, project creation, environment
 resolution, linking, or the verification read fails, stop before workers and
 report the exact failed command and setup requirement.
@@ -204,14 +213,16 @@ The target is its own Fimo project directory. The client source checkout is
 read-only evidence: never run setup inside it, never modify it, and never
 hand-write a `.fimo/project.json` marker to fake a link.
 
-`fimo migrate init` is the migration setup gate. For a source-backed migration
-it validates the target and CLI auth, then delegates project selection and
-creation to the standard `fimo init` flow (same options, no separate creation
-path), and returns a setup receipt covering auth, the target link, the
-migration directory, and readiness. It fails with a structured error when auth
-is missing, the target is missing or invalid, or the project or organization
-is inaccessible. Both forms need a real ID supplied by the owner — without
-one, stop with an unresolved owner action instead of inventing an ID:
+`fimo migrate init` is the setup gate for an empty target; a target that
+already holds the copied source is set up with `fimo link` instead (see
+Initialized target precondition). `fimo migrate init` validates the target and
+CLI auth, then delegates project selection and creation to the standard
+`fimo init` flow (same options, no separate creation path), and returns a setup
+receipt covering auth, the target link, the migration directory, and readiness.
+It fails with a structured error when auth is missing, the target is missing or
+invalid, or the project or organization is inaccessible. Both forms need a real
+ID supplied by the owner — without one, stop with an unresolved owner action
+instead of inventing an ID:
 
 - Link an owner-supplied (empty) project:
   `fimo migrate init <target-dir> --project-id <projectId> --framework <framework>`
@@ -253,12 +264,16 @@ Commands that perform actual data writes, all requiring the linked target:
   `fimo singles update`, `fimo labels set|set-many`, `fimo forms push`.
 - `fimo migrate init` (source-backed form): the project link/creation and
   initial commit push described above.
+- `fimo link`: project creation or selection plus the in-place adoption of a
+  copied source target.
 - `fimo deploy` / `fimo publish` — owner-approved only.
 
 ## Migration loop
 
-1. Run `fimo migrate init` and inspect the initialized target before any worker
-   edits it. Choose the target framework through the same canonical option as
+1. Run the setup path from "Initialized target precondition" and inspect the
+   initialized target before any worker edits it. A `fimo link` adoption keeps
+   the source framework; the `fimo init` / `fimo migrate init` paths choose the
+   target framework through the same canonical option as
    `fimo init`: pass the detected source framework for a source-backed
    migration, the framework the user explicitly chose for a conversion, and —
    for a URL-only or rebuild migration — the framework the user selected (ask

package/assets/skills/fimo-studio/references/ai-chat.md

@@ -22,7 +22,7 @@ Give the AI more to work with:
 - **+ button**: Opens a dropdown with options:
   - **Attach Assets** -- browse your media library and attach files.
   - **Attach Entries** -- attach CMS content for the AI to reference.
-  - **Upload from Computer** -- upload a file directly. ZIP archives are supported up to 20 MiB; the AI can download and inspect them under `/tmp` in its sandbox while the original stays attached to the conversation.
+  - **Upload from Computer** -- upload a file directly. For GLB, self-contained glTF, FBX, OBJ, STL, and PLY models, Fimo renders four views and saves a description so every chat model can understand the attachment. ZIP archives are supported up to 20 MiB; the AI can download and inspect them under `/tmp` in its sandbox while the original stays attached to the conversation.
   - **Draw** -- opens the drawing tool where you can sketch a wireframe or layout idea for the AI to follow.
 - **@ mentions**: Type **@** in the chat to reference specific files, pages, or content inline.
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-21T16:17:31.344Z",
+  "bundledAt": "2026-08-22T06:55:45.215Z",
   "cliVersion": "0.20.0",
   "external": [
     "oxc-parser",