fimo 2.4.0-staging.1 → 2.4.0-staging.10

package/assets/skills/fimo-code/references/frameworks/next/seo.md

@@ -0,0 +1,168 @@
+# Next.js SEO
+
+Use the installed package APIs. The app owns routing, metadata policy and
+rendering mode. Fimo supplies editable values, not a router or a merge policy.
+
+## Read, resolve, convert
+
+```ts
+import { getFimoSeo } from 'fimo/seo/server';
+import { toNextMetadata, toNextViewport } from 'fimo-next/seo';
+
+// Root layout: global defaults, never implicitly Home.
+export const generateMetadata = () => toNextMetadata(getFimoSeo());
+export const generateViewport = () => toNextViewport(getFimoSeo());
+```
+
+For a new App Router site, keep this root wiring. Home is an explicit route:
+
+```ts
+// app/page.tsx
+export const generateMetadata = () => toNextMetadata(getFimoSeo({ pathname: '/' }));
+```
+
+For each route module with configured route SEO, resolve its real pathname.
+One dynamic module handles every slug. Reuse the app's content loader and URL
+builder; do not try to infer a full pathname from Next's params in the root.
+
+```ts
+// app/blog/[slug]/page.tsx, using the app's existing loader and URL builder
+export async function generateMetadata({ params }: { params: Promise<{ slug: string }> }) {
+  const { slug } = await params;
+  const article = await getArticle(slug);
+  return toNextMetadata(
+    getFimoSeo({
+      pathname: articlePath(article),
+      routeData: { article },
+    })
+  );
+}
+```
+
+Loaders should retain their normal not-found and caching behavior. Add
+`generateViewport` at a route only when route-specific `themeColor` needs to
+apply; share the existing cached loader if both exports need its data. Other
+routes inherit the root color. When adding a page, follow the established
+pattern and keep its Fimo catalog entry aligned with a URL the app serves.
+
+`getFimoSeo({ pathname?, routeData?, rootDir? })` is synchronous and Node-only.
+No pathname reads global SEO. A pathname applies matching route overrides.
+It reads current or legacy project config using Fimo's config discovery;
+missing config/SEO returns `undefined`, malformed JSON and other I/O errors
+throw. Pass `rootDir` for a monorepo app located away from the process cwd.
+It does not cache, fetch content, infer locales or invalidate Next's caches.
+Config edits reach static output on rebuild and cached output on the app's
+normal revalidation path. Fetched route content can remain cached across
+builds; use the app's data-cache invalidation/revalidation policy and verify
+the rendered value after a content edit. Rebuild success is not freshness proof.
+
+For bundled data or Edge, supply config yourself to the pure resolver instead
+of importing the Node reader:
+
+```ts
+import { resolveSeoForPath } from 'fimo/seo';
+import { toNextMetadata } from 'fimo-next/seo';
+
+const seo = resolveSeoForPath(pathname, publicSeoConfig, { article });
+const metadata = toNextMetadata(seo);
+```
+
+Bundle only public SEO/routes, not credentials or project connection data.
+Every ancestor layout of an Edge page must also avoid the Node reader. Use
+bundled public SEO for shared root defaults, not just for the Edge leaf.
+The converters have no I/O or Next request dependency. Their output is for
+App Router; Pages Router keeps its existing `next/head` or SEO library and
+maps resolved Fimo values there. Do not convert routers for SEO.
+
+## Available fields
+
+Global values live at `seo` and overrides at `routes.<id>.seo` in the project's
+existing Fimo config (normally `.fimo/config.json`). Preserve other config keys.
+`fimo pages set` manages the route catalog but has no `--seo` flag; edit the
+config to author route SEO. For example:
+
+```json
+{
+  "seo": { "title": "Journal", "description": "Notes from the field" },
+  "routes": {
+    "article": {
+      "path": "/blog/:slug",
+      "seo": { "title": "{{article.title}}", "description": "{{article.summary}}" }
+    }
+  }
+}
+```
+
+`FimoSEO` from `fimo/seo` has these optional string fields:
+
+| Fimo field    | Next output                                            |
+| ------------- | ------------------------------------------------------ |
+| `title`       | `title`                                                |
+| `description` | `description`                                          |
+| `siteName`    | `openGraph.siteName`                                   |
+| `url`         | `metadataBase`, relative canonical and `openGraph.url` |
+| `image`       | `openGraph.images`                                     |
+| `favicon`     | `icons.icon` and `icons.apple`                         |
+| `twitterSite` | `twitter.site`                                         |
+| `robots`      | `robots` meta, not robots.txt                          |
+| `themeColor`  | `Viewport.themeColor`, not Metadata                    |
+| `locale`      | `openGraph.locale`, not URL or translation selection   |
+
+Route fields use the same shape. `{{article.title}}` reads caller-supplied
+`routeData.article.title`; `siteName` and route `label` are built-in context.
+A missing, empty or nonscalar token falls back for the entire field to its
+global value, then absence. Tracked Fimo strings are supported. This does not
+invent content when an article is missing.
+
+Converters return `{}` for undefined SEO. They leave social title/description
+and Twitter images unset so Next derives them from final page metadata/OG.
+They default OG type to `website` and Twitter card to `summary_large_image`.
+`url` is a site base; relative canonical/OG URLs follow the active route.
+App-specific canonical policies, hreflang, JSON-LD, sitemaps, robots.txt,
+verification tags and generated social images remain app-owned.
+
+## Existing app: adopt only chosen fields
+
+Inspect existing root/section/page exports and file-based icons/social images
+first. Do not spread every resolved global value into a leaf: that can replace
+a section's `noindex` policy or image. Keep the app's established metadata
+builder and choose the fields Fimo should supply. For example, an app choosing
+Fimo's editable description while retaining its title and policy:
+
+```ts
+export async function generateMetadata(context: Props) {
+  const application = await getApplicationMetadata(context);
+  const seo = getFimoSeo({ pathname: await getApplicationPathname(context) });
+  return {
+    ...application,
+    ...(seo?.description ? { description: seo.description } : {}),
+  };
+}
+```
+
+The loader/path helpers above belong to the app, not Fimo. For nested fields,
+explicitly retain the siblings the app intends to keep. Next replaces
+`openGraph`, `twitter`, `icons` and `alternates` objects across segments; there
+is no generic deep-merge or null-based suppression guarantee. Never spread
+parent `ResolvedMetadata` wholesale. File-based images can mask config values;
+preserve them unless the user chooses to replace that behavior.
+
+Use one title-suffix owner. If a Fimo template already produces a complete
+title, return `title: { absolute: seo.title }` to bypass an ancestor
+`title.template`, or remove the duplicated suffix from the Fimo template.
+Next's layout `title.template` does not apply to a page in that same segment;
+give Home its complete app-owned title when it needs the suffix too.
+Preserve deliberate Twitter-specific images; otherwise allow Next's OG fallback.
+
+The existing `buildFimoMetadata(rootDir?)` and `buildFimoViewport(rootDir?)` from `fimo-next`
+remain global-only helpers. Their string argument is a directory, not a route.
+
+## Prove the rendered result
+
+Build and request representative Home, static and dynamic routes. Check the
+actual title, description, canonical, OG/Twitter images, icons, robots and
+theme color against configured values. Include missing template data and an
+existing section policy. Confirm social titles follow the final page title,
+suffixes occur once, and no Home values leak to other routes. A helper import
+or a successful build alone does not prove SEO. Check supported runtime and
+revalidation behavior when those are part of the task.

package/assets/skills/fimo-code/references/frameworks/next.md

@@ -2,7 +2,7 @@
 
 Use this reference when `fimo describe --json` reports `framework.slug: "nextjs"`, or the project uses an App Router (`app/` or `src/app/`) or Pages Router (`pages/` or `src/pages/`) tree.
 
-Fimo supports schema-first content in both routers across static generation, ISR, request-time rendering, and Client Components. The application owns routes, locale resolution, links, `<html lang/dir>`, and per-page SEO overrides. Fimo receives the resolved locale and supplies content, labels, source metadata, client editing context, and the site-wide SEO defaults (App Router: `buildFimoMetadata`/`buildFimoViewport` in the root layout — see the router reference's Metadata section).
+Fimo supports schema-first content in both routers across static generation, ISR, request-time rendering, and Client Components. The application owns routes, locale resolution, links, `<html lang/dir>`, and SEO policy. Fimo supplies content, labels, editing context and optional resolved SEO values. For site creation, new routes or SEO changes, load `references/frameworks/next/seo.md`.
 
 ## Choose the router reference
 

package/assets/skills/fimo-code/references/frameworks/seo-head.md

@@ -0,0 +1,78 @@
+# Astro and SvelteKit SEO
+
+Resolve route data, apply the app's policy, then convert. Both imports are pure
+and bundle-safe. Neither reads files, fetches content, discovers a route, nor
+sets framework caching. Use the installed package's exports.
+
+```ts
+import { resolveSeoForPath, toSeoHead, type FimoSEO } from 'fimo/seo';
+import config from '../../.fimo/config.json'; // adjust to the actual file
+
+const resolved = resolveSeoForPath(pathname, config, { article });
+const seo: FimoSEO = { ...resolved, title: String(article.title) };
+const head = toSeoHead(seo, { canonicalUrl });
+```
+
+`resolveSeoForPath` combines global defaults and the matching catalog route's
+`seo`. Supply the actual pathname, including the app's locale/base path, and
+the already-loaded data named by templates such as `{{article.title}}`.
+Unresolved tokens fall back for the entire field. The route catalog is not a
+router. For domain/custom locale routing, the app selects locale-specific
+values explicitly. No global defaults are required to use route SEO.
+
+All `FimoSEO` fields are optional strings:
+
+| Fields                 | Output                                                                            |
+| ---------------------- | --------------------------------------------------------------------------------- |
+| `title`, `description` | Native title/description and matching Open Graph/Twitter values                   |
+| `image`                | Open Graph and Twitter share image                                                |
+| `favicon`              | Icon and apple-touch-icon links                                                   |
+| `siteName`, `locale`   | Open Graph site name and locale                                                   |
+| `twitterSite`          | Twitter site account                                                              |
+| `robots`, `themeColor` | Native meta tags                                                                  |
+| `url`                  | Site base only. The app computes `canonicalUrl`; it emits canonical and `og:url`. |
+
+`toSeoHead` returns `{ title?, meta, links }`. No configured values produces
+empty arrays. Absent/empty fields emit no corresponding tags. The default
+social type/card are `website`/`summary_large_image`; use the existing head
+component for article tags, alternate languages, JSON-LD, and other app-owned
+metadata. Filter a converter attribute before replacing that same tag.
+
+Preserve editor-owned settings through resolution; do not copy their initial
+values into app constants that overwrite config. Derive content-owned title
+and description from the same loaded entry or singleton as the visible page,
+including Home/About. Pass that data to resolution or compose its current
+values before conversion. A correct first render does not prove editability.
+
+App values win only where intentionally required. Keep overrides together and
+record their reason in the existing code or handoff, not a new ownership
+registry. Set `image: undefined` to remove a
+global image, or `robots: 'noindex'` for an editorial page before conversion. An
+explicit `undefined` in a spread removes a field; use conditional spreads to
+retain defaults for missing optional overrides. Resolve once, then compose;
+do not resolve again after applying policy.
+
+Pass a final absolute canonical URL from the app's production URL policy.
+`new URL(pathname, seo.url).href` fits a root-hosted starter; preserve existing
+base paths, domains, trailing slashes and query policy in other apps. Never use
+the preview/request origin as a production canonical. Omit `canonicalUrl` to
+emit neither canonical nor `og:url`.
+
+For existing apps, inventory the current head owner and extend it in place.
+Do not add duplicate tags or overwrite unrelated metadata. Framework-escape
+attributes; never render a raw HTML string. Each new route must use the app's
+SEO path, with route data where needed. Verify title, description, canonical,
+robots and social values in built HTML, not only the browser tab title.
+
+Imported JSON is a build snapshot. Studio config changes need sync and
+rebuild/redeploy. Content freshness follows the app's SSR/prerender/cache
+policy; changing a helper does not change that policy.
+
+For SEO integration acceptance, use an authorized isolated project to change
+one inherited setting and one content-owned value after the initial render.
+Follow the app's sync/build/cache policy, then compare built HTML and the
+hydrated head; verify intentional overrides remain unchanged. Restore the
+test values. Include client navigation and Back where supported. Never mutate
+customer production data for this check. If edits or rendering are unavailable,
+report freshness unproven. `fimo validate` checks declared contracts, not rendered
+head propagation; a green result or helper import is not this acceptance proof.

package/assets/skills/fimo-code/references/frameworks/sveltekit.md

@@ -2,7 +2,8 @@
 
 Use this reference when `fimo describe --json` reports
 `framework.slug: "sveltekit"`. SvelteKit keeps owning routes, load functions,
-locale resolution, links, document metadata, and SEO.
+locale resolution, links, document metadata, and per-page SEO; Fimo supplies the
+site-wide SEO defaults from Studio's Settings → SEO.
 
 ## Compatibility
 
@@ -12,7 +13,7 @@ SvelteKit 1 or Svelte 4 projects are compatible.
 
 ## Install both packages
 
-Every SvelteKit surface lives in `fimo-sveltekit`, installed at the same version
+SvelteKit-specific APIs live in `fimo-sveltekit`, installed at the same version
 as `fimo`:
 
 ```bash
@@ -95,9 +96,10 @@ export async function load(event) {
 <script lang="ts">
   import { afterNavigate } from '$app/navigation';
   import { FimoProvider } from 'fimo-sveltekit/components';
-  import type { LayoutData } from './$types';
   import type { Snippet } from 'svelte';
 
+  import type { LayoutData } from './$types';
+
   let { data, children }: { data: LayoutData; children: Snippet } = $props();
 
   afterNavigate(() => {
@@ -110,6 +112,57 @@ export async function load(event) {
 </FimoProvider>
 ```
 
+## SEO defaults
+
+Resolve SEO in the existing server load and return `seoHead`. Preserve the
+load's other data, including labels. A content page resolves after its read:
+`resolveSeoForPath(event.url.pathname, config, { article })`, applies app
+overrides, and returns its complete `seoHead` using `toSeoHead`.
+
+```ts
+// src/routes/+layout.server.ts, or a content page's +page.server.ts
+import { resolveSeoForPath, toSeoHead } from 'fimo/seo';
+import config from '../../.fimo/config.json';
+
+export function load({ url }) {
+  const seo = resolveSeoForPath(url.pathname, config);
+  return {
+    seoHead: toSeoHead(seo, {
+      canonicalUrl: seo?.url ? new URL(url.pathname, seo.url).href : undefined,
+    }),
+  };
+}
+```
+
+Render the final merged route data from one head owner. A leaf load's
+`seoHead` replaces the default head as a whole.
+
+```svelte
+<!-- Inside the existing root layout, alongside its provider and children -->
+<script lang="ts">
+  import { page } from '$app/state';
+  const head = $derived(page.data.seoHead ?? { meta: [], links: [] });
+</script>
+
+<svelte:head>
+  <title>{head.title ?? 'My site'}</title>
+  {#each head.meta as attributes}<meta {...attributes} />{/each}
+  {#each head.links as attributes}<link {...attributes} />{/each}
+</svelte:head>
+```
+
+Do not add a second page title beside root social tags. Use the same final
+values for all tags and check client navigation, including returning to a page
+without overrides. Existing apps can keep their current head component and
+extend it in place.
+
+The example canonical policy fits a root-hosted site; preserve existing
+production domains, base paths and trailing slashes. Imported config needs
+sync and rebuild/redeploy. Content freshness follows the app's load,
+prerender and cache policy.
+
+Read `references/frameworks/seo-head.md` for the field and composition contract.
+
 Generated values are serialized at a `load` boundary and hydrated in the
 component that renders them. Use `Text`, `RichText`, `Image`, `Video`, `Date`,
 `DateTime`, `Boolean`, `Json`, and `Number` from
@@ -142,7 +195,7 @@ component, read Fimo preview environment variables, or inject Fimo scripts.
 
 ## Boundaries
 
-- SvelteKit owns routing, history, 404s, locale URLs, and SEO.
+- SvelteKit owns routing, history, 404s, locale URLs, and per-page SEO; the root layout renders Fimo's site-wide SEO defaults.
 - `fimo-sveltekit/vite` owns dev source tagging only.
 - `FimoProvider` owns labels and the optional Studio preview bridge.
 - Do not add React, React Query, or a Vite SPA fallback to a SvelteKit project.

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

@@ -100,9 +100,9 @@ Pick the setup path from the evidence:
   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.
+- **Empty target, or an explicit framework conversion** — `fimo init` or
+  `fimo migrate init <dir>` with the chosen `--framework`. 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
@@ -151,7 +151,7 @@ report the exact failed command and setup requirement.
   unresolved item with the source evidence, the owner action, and the
   user-visible impact. Never claim completion while source content is
   unwired.
-- Prefer source code and exports over inferred crawl data. Use a public URL as
+- Prefer source code and exports over what a page renders. Use a public URL as
   visual, SEO, route, and behavior evidence when better source material exists.
   When the source defines an active CMS but its deployed records are unavailable,
   rebuild published content from the public site only after the user explicitly
@@ -205,8 +205,12 @@ report the exact failed command and setup requirement.
    - **source-backed**: source repository, export, downloaded HTML, CMS data,
      or media folder. The source files are truth; the workers read them
      directly.
-   - **url-only**: only a published URL. Run `fimo migrate <url> [dir]` to
-     create the draft evidence pack.
+   - **url-only**: only a published URL. You read the site yourself: open each
+     route in a browser, let client-side rendering finish, and record the
+     sections, copy, images, links, and forms you actually see. Fetching HTML
+     without executing JavaScript is not evidence — a client-rendered page
+     returns an empty root element, which reads as a site with no content.
+     Never report a route as covered from a fetch that returned no sections.
    - **hybrid**: source material plus a public URL. Treat source material as
      truth and the URL as comparison evidence.
 4. Read `references/questions-and-improvements.md`, finish its read-only
@@ -220,6 +224,10 @@ report the exact failed command and setup requirement.
    - Content data/code workers -> `references/workers/content-execution.md`.
    - Independent validator -> `references/workers/validator.md`.
    - Next.js source -> `references/frameworks/nextjs.md`.
+   - Astro/SvelteKit SEO -> the target's `fimo-code` framework reference and
+     `frameworks/seo-head`. Preserve the existing head owner and URL policy;
+     follow its value-ownership and edit-and-render contract, preserving
+     intentional source overrides rather than freezing editor-owned values.
    - React Router/Vite source -> load the target project's `fimo-code`
      `frameworks/react-router`, `frameworks/vite-react`, and
      `frameworks/hosting` references as applicable.
@@ -254,7 +262,8 @@ instead of inventing an ID:
 
 `--source-platform` names what the site is migrated from (`wordpress`, `nextjs`,
 `astro`, `react-router`, `webflow`, `framer`, `squarespace`, `wix`, `carrd`,
-`other`); pass what the source checkout proves, `unknown` only when nothing does.
+`other`); pass what the source proves, `unknown` only when nothing does. It is
+explicit only — nothing detects it, and omitting it records `unknown`.
 
 After setup, check `.fimo/config.json#runtime.framework` and the scaffold's
 framework files before starting workers. A Next.js target must still have its
@@ -268,32 +277,23 @@ deploy happens only after successful local QA (see Completion and deployment).
 
 ## Command surface
 
-Plan-only commands operate on local artifacts and work before the target is
-linked:
-
-- `fimo migrate init <url> [dir]` — URL migrations only: crawl the live site
-  into the draft evidence pack.
-- `fimo migrate inspect` — summarize the URL draft or an existing legacy ledger.
-- `fimo migrate import` — print the import plan; it writes no data.
-- `fimo migrate apply` / `fimo migrate refine` — URL-draft-only scaffold and
-  refinement handoff; they play no role in a source-backed migration. `apply`
-  must never run against an initialized non-React-Router target: it is the
-  legacy React Router scaffold path and must fail instead of downgrading a
-  Next.js (or another framework) project.
-- `fimo migrate manifest` / `fimo migrate report` — legacy URL-draft helpers.
-  New source-backed migrations use the plain-text migration plan, worker
-  reports, and final migration report; they do not bootstrap another JSON
-  registry.
-
-Commands that perform actual data writes, all requiring the linked target:
+`fimo migrate init <dir>` is the only migration subcommand. It sets the target
+up and nothing else: it never reads, fetches, or renders the source site, and
+it produces no evidence pack, draft, manifest, or scaffold to inspect. Reading
+the source is your job, and every finding is yours to prove.
+
+- `fimo migrate init <dir> --project-id <projectId>` — link an owner-supplied
+  project.
+- `fimo migrate init <dir> --org <organizationId>` — create a new project.
+- Both accept `--framework`, `--source-platform` (see Target setup),
+  `--install` / `--no-install`, `--agents` / `-a`, `--mode`, `--template-root`,
+  and `--json`; `-C <dir>` replaces the positional for an already-linked target.
+
+The link/creation and its initial commit push are the only remote writes. Data
+writes go through the normal commands against the linked target:
 
 - `fimo schemas push`, `fimo assets upload`, `fimo entries create|update`,
   `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. Pass `--source-platform <platform>`
-  (webflow, framer, squarespace, wix, carrd, wordpress, nextjs, astro,
-  react-router, other) when the source is known; URL crawls detect it.
-
 - `fimo link`: project creation or selection plus the in-place adoption of a
   copied source target.
 - `fimo deploy` / `fimo publish` — owner-approved only.
@@ -378,9 +378,9 @@ Commands that perform actual data writes, all requiring the linked target:
 - `references/workers/content-execution.md` - data import and code-wiring
   contracts.
 - `references/workers/validator.md` - independent fan-in validation.
-- Existing manifest/decision helper scripts are legacy compatibility tools for
-  older migration artifacts. Do not invoke them in a new migration unless the
-  user explicitly asks to replay an older artifact.
+- `scripts/apply-decision.mjs` and `scripts/write-migration-report.mjs` replay
+  an older JSON-ledger migration. A new migration writes the plain-text plan
+  and report instead; do not invoke them unless the user asks for that replay.
 
 ## Completion and deployment
 

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

@@ -119,7 +119,7 @@ Then use source headers, values, and repeated patterns:
 - excerpt/summary/dek -> `text`
 - image/photo/thumbnail/media/asset/file -> `media`, carrying the source alt on
   the media value; never add a separate alt field (`references/media.md`)
-- date/published/created/updated -> `date`; use `datetime` only when the crawled
+- date/published/created/updated -> `date`; use `datetime` only when the source
   values carry a time and a UTC offset, which `datetime` requires
 - event start/end time -> `datetime`
 - price/amount/rating/order/count -> `number`

package/assets/skills/fimo-migration/references/frameworks/nextjs.md

@@ -86,6 +86,13 @@ behavior in place; when one cannot be preserved, record an explicit gap with
 the affected routes instead of shipping pages that silently lost their share
 metadata.
 
+Before adopting Fimo SEO values, load the target's `fimo-code` reference
+`frameworks/next/seo`. Record which fields remain app-owned and which become
+editor-managed. Preserve section robots policies, title templates and
+file-based images; verify the rendered result on representative routes. Link
+the established route pattern in the project's instructions so later pages
+reuse it. Do not replace an existing SEO library or add a universal merge wrapper.
+
 ## Fimo connection
 
 Follow the target project's `fimo-code` Next.js reference and render its

package/assets/skills/fimo-migration/references/import-contract.md

@@ -9,18 +9,16 @@ assets, schemas, entries, and forms, or the gaps are owner-visible unresolved
 items.
 
 Every data-plane write in this contract targets the linked project from
-workflow Phase 0. Local artifacts never require the link — `fimo migrate
-import` only prints the import plan (it writes no data) and warns in an
-unlinked directory — running the printed commands is what needs the link.
-When no owner-supplied target exists, the writes stay unresolved owner
-actions; do not fake a link to make them pass.
+workflow Phase 0. Planning and payload authoring need no link; running the
+writes does. When no owner-supplied target exists, the writes stay unresolved
+owner actions; do not fake a link to make them pass.
 
 ## Media Files
 
 Discovery must include:
 
 - local export media folders
-- media URLs from crawled HTML/CSS
+- media URLs found in the source HTML/CSS
 - CMS media fields
 - SEO/share images
 - downloadable files linked from pages or entries

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

@@ -4,9 +4,10 @@ New migrations do not create a canonical `manifest.json`. The coordinator uses
 the readable `.fimo/migration/migration-plan.md` and
 `.fimo/migration/migration-report.md` instead.
 
-Older URL-only migrations may contain `.fimo/migrations/current/manifest.json`.
-Read it as source evidence when useful, but do not copy it into another
-registry or ask workers to keep it synchronized.
+A pre-existing project may still contain `.fimo/migrations/current/manifest.json`
+from a retired URL crawl. Nothing writes it any more, and it was never
+trustworthy on a client-rendered site: read it as a hint at most, re-verify
+every claim against the source, and do not copy it into another registry.
 
 JSON remains appropriate for actual Fimo artifacts: schema files and the
 content payloads passed to data-plane commands. It is not needed to describe

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

@@ -67,6 +67,12 @@ items.
   categories, tags, redirects, and locales are preserved when present.
 - Existing SEO, OG, and social behavior - including dynamic OG image routes -
   is preserved or explicitly reported as a gap.
+- Editor-owned SEO remains connected to its setting, entry, or singleton.
+  Inspect the implementation lane's before/after edit-and-render receipt from
+  an authorized isolated target, including preserved intentional overrides and
+  required rebuild/cache steps. If absent, report freshness unproven and hand
+  back a bounded test; this read-only validator does not mutate content.
+  `fimo validate` and matching initial tags do not prove later edits propagate.
 - When the source has no low-risk SEO or social value, safe defaults derived
   from verified page/site data are present or the missing behavior is reported;
   the migration must not invent marketing claims.

package/assets/skills/fimo-migration/references/questions-and-improvements.md

@@ -94,7 +94,7 @@ The question should sound like this:
 
 If the owner chooses the public website, stay inside the selected route scope.
 Public retrieval does not authorize private endpoint discovery, credential use,
-or a broader crawl. Record the URL, retrieval time, redirects, and every field
+or a broader sweep. Record the URL, retrieval time, redirects, and every field
 or relation that remains unknown.
 
 ## Ask what happens outside a partial migration

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

@@ -18,12 +18,11 @@ ask a generic optimization question.
 1. Confirm the target path. The target is a separate directory; the source
    checkout remains read-only evidence.
 2. Initialize or reuse exactly one linked Fimo target before workers start:
-   - URL migration: `fimo migrate init <source-url> <target-dir> --framework <framework>`
    - link an existing project: `fimo migrate init <target-dir> --project-id <projectId> --framework <framework>`
    - create a project: `fimo migrate init <target-dir> --org <organizationId> --framework <framework>`
    - add `--source-platform <platform>` when the source platform is known
      (webflow, framer, squarespace, wix, carrd, wordpress, nextjs, astro,
-     react-router, other); URL crawls detect it themselves.
+     react-router, other). Nothing detects it; omitting it records `unknown`.
      Use the detected source framework for source-backed migrations. A framework
      conversion requires an explicit user choice; URL-only and rebuild
      migrations ask the user which framework to use. Never choose a framework by
@@ -78,9 +77,12 @@ Treat absent/private fields as unknown, keep uncertain fields optional, and do
 not turn sampled values into enums. Bounded retrieval scripts are accelerators
 the planner may adapt or replace, never schema decision makers.
 
-For URL-only migrations, run `fimo migrate <url> [dir]` and inspect the
-generated `.fimo/migrations/current/` files as source evidence. Do not copy
-that crawl manifest into another canonical JSON registry.
+For URL-only migrations, read the published site yourself with a browser. Open
+every selected route, let client-side rendering finish, and record the sections,
+copy, images, links, and forms you actually see. An HTML response fetched
+without executing JavaScript is not evidence: a client-rendered page returns an
+empty root element, and treating that as the page reports an empty site as a
+complete one.
 
 ## Phase 2: Fan out workers
 

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

@@ -1,6 +1,6 @@
 # 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.
+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, resume, and delete them.
 
 ## Open an agent
 
@@ -20,6 +20,12 @@ A stopped agent shows **Paused** in the header. **Resume** makes the same trigge
 
 Only project managers see Run, Stop, and Resume. Other project members can still see schedule timing, status, settings, and run history.
 
+## Delete an agent
+
+Project managers can open **Agent actions** beside Run/Stop, choose **Delete agent**, and confirm. Deletion stops planned or running work and commits removal of the agent bundle from `main`. Recorded runs remain in history. Remove the bundle from a local checkout before deploying again, or that deployment recreates the agent.
+
+If a run cannot be stopped or `main` changes before deletion commits, the definition stays intact and the agent may remain paused. Reload and retry, or resume it if you want to keep it.
+
 ## 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.