fimo 2.8.0-staging.4 → 2.8.0-staging.6

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

@@ -107,7 +107,6 @@ Load the matching reference when the user's request fires its trigger. Recipes t
 - "Modify the URL of the website / change my project's address / connect a custom domain (e.g. blog.example.com) / rename the Fimo-provided `*.fimo.site` subdomain / buy a new domain through Fimo / set up a domain" → `references/domains.md`
 - "Invite a collaborator / add Marc / share with client" → `references/invite.md`
 - "Login / log out / who am I / switch organization" → `references/account.md` — note: switching **org** is `fimo orgs switch`; bare `fimo switch` changes the active **Fimo Branch** (see `references/branches.md`)
-- "Check the Inbox / what are my agents waiting on / answer a blocked agent / an agent asked me a question / approve or deny what an agent asked for (`fimo inbox *`)" → `references/inbox.md`. Never answer on the person's behalf.
 - "Create / scaffold / run / validate an agent / agent bundle / wire or enable its triggers / list agent templates / view agent runs, reports, or logs (`fimo agents *`)" → `references/agents.md`
 - "Install Fimo for my agent / fimo skills install / set up Claude Code, Codex, or Cursor for Fimo" → `references/agent-setup.md`
 - "Add, inspect, search, or run a remote MCP server / use `fimo mcp`" → `references/mcp.md`
@@ -132,7 +131,7 @@ These fire at specific moments in the project lifecycle. **Surface them proactiv
 - **You need the current preview URL but haven't changed code** (opening it, screenshotting it, handing it to another tool, the previous URL expired) → `fimo preview url`, never a no-op `fimo deploy`. See `references/preview.md`.
 - **When the user wants to try something risky / explore a redesign without touching the live site** → suggest a feature Branch: `fimo checkout -b <name>` gives an isolated Branch + DB + preview. Deploy previews there, then `fimo merge` it back and `fimo publish`. See `references/branches.md`.
 - **After completing or safely preserving the user's main work, when a confirmed Fimo platform failure still materially blocks the task after one safe recovery attempt, or a confirmed missing capability blocks completion or forces a fragile or heavily manual workaround** → use the built-in `supportReport` tool. Do not wait for the user to ask and do not stop after only describing the gap. See `references/support.md`.
-- **When a project agent has stopped and is waiting on a person** → `fimo inbox list --topic agent_question --unread` surfaces it. Show the stored form to the person, collect their explicit answer, and submit it with `fimo inbox answer`. See `references/inbox.md`.
+- **When a project agent has stopped and is waiting on a person** → a project member answers its question in Studio, on the run's page; the question email links there. The CLI cannot answer it. Never answer on the person's behalf.
 - **After the first successful `fimo deploy`** → suggest `fimo invite` if the project involves multiple people. Typical roles: `edit` for developers/content editors, `view` or `comment` for clients/stakeholders, `full` for project leads. See `references/invite.md`.
 - **After the automatic first-preview deploy on the create-new path, before the project has been published** → if there is no custom domain and the free default `*.fimo.site` slug still looks generated or was never explicitly chosen, offer to find a cleaner free subdomain. It needs no DNS. Never claim one without explicit user confirmation: suggest candidates, let the user choose, then rename it. Choosing the slug does not publish the site; the URL starts resolving only after the first successful `fimo deploy --publish`. Skip this nudge if the user already chose the default slug, attached a custom domain, or declined. See `references/domains.md` § Offer a cleaner default URL before first publish.
 - **When the user wants to modify the URL of their website** → walk through `references/domains.md`. The CLI surface covers renaming the Fimo-provided subdomain (`fimo domains rename-default`, free), attaching a domain they already own (`fimo domains add`, Premium), and buying a new domain through Fimo (`fimo domains buy`, Premium).

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

@@ -141,9 +141,10 @@ A review-first content agent could use this complete policy:
 - Discard only when no useful draft was produced or the attempted approach was fully abandoned.
 ```
 
-When a run cannot continue correctly without a decision from a project member, it may call `ask_user` instead. The
-question goes to the Fimo Inbox and the current invocation ends. It can reference zero or more sessions. An authorized
-answer starts a continuation in the same thread; the referenced work stays open and the original model process does not wait.
+When a run cannot continue correctly without a decision from a project member, it may call `ask_user` instead. Fimo
+emails project members a link to answer it in Studio, and the current invocation ends. It can reference zero or more
+sessions. An authorized answer starts a continuation in the same thread; the referenced work stays open and the original
+model process does not wait.
 
 Use `ask_user` sparingly, especially from scheduled agents:
 
@@ -170,8 +171,8 @@ changes and records a brief report of what is waiting.
 
 ## Define reporting preferences when they matter
 
-Fimo's default report needs no setup: a short, scannable brief appears in email and the Inbox, while the full report in
-Fimo carries the organized evidence and depth. Do not add a reporting section merely to restate that default.
+Fimo's default report needs no setup: a short, scannable brief appears in email, while the full report in Fimo carries
+the organized evidence and depth. Do not add a reporting section merely to restate that default.
 
 When the user names an audience, depth, recurring comparison, required section, or useful visual, preserve the request
 in a short **Reporting** section of `GOAL.md`. Describe the communication outcome in ordinary language. Do not prescribe

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

@@ -1,16 +1,10 @@
 # Analytics workflow
 
-Pageview aggregates are read for the selected branch. Fimo production builds enable
-the React Router tracker; hosted preview builds disable it. Ingestion itself accepts
-resolved branches, so do not assume that every possible preview sender is excluded.
-
-For tracking setup, load `fimo-code`. Reading analytics does not install a tracker.
-If counts are zero, check the selected branch, built scripts, enabled setting,
-browser requests and stored results before diagnosing a missing implementation.
-A successful HTTP response alone does not establish that a row was stored.
-Use `fimo-code` analytics setup for the standalone `fimo-analytics` APIs.
-Confirm that the selected package release contains them before generating imports;
-older Fimo releases and existing published sites do not acquire a tracker automatically.
+Pageview aggregates are read for the selected branch. Reading analytics does not
+install tracking. For installation or missing pageview requests, load
+`fimo skills get fimo-code --ref analytics`. For zero counts, first check the
+branch, date range and device filter using the guidance below. A successful HTTP
+response alone does not establish that a row was stored.
 
 Analytics has a **retained preview for every org** — free included. The free default is a 7-day retention window, so short ranges (`today`, `yesterday`, `this_week`, `last_week`, `last_7_days`) work for everyone. **Extended date ranges and longer retention are paid** — `last_30_days`, `last_90_days`, `this_month`, `last_month`, `last_quarter`, `last_year`, and `custom` require the `canUseExtendedDateRanges` privilege, which only paid orgs have. Asking for an extended range as a free user returns a 403 with an upgrade hint.
 

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

@@ -24,15 +24,12 @@ What it refuses to touch:
 
 ## Analytics when updating
 
-Existing analytics tracking remains supported. Keep the existing integration;
-do not add a second tracker. If the project declares `fimo-analytics`, the
-update keeps it aligned with the other Fimo packages.
-
-Updating a project without a tracker does not enable analytics. If analytics
-is wanted, load `fimo skills get fimo-code --ref analytics` and check for any
-existing tracker before adding one. After the developer publishes the update,
-verify new pageviews in Studio. Existing analytics history remains available.
-The update command itself does not publish the website.
+If the project declares `fimo-analytics`, the update keeps it aligned with the
+other Fimo packages. The update never adds a tracker: React Router projects that
+tracked through `FimoProviders` before 2.8.0 need `<Analytics />`, and other
+projects without `fimo-analytics` should add it to match new projects. For setup and
+verification, load `fimo skills get fimo-code --ref analytics`. The update
+command itself does not publish the website.
 
 ## Reading the report
 

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

@@ -78,11 +78,7 @@ Each reference defines one package contract. Fetch it when the task reaches that
 
 ## Analytics
 
-For pageview installation, read [references/analytics.md](references/analytics.md).
-`FimoProviders` from `fimo-react-router` already tracks when `VITE_API_URL` and
-`VITE_ENABLE_ANALYTICS=true` are configured. Inspect the installed version and
-browser requests before adding a sender. Hosting or the neutral Vite plugin alone
-does not install a tracker. Older releases do not acquire new package exports.
+For pageview installation or debugging, read [references/analytics.md](references/analytics.md).
 
 ## Non-negotiable boundaries
 

package/assets/skills/fimo-code/references/analytics.md

@@ -1,104 +1,70 @@
 # Pageview tracking
 
-First inspect the installed package and the built page. React Router's
-`FimoProviders` already tracks when `VITE_API_URL` and
-`VITE_ENABLE_ANALYTICS=true` are present. Do not mount another sender beside an
-unmodified legacy tracker. The neutral Vite plugin and hosting alone do not
-install tracking.
+## Before adding tracking
 
-## Standalone setup
+Inspect the installed packages and the built page first; never mount a second
+sender beside one the app already renders. Projects created from current
+templates already declare `fimo-analytics` and mount `<Analytics />` in the root. `fimo-react-router` before 2.8.0
+tracked from `FimoProviders`; from 2.8.0 it does not.
 
-Install a released version of `fimo-analytics` that exposes the adapter you need.
-Keep any version/channel selector the user already chose. An older `fimo`
-release does not imply these standalone APIs exist, and existing published
-sites need a code update to gain missing instrumentation.
+Install `fimo-analytics`, preserving the project's chosen version or channel.
+Publish the code change before verifying live traffic.
 
 ```sh
 pnpm add fimo-analytics
 ```
 
-Obtain the tenant API base URL from the project's configured Fimo connection,
-and append `/e/p`. Pass that complete URL as `endpoint`. Never infer it from the
-site's public URL, guess a project hostname, or invent a discovery command. If
-the connection does not supply a tenant endpoint, obtain it before enabling
-tracking. A configured origin-relative proxy is also accepted.
-
-| Framework      | Import                                              | Placement                                    |
-| -------------- | --------------------------------------------------- | -------------------------------------------- |
-| React          | `{ Analytics }` from `fimo-analytics/react`         | Application root                             |
-| React Router   | `{ Analytics }` from `fimo-analytics/react-router`  | Inside root router                           |
-| Next App/Pages | `{ Analytics }` from `fimo-analytics/next`          | Root layout or `_app`                        |
-| Astro          | default `Analytics` from `fimo-analytics/astro`     | Shared layout, no `client:*`                 |
-| Svelte         | default `Analytics` from `fimo-analytics/svelte`    | Root component                               |
-| SvelteKit      | default `Analytics` from `fimo-analytics/sveltekit` | Root `+layout.svelte`                        |
-| Vue            | `{ Analytics }` from `fimo-analytics/vue`           | Root component, history routing              |
-| Nuxt           | `modules: ['fimo-analytics/nuxt']`                  | `analytics: { endpoint, enabled }` in config |
-
-Components accept `endpoint` and `enabled`. React example:
+## Install and mount
+
+Mount the matching component once, with no props:
+
+| Framework    | Import                                              | Placement                                                                                                                |
+| ------------ | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| React Router | `{ Analytics }` from `fimo-analytics/react-router`  | Root route component beside `<Outlet />`, or inside the existing `<BrowserRouter>` / `<HashRouter>`                      |
+| Next.js      | `{ Analytics }` from `fimo-analytics/next`          | App Router: inside `<body>` in `app/layout.tsx`. Pages Router: beside `<Component {...pageProps} />` in `pages/_app.tsx` |
+| Astro        | default `Analytics` from `fimo-analytics/astro`     | Shared layout, no `client:*` directive                                                                                   |
+| SvelteKit    | default `Analytics` from `fimo-analytics/sveltekit` | Root `src/routes/+layout.svelte`                                                                                         |
+| React (Vite) | `{ Analytics }` from `fimo-analytics/react`         | Application root                                                                                                         |
+| Svelte       | default `Analytics` from `fimo-analytics/svelte`    | Root component                                                                                                           |
+| Vue          | `{ Analytics }` from `fimo-analytics/vue`           | Root component                                                                                                           |
 
 ```tsx
 import { Analytics } from 'fimo-analytics/next';
-<Analytics endpoint={endpoint} enabled={isProduction} />;
+<Analytics />;
 ```
 
-For Nuxt, also install the optional build peer with `pnpm add -D @nuxt/kit`.
-Next owns its client and Suspense boundaries. SvelteKit uses committed
-navigation; Nuxt covers reused pages and query changes. Generic React, Vue and
-Svelte observe history. For a router that changes the URL before committing,
-use the manual core. For Vue Router, initialize in `onMounted` after initial
-router readiness, send once, subscribe to `router.afterEach`, send only when
-`failure` is falsy, and remove the subscription and destroy on unmount.
-
-```ts
-import { init } from 'fimo-analytics';
-const analytics = init({ endpoint, enabled: isProduction, routing: 'manual' });
-// In the router's successful-navigation callback:
-analytics.pageview();
-// During cleanup:
-analytics.destroy();
-```
+For Nuxt, mount nothing: add `'fimo-analytics/nuxt'` to `modules` in
+`nuxt.config.ts` and run `pnpm add -D @nuxt/kit`.
 
-Vanilla apps can omit `routing` to track the initial page and browser history.
-Hash routers can pass `{ path: resolvedVirtualPath, pageName }` to `pageview`;
-the React Router adapter already reads its router's virtual location.
+The generic React, Svelte and Vue components observe browser history and do not
+resolve hash-router paths; use a framework adapter when one exists.
 
-For plain HTML, copy the installed `dist/browser.js` into static assets:
+For a plain HTML Vite site, copy `node_modules/fimo-analytics/dist/browser.js`
+to `public/fimo-analytics.js` and add this classic script to `index.html`:
 
 ```html
-<script defer src="/fimo-analytics.js" data-endpoint="https://YOUR-TENANT-API-HOST/e/p" data-enabled="true"></script>
+<script
+  defer
+  src="/fimo-analytics.js"
+  data-endpoint="%VITE_API_URL%/e/p"
+  data-enabled="%VITE_ENABLE_ANALYTICS%"
+></script>
 ```
 
-Use a classic script, not `type="module"`. Set `data-enabled="false"` in preview
-builds. No framework peer is required for core or HTML. Framework peers are
-optional and only the chosen adapter's framework is needed.
-
-## Choose the enabled guard
-
-Tracking defaults to enabled, so always pass `enabled`. Never use `NODE_ENV`:
-a Fimo hosted preview is a production build, so that guard leaves previews
-reporting. Read the build variable Fimo already sets:
-
-| Framework                 | Guard                                              |
-| ------------------------- | -------------------------------------------------- |
-| React Router and any Vite | `import.meta.env.VITE_ENABLE_ANALYTICS === 'true'` |
-| Next.js                   | `process.env.NEXT_PUBLIC_FIMO_ENV === 'prod'`      |
-| Build-time server env     | `process.env.FIMO_ENV === 'prod'`                  |
-
-Astro, SvelteKit, Svelte and Vue have no browser-visible environment name from
-Fimo. Read `FIMO_ENV` at build time and pass the boolean into the bundle through
-the framework's own public-variable mechanism. Do not invent a `PUBLIC_FIMO_ENV`
-and do not expose the whole environment name when a boolean is enough.
+## Hosting controls tracking
 
-## Verify the installed integration
+Fimo hosting provides the destination and the switch while the site builds:
+on for published sites, off for previews. Without it, as in local development,
+tracking is off; `[fimo-analytics]` in the browser console, or in build logs for
+Astro and Nuxt, says why. Do not add an `endpoint`, an `enabled` guard, or a
+`NODE_ENV` check.
 
-Standalone tracking defaults to enabled. Supply an explicit production guard;
-`bl_preview_token` also suppresses sends. SSR and disabled calls are inert.
-Do not add browser secrets, project IDs or branch claims to payloads.
+## Verify and diagnose
 
-Verify one initial POST, navigation, query-only changes, back/forward and a
-route revisit. Check duplicate mounts and cleanup. Existing visitor/session
-storage keys are retained; blocked storage uses per-document IDs. Delivery is
-best effort and has no retries. A 202 response alone does not prove persistence;
-check recorded analytics separately. Framework peer ranges are not proof that
-every older framework release was tested. Use the installed package's version
-qualification and preserve existing supported integrations when upgrading.
+On the published site, check Network for one POST to `/e/p` on the initial load
+and on each pathname or query change, including back/forward and revisits.
+Hash-only changes do not send. Previews send nothing. If requests are missing,
+check that the deployed app mounts the component and read the `[fimo-analytics]`
+diagnostics. If requests arrive but counts stay at zero, use the `fimo-cli`
+analytics reference to check the branch, date range and device filter; headless
+browsers count as bots. A 202 response does not prove a stored row.

package/assets/skills/fimo-code/references/frameworks/vite-react.md

@@ -27,7 +27,7 @@ Import it from `fimo-react-router/vite` whenever the application renders through
 
 ## Application root
 
-`FimoProviders` needs a React Router context for Studio navigation and pageview tracking. Keep the application's existing router type:
+`FimoProviders` needs a React Router context for Studio navigation. Keep the application's existing router type. For pageview tracking, read `references/analytics.md`.
 
 ```tsx
 import { QueryClient, QueryClientProvider } from '@tanstack/react-query';

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

@@ -1,6 +1,10 @@
 ## Where to Find It
 
-On desktop, the AI chat opens docked on the left by default. You can make it floating or dock it on either side from the project menu's **Chat position** submenu (Floating / Left / Right). Toggle the chat open or closed by clicking the **chat (speech-bubble) icon** in the header, or press **Cmd+Shift+H** (Mac) / **Ctrl+Shift+H** (Windows/Linux).
+Open the **Chats** tab in the project header. On a phone, the Chat tab at the bottom opens the chat list first; select a chat to open it.
+
+## Working in Several Chats
+
+Chat has its own **Chats** tab in the project header; the tab shows how many chats have unread activity. A project can have several chats, shared by everyone on the project. The left list shows them most recently active first with a status (**Working** with a spinner while replying, **Done** once the reply finished) and their last words; a dot marks unread activity. Select **+** for a new chat (its name comes from the first message; an empty chat offers starter requests), the search icon to find a chat, the filter icon to show only Working or Done chats, and the list settings for ordering and showing read, unread, or archived chats. The buttons above an open chat (or a right-click on a row) mark it unread, pin, archive, or mute it, for you only; the settings icon opens the chat's settings, which rename it for everyone, hold the same pin, mute and archive switches, and delete it, stopping a running reply first. Each chat has only its own messages and context. The open chat is in the page address (`/chats?chat=<id>`), so a link or reload opens the same chat.
 
 ## Sending a Message
 
@@ -51,7 +55,7 @@ Delete a proposal from the Branch picker when you no longer need it. Pull is una
 
 Chat changes are prepared separately and then applied to the environment you are viewing. Most changes merge automatically.
 
-If the project changed in the same place while the AI was working, the response shows a **Review changes** card and an attention banner above the chat input. The banner remains visible when floating chat history is collapsed.
+If the project changed in the same place while the AI was working, the response shows a **Review changes** card and an attention banner above the chat input.
 
 Choose **Auto fix** or keep chatting to let Fimo continue in the retained proposal, resolve the conflict, and retry the merge. Choose **Review manually** to inspect and resolve the proposal yourself. Discarding leaves the current environment unchanged and permanently removes the proposal.
 

package/assets/skills/fimo-studio/references/command-palette.md

@@ -25,7 +25,6 @@ Studio adds commands that are relevant to the page you are viewing. Depending on
 - Uploading an asset, creating a folder, or generating an image
 - Running an agent, opening its Preview result, or resolving proposed changes
 - Editing or opening the current CMS page in Preview
-- Marking the current Inbox item read or unread, and archiving or restoring it
 - Running, pausing, resuming, or opening runs for the current schedule
 - Sending a test or opening deliveries for the current webhook
 - Inviting a member or buying a domain from the corresponding organization page

package/assets/skills/fimo-studio/references/media-library.md

@@ -28,6 +28,10 @@ Click any file to open a preview dialog:
 
 The preview shows file metadata (size, dimensions, upload date) and editable fields for **name**, **alt text**, and **caption**. Alt text and captions are generated automatically by AI after upload -- you'll see a **Generating with AI** indicator, then an **AI generated** badge once they're ready, and you can edit the suggested text inline. From here you can also **copy the link** or **send the file to chat**. To **move**, **rename**, or **delete** a file, use its right-click menu in the grid instead.
 
+## Replacing a File in Content
+
+In a file's details, choose **Replace file**, pick a replacement, then select **Continue** to review the Current Branch reference count. **Back** or **Escape** returns to the picker with the choice preserved; closing the picker returns to the file's details. Only confirming the replacement changes references. Main, the live site, other Branches, and the original file stay unchanged.
+
 ## AI Image Generation
 
 1. Click the **Plus (+) dropdown** in the media library and select **Generate Image**.

package/assets/skills/fimo-studio/references/publish-and-deploy.md

@@ -31,7 +31,7 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
 - **"Publishing"** — Publishing is in progress. A spinner and a **Publishing** status badge show while it builds, and the button is disabled.
 - **"Published"** — Your site is live. A **Published** status badge appears, your live URL is listed under a **Published site** heading as a clickable link, and a **Last published** date and time is shown.
 - **"Couldn't publish · N issues"** — Project validation found issues that must be fixed first. Choose **Fix with Fimo** to send the safe issue list to the project chat and ask Fimo to repair it.
-- **"Latest update failed"** — The newest publication did not finish. The panel says what went wrong and, for a site that was published before, that the previous version remains the active release — so it can appear beside **Published**. It stays until a newer publication finishes. **View details** opens the reader's Inbox item about the failure, which offers **Open publishing** and **Contact support**. Studio never shows the build output; read it with `fimo publish logs <id>`, taking the id from `fimo publish list`. The person who published and the project's managers get that Inbox item, plus an email unless they turned off **Publication failures** in Account settings → Notifications.
+- **"Latest update failed"** — The newest publication did not finish. The panel says what went wrong and, for a site that was published before, that the previous version remains the active release — so it can appear beside **Published**. It stays until a newer publication finishes. Studio never shows the build output; read it with `fimo publish logs <id>`, taking the id from `fimo publish list`. The person who published and the project's managers get an email that opens this panel, unless they turned off **Publication failures** in Account settings → Notifications.
 
 ## Key Concepts
 

package/assets/skills/fimo-studio/references/visual-editing.md

@@ -4,13 +4,15 @@ Click the **Edit mode** icon in the preview header, next to Share, or press **Al
 
 ## Selecting and Editing Elements
 
-Once in edit mode, click an element in the preview. An orange outline highlights it. Plain CMS-managed text edits in place; images, rich text, and structured fields open the side editor.
+Once in edit mode, click an element in the preview. An orange outline highlights it. CMS-managed text, images, rich text, and structured fields open the side editor.
 
 ### Editing Content
 
-Type directly into selected CMS-managed text, then press **Enter** or choose **Done** above it to save. **Escape** discards the text edit; **Shift+Enter** inserts a newline. **Ask Fimo** opens chat with the selected element as context. Selecting an image opens its image editor. Image and structured-field changes save automatically; inline text is saved only with Enter or Done. Failed text saves keep the toolbar open for correction or retry. Text and images written directly in the site code remain selectable for chat context; ask the AI chat to change them.
+Update the selected field in the sidebar. Changes save automatically and appear in the preview. Failed saves keep the draft available for correction or retry. Use AI chat to change text and images written directly in the site code.
 
-The link icon in the selected element's toolbar opens its label or CMS entry. Choose **All fields** in the side editor to open the complete entry form. Studio keeps the content type's field order, scrolls to the field you selected, and focuses it in place. Loading appears only while Studio fetches this additional entry data or moves to another entry.
+The link icon beside the field in the sidebar opens its label or CMS entry. Choose **All fields** in the side editor to open the complete entry form. Studio keeps the content type's field order, scrolls to the field you selected, and focuses it in place. Loading appears only while Studio fetches this additional entry data or moves to another entry.
+
+Incomplete JSON drafts stay local. Leaving an empty JSON field saves `null` and updates the preview without reloading the page.
 
 ### References and Components
 
@@ -26,7 +28,7 @@ Selecting an element with nothing editable (a container, a spacer, a decorative
 
 ## Exiting Edit Mode
 
-Choose **Done** above selected text or click the **Edit mode** icon again to return to preview mode. Closing the side panel dismisses its selected field.
+Click the **Edit mode** icon again to return to preview mode. Closing the side panel dismisses its selected field.
 
 ## When to Use Edit Mode vs. Chat
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-10-03T17:32:27.590Z",
+  "bundledAt": "2026-10-06T12:40:39.311Z",
   "cliVersion": "2.7.1",
   "external": [
     "oxc-parser",