fimo 2.2.0-staging.10 → 2.2.0-staging.11

package/assets/skills/fimo-migration/references/workflow.md

@@ -4,6 +4,15 @@ Use this as the phase contract for a complete migration. The coordinator and
 workers communicate in plain text. JSON is used only for Fimo schemas and the
 content payloads that the data-plane commands import.
 
+## Preflight: inspect and ask
+
+Before target initialization or any other write, inspect the source read-only
+and follow `references/questions-and-improvements.md`. Use the coding agent's
+native structured-question UI to ask one stacked batch for integration,
+environment, framework, and ownership decisions that the source cannot settle.
+Never move environment values or credentials without explicit consent. Do not
+ask a generic optimization question.
+
 ## Phase 0: Initialize the target
 
 1. Confirm the target path. The target is a separate directory; the source
@@ -20,9 +29,15 @@ content payloads that the data-plane commands import.
 3. Inspect the target's real `package.json`, `.fimo/config.json`, framework config, and route
    directories. They are the authority for paths. Do not infer an app root
    from a skill example and do not create a second `app/` or `src/app/` tree.
-4. If the target is non-empty and not a Fimo project, stop and ask for a target
+4. Verify dependency provenance before workers start. A project created by a
+   published CLI pins that exact CLI release and matching companion packages.
+   A local source-checkout project uses the checkout-local CLI. Stop when the
+   target records an absolute package-manager cache path, an unapproved
+   `latest`, or a CLI and API from different runtime channels; do not let the
+   producer repair release setup inside the migration.
+5. If the target is non-empty and not a Fimo project, stop and ask for a target
    path; do not overlay a template on top of it.
-5. Keep source material in `.fimo/migration/source` or another explicit source
+6. Keep source material in `.fimo/migration/source` or another explicit source
    location. Do not copy source files over the initialized target root.
 
 Write a short `.fimo/migration/migration-plan.md` containing the source
@@ -46,8 +61,10 @@ Classify the available evidence:
 For private APIs or CMSs, ask for a user-provided export or a narrowly scoped
 server-side credential. Never recover credentials from browser bundles or copy
 them into migration artifacts. If the source API URL or access is missing or
-unreachable, stop and ask the user for it; do not guess or continue with
-replacement content.
+unreachable, stop and ask whether to use scoped access, reconstruct only the
+selected published routes from the public site, or migrate code without the CMS
+records. Continue with public reconstruction only after that explicit choice,
+and record everything the rendered site cannot reveal.
 
 For API-backed content, trace active clients, endpoints, frontend types, and
 consumers first. Prefer backend source schemas; otherwise use public OpenAPI,
@@ -143,12 +160,22 @@ one generic static shell. Apply the matching framework reference before
 disposing of provider-specific rules; redirects, headers, feeds, metadata,
 forms, and freshness behavior are observable contracts.
 
+When local or bundled content becomes Fimo-backed, follow the content-delivery
+contract in `references/questions-and-improvements.md`. Preserve build-time or
+server rendering, direct lookups, bounded reads, request parallelism, and edit
+freshness. A new browser waterfall, repeated full-list read, avoidable
+sequential request chain, or stale edit is a migration regression.
+
 ## Phase 6: Fan in, validate, and report
 
 Workers return the plain-text receipt defined in `references/workers.md`.
 The coordinator checks those claims against the diff, source, CLI read-back,
-build, and rendered routes. Then an independent worker follows
-`references/workers/validator.md`; a worker saying "done" is not evidence.
+build, and rendered routes. Then it runs the read-only validation wave from
+`references/workers/validator.md`, passing the accepted scope and deliberate
+user-approved differences as task context; a worker saying "done" is not
+evidence.
+Collect the complete finding set before assigning repairs. Run disjoint repair
+owners together, wait for all repairs, and rerun one central validation wave.
 
 Write `.fimo/migration/migration-report.md` with route/content/media/form/SEO
 coverage, import counts, worker timings, unresolved items, and next actions.

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

@@ -6,7 +6,7 @@ description: >-
   Triggers: "in Fimo Studio", "in the dashboard", "in the web app",
   "how do I X in the UI", or screenshots of the dashboard. Topics
   covered: dashboard content and CMS, publishing from the dashboard,
-  dashboard SEO/domain settings, project connections, schedules and run history, outbound webhooks,
+  dashboard SEO/domain settings, project connections, agents, schedules and run history, outbound webhooks,
   visual editing, version history UI, dashboard sharing/billing, dashboard chat,
   and the command palette. Never describe
   UI locations, buttons, or panels from memory — always read the relevant
@@ -39,6 +39,7 @@ Read the relevant reference file when the user's question matches a topic.
 | AI Chat                  | references/ai-chat.md                   | "What can the AI do?", "How do I give context?"       |
 | Code Editor              | references/code-editor.md               | "How do I edit code?", "Where are my files?"          |
 | SEO Settings             | references/seo-settings.md              | "How do I set up SEO?", "Favicon, title, share image" |
+| Agents                   | references/agents.md                    | "Run an agent", "Pause an agent", "Next agent run"    |
 | Schedules                | references/schedules.md                 | "Recurring commands", "Run history", "Run now"        |
 | Webhooks                 | references/webhooks.md                  | "React to forms", "Send events to another service"    |
 | Connections              | references/connections.md               | "Connect a service", "Add an MCP server"              |
@@ -60,6 +61,7 @@ Read the relevant reference file when the user's question matches a topic.
 | Content/CMS             | AI Chat, Media Library                                                         |
 | Webhooks                | Project secrets, Forms, Publishing, Agents                                     |
 | Connections             | AI Chat, Agents, Project secrets                                               |
+| Agents                  | Connections, Project secrets, Branches                                         |
 | Schedules               | Project secrets, Environments, Agents                                          |
 | Visual changes          | Edit Mode (quick tweaks), AI Chat (bigger changes), Code Editor (full control) |
 | Something went wrong    | Version History, AI Chat                                                       |

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

@@ -0,0 +1,25 @@
+# Agents
+
+Project agents are versioned bundles from the project's repository. Studio lets project members inspect their configuration and run history, while project managers can start, stop, and resume them.
+
+## Open an agent
+
+1. Open the project and choose **Agents**.
+2. Select **Agents** again to see the available bundles.
+3. Choose an agent to open its **Runs** and **Settings** tabs.
+
+When the agent has a live schedule, its next run appears first in **Runs**, marked **Scheduled**. The row uses **Next** for its projected ID, a relative date such as **Tomorrow at 11:00 AM**, and **—** for changes and duration until it starts. **Settings** shows the bundle's declared capabilities and trigger wiring; it is read-only because the repository remains the source of truth.
+
+## Run, stop, or resume
+
+Choose **Run** to start an agent whose manual trigger is live.
+
+Choose **Stop** to pause every future trigger and stop planned or running work. Studio asks for confirmation and explains that the bundle, trigger configuration, model, capabilities, and other settings are preserved.
+
+A stopped agent shows **Paused** in the header. **Resume** makes the same triggers live again with their previous settings.
+
+Only project managers see Run, Stop, and Resume. Other project members can still see schedule timing, status, settings, and run history.
+
+## Inspect runs
+
+Open **Runs** on an agent to see only that bundle's history. Select a run to read its status, report, captured changes, and any question or review state that needs attention.

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-28T09:18:13.313Z",
+  "bundledAt": "2026-08-28T13:10:10.719Z",
   "cliVersion": "2.1.0",
   "external": [
     "oxc-parser",