fimo 0.2.3-staging.10 → 0.2.3-staging.7

package/assets/skills/fimo/references/setup-plain-vite.md

@@ -36,6 +36,7 @@ pnpm add -D vite @vitejs/plugin-react @types/react @types/react-dom typescript
   "type": "module",
   "scripts": {
     "dev": "vite --host 0.0.0.0 --port 5173",
+    "prebuild": "fimo validate",
     "build": "vite build",
     "preview": "vite preview --host 0.0.0.0 --port 4173",
     "typecheck": "tsc --noEmit"
@@ -43,10 +44,6 @@ pnpm add -D vite @vitejs/plugin-react @types/react @types/react-dom typescript
 }
 ```
 
-Validate runs automatically during `fimo deploy` and API-side sandbox builds.
-For a purely local build, run `fimo validate` manually first when you need to
-sync schemas/forms/translations before `pnpm build`.
-
 ## File: `vite.config.ts`
 
 ```ts

package/assets/skills/fimo/references/setup-react-router.md

@@ -27,6 +27,7 @@ pnpm add -D @react-router/dev @react-router/node @tailwindcss/vite tailwindcss v
   "type": "module",
   "scripts": {
     "dev": "react-router dev --port 5173",
+    "prebuild": "fimo validate",
     "build": "react-router build && fimo export-static",
     "preview": "vite preview --host 0.0.0.0 --port 4173",
     "typecheck": "tsc --noEmit"
@@ -34,9 +35,7 @@ pnpm add -D @react-router/dev @react-router/node @tailwindcss/vite tailwindcss v
 }
 ```
 
-Validate runs automatically during `fimo deploy` and API-side sandbox builds.
-For a purely local build, run `fimo validate` manually first when you need to
-sync schemas/forms/translations before `pnpm build`.
+(Dependencies installed via the command above; this is the scripts shape.)
 
 ## File: `vite.config.ts`
 

package/assets/skills/fimo-cli/references/agent-setup.md

@@ -60,7 +60,7 @@ The command prints exactly which files were written, so the context-aware behavi
 You rarely have to invoke it by hand:
 
 - **Global skills auto-refresh** after a CLI version change via a marker at `~/.config/fimo/last-version`.
-- **The project skill auto-refreshes during Fimo-controlled installs** when the `fimo` package version bumps — the package's postinstall hook re-syncs the skill from `node_modules/fimo/assets/skills/fimo/` (which is version-locked to the installed package). For pnpm, `fimo create --install`, sandbox `fimopm install`, and E2E helper installs pass a scoped allow-all-builds flag so the hook can run without persisting build-script approvals in the template. npm / yarn run lifecycle scripts by default and need no extra config.
+- **The project skill auto-refreshes on `pnpm install`** when the `fimo` package version bumps — the package's postinstall hook re-syncs the skill from `node_modules/fimo/assets/skills/fimo/` (which is version-locked to the installed package). The scaffolded template approves the `fimo` and `esbuild` build scripts for pnpm (`pnpm-workspace.yaml` `allowBuilds` for pnpm 11+, plus `package.json` `pnpm.onlyBuiltDependencies` for pnpm 10-era installs). npm / yarn run lifecycle scripts by default and need no extra config.
 
 Invoke `fimo skills sync` explicitly when iterating on skill content locally, when you bumped the package via something other than a fresh install, or any time you want to force a refresh.
 

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

@@ -1,7 +1,5 @@
 # Envs & branches (git-shaped workflow)
 
-> **Beta:** Branch environments are still in beta. The CLI surface is available for early workflows, but not every command or cross-surface merge path is guaranteed to work reliably yet.
-
 A Fimo **env** is a multi-surface clone of the project: a git branch **plus** its own Neon DB branch, sandbox, preview URL, and R2 asset prefix. The CLI mirrors `git` command shapes so the workflow transfers directly — same verbs, multi-surface semantics.
 
 Every project starts with one env: `main`. You create more for feature work, deploy previews per-env, then merge back and publish.

package/assets/skills/fimo-studio/references/code-editor.md

@@ -1,6 +1,6 @@
 ## Browsing Your Files
 
-Click the **Code** tab (the code icon) in the workspace navigation, or press **Option+4** (Mac) / **Alt+4** (Windows/Linux). A file tree appears showing all your project files and folders.
+The Code tab requires **Developer Mode** to be enabled. Go to **Account Settings → Preferences** and turn on the **Developer Mode** toggle. Once enabled, click the **Code** tab (the code icon) in the workspace navigation, or press **Option+4** (Mac) / **Alt+4** (Windows/Linux). A file tree appears showing all your project files and folders.
 
 Inside the Code workspace, the left sidebar shows the **Files** tree. If you ever switch the sidebar to another view, press **Cmd+Shift+E** (Mac) / **Ctrl+Shift+E** (Windows/Linux) to bring the Files explorer back.
 

package/dist/cli/bundle.json

@@ -1,8 +1,8 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-06-23T15:06:33.888Z",
-  "cliVersion": "0.2.3-staging.10",
+  "bundledAt": "2026-06-23T08:08:32.546Z",
+  "cliVersion": "0.2.3-staging.7",
   "external": [
     "oxc-parser",
     "fsevents"