fimo 2.9.0 → 2.10.0-staging.10

package/assets/skills/fimo-cli/references/site-checks.md

@@ -24,6 +24,9 @@ URL can describe the live version, but one synthetic run is not field data.
 
 Inspect the available tools and skills before choosing a method.
 
+- For SEO, links, images, structured data or AI readiness, start with
+  `fimo site check` (below): it picks the target and reports findings.
+
 - If `agent-browser` is available, load its skill and version-matched `core`
   guidance before using it.
 - Otherwise use equivalent browser automation, accessibility, HTTP, network,
@@ -35,6 +38,41 @@ Inspect the available tools and skills before choosing a method.
   own guidance and name the target. If it does not, report that limitation and
   use only measurements that can actually run.
 
+## Check pages with `fimo site check`
+
+`fimo site check` reads pages of the current Branch's hosted preview over HTTP
+and reports findings by topic. Name the pages a change touches, or pass `--all`
+for the whole site: the home page, the sitemap, llms.txt and every page they
+link to, at most 300 pages.
+
+```bash
+fimo site check / /pricing --json                   # named pages, every topic
+fimo site check /blog/my-post --topic meta-tags      # one topic
+fimo site check --all --branch main                  # every page of main's hosted preview
+fimo site check /about --browser --topic accessibility,mobile
+fimo site check / --url http://localhost:3000        # another address, such as your dev server
+fimo site links /pricing                             # each link on the page and its target's status
+```
+
+- Name at most 50 pages per run. Paths, bare names and full URLs all work.
+- Topics: `technical`, `meta-tags`, `broken-links`, `image-seo`,
+  `internal-linking`, `hreflang`, `ai-readiness`, `structured-data`,
+  `citation`, `lifecycle`, `refresh`, `accessibility`, `mobile`, `consent`,
+  `privacy`. Without `--topic`, every topic runs.
+- `--browser` renders every page in a real browser (needs `agent-browser`).
+  Use it for `accessibility`, `mobile`, `consent` and `privacy`; the other
+  topics read HTML. A page whose HTML has no content before JavaScript runs (a
+  client-rendered site) is read in the browser without `--browser`; the output
+  says how many.
+- The target is the Branch's hosted preview. While it builds, the command
+  waits up to 90 seconds. `prod` has no preview: check `--branch main`, or the
+  published address with `--url`.
+- Findings that compare pages (shared titles, title shape, pages nothing links
+  to, pages missing from the sitemap) need `--all`.
+- Each finding is `auto` (one right fix), `suggest` (a person decides) or
+  `note`. Read `data.output` in `--json` mode. Lines marked "could not tell"
+  are not clean: say what could not be checked.
+
 ## 3. Pick the lens the question needs
 
 | The user asks                                                   | Evidence to obtain                            |

package/assets/skills/fimo-code/references/content/richtext.md

@@ -33,7 +33,7 @@ generated client hydration helper where required.
 
 ## Entry payload
 
-CLI entry writes put every value, including the collection slug, under `data`:
+`entries create` and `entries update` take `--body` with every field, including the collection slug, under `data`:
 
 ```json
 {
@@ -46,7 +46,7 @@ CLI entry writes put every value, including the collection slug, under `data`:
 }
 ```
 
-Do not put `slug` at the top level; unsupported top-level keys are stripped.
+Keep `slug` inside `data`; `entries create` rejects unsupported top-level keys.
 
 Slugs should be lowercase, hyphenated, stable, meaningful, and unique per content type. Fimo slugifies the supplied candidate. If omitted, Fimo generates one, which is unsuitable for content with durable public URLs.
 

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

@@ -20,11 +20,11 @@ into a real Fimo project without silently dropping source material.
 > supports the source framework, preserve it explicitly and verify the runtime
 > before importing data.
 >
-> Use the CLI invocation selected for this flow for every `fimo` command in the migration. Otherwise use `npx fimo@latest`; do not install it globally.
+> Use the pinned CLI invocation selected for this flow for every `fimo` command in the migration (see CLI provenance); do not install it globally.
 
 The first pass is a faithful migration, not a framework conversion. Detect the
-source framework before creating the target and pass it explicitly to
-`fimo migrate init`. For a Next.js source, use `--framework nextjs`; never rely
+source framework before setup. When `fimo migrate init` creates the target, pass
+it explicitly: for a Next.js source, use `--framework nextjs`; never rely
 on the React Router default. The setup receipt must report the target runtime
 framework, and a mismatch is a setup failure before any schemas, entries,
 assets, labels, or forms are imported.
@@ -90,30 +90,43 @@ artifact, and record which one.
 
 ## Initialized target precondition
 
-Before workers start, the root process must establish a real Fimo project and
-environment, link the migration checkout to it, and prove the data plane is
-reachable with a read such as `fimo schemas list -C <target> --branch <branch>` using
-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.
-
-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> --branch <branch>`
-  (`fimo link <project-id> -C <target> --branch <branch>` 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` 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
-report the exact failed command and setup requirement.
+This is the one setup decision; every other reference points here. Pick the
+row that matches the user's request and the folder's state. When the target is
+genuinely unclear, ask once in the preflight question batch.
+
+| Starting point                                                                         | Setup                                                                                                                                                                                     | Original evidence                                                                                                                                                                      |
+| -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| The user asked to put this existing folder on Fimo; it is already linked               | Reuse it. Verify its project, branch, and framework. Run `fimo link <same-id> -C <folder>` only to repair it.                                                                             | Keep the baseline below.                                                                                                                                                               |
+| The same, but the folder is not linked                                                 | Keep the baseline, then run `fimo link -C <folder> --branch <branch>`, with the project id when one was chosen.                                                                           | Keep the baseline below. Never reset, overwrite, or discard existing work.                                                                                                             |
+| The source is read-only input, or the user asked for a separate target; same framework | Copy or clone the source into the target first. If the copy kept a `.fimo/project.json`, reuse that project or resolve it on purpose. Then run `fimo link -C <target> --branch <branch>`. | The original stays read-only. A `git worktree` shares the repository's config and remotes: use an independent copy or clone when adding the `fimo` remote must not touch the original. |
+| An empty or new target with nothing to adopt, or an explicit framework conversion      | `fimo migrate init <target> --framework <chosen>` (see Target setup). Never overlay a template on populated source.                                                                       | The source repository or export stays separate.                                                                                                                                        |
+
+The baseline is an exact copy of the folder's pre-migration state, kept outside
+the folder. A commit plus a detached worktree is enough only when the tree is
+clean; otherwise also keep the dirty and untracked files. Never copy secret
+values into evidence.
+
+`fimo link` keeps the folder's code, framework, git history, branches, and
+`origin`, initializes a repository when there is none, and adds only the Fimo
+dependency, `.fimo/project.json`, the `fimo` remote, and
+`.fimo/config.json#runtime.framework`. It never overlays a template.
+
+Never invent a project or organization id, and never silently relink a folder
+to another project (`fimo link --relink` needs the owner's explicit choice).
+In a non-interactive shell, `fimo link` on an unlinked folder without an id,
+and `fimo migrate init` without `--project-id`, create a new project in the
+active organization, else the only one; `fimo migrate init` also takes `--org`. With several organizations and none
+active, the CLI fails clearly: ask the user which one. Ask only for a selection
+the CLI cannot resolve.
+
+Every row ends at the same gate. Before workers start, prove the actual project
+id and branch, a runtime framework that matches the source or the chosen
+conversion, the selected pinned CLI, and a successful data-plane read such as
+`fimo schemas list -C <target> --branch <branch>`. A local marker, generated
+`.fimo` JSON, or a `ready: true` receipt without that read is not
+initialization. Give workers the project id, branch, exact CLI invocation, and
+verification command. If any setup step fails, stop before workers and report
+the exact failed command and setup requirement.
 
 ## Core contract
 
@@ -135,7 +148,9 @@ report the exact failed command and setup requirement.
   ports the source's APIs, loaders, hardcoded content, integrations, and
   visible behavior into the new framework unchanged, and Fimo schemas,
   payloads, imports, and code wiring happen later through the content workers
-  (`references/workers/content-execution.md`). If the framework or hosting
+  (`references/workers/content-execution.md`). That content pass is part of the
+  migration, never a follow-up: the `editable-text` guardrail
+  (`references/qa.md`) fails while visible text is still typed in the code. If the framework or hosting
   setup is unclear or unsupported, stop and ask instead of guessing,
   converting it, or deleting provider-specific files.
 - Inventory provider-specific files and rules before editing them. Classify each
@@ -247,25 +262,24 @@ report the exact failed command and setup requirement.
 
 ## Target setup
 
-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 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:
+Choose the setup row in "Initialized target precondition". Never modify an
+original that the row keeps read-only, and never hand-write a
+`.fimo/project.json` marker to fake a link.
+
+`fimo migrate init` serves the empty-target and conversion row. 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, the target is populated but not
+linked, or the project or organization is inaccessible:
+
+- Use an existing (empty) project:
   `fimo migrate init <target-dir> --project-id <projectId> --framework <framework> --source-platform <platform>`
-- Create a new project in an owner-supplied organization:
-  `fimo migrate init <target-dir> --org <organizationId> --framework <framework> --source-platform <platform>`
+- Create a new project:
+  `fimo migrate init <target-dir> --framework <framework> --source-platform <platform>`,
+  adding `--org <organizationId>` when the precondition's organization rule
+  needs it.
 
 `--source-platform` names what the site is migrated from (`wordpress`, `nextjs`,
 `astro`, `react-router`, `webflow`, `framer`, `squarespace`, `wix`, `carrd`,
@@ -277,9 +291,11 @@ framework files before starting workers. A Next.js target must still have its
 Next runtime/configuration (`next.config.*` and the source router shape), not a
 React Router scaffold.
 
-Setup scaffolds the target and pushes its initial commit; that is the only
-remote write it performs — it never pushes schemas, uploads assets, or imports
-entries. Setup itself never deploys or publishes; the one new-project preview
+`fimo migrate init` on a new target scaffolds it and pushes its initial
+commit. `fimo link` and reusing a linked folder scaffold and push nothing; the
+first commit waits for `fimo deploy`. Project creation or linking and that
+initial push are the only remote writes setup performs — it never pushes
+schemas, uploads assets, or imports entries. Setup itself never deploys or publishes; the one new-project preview
 deploy happens only after successful local QA (see Completion and deployment).
 
 ## Command surface
@@ -289,20 +305,18 @@ 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.
+- `fimo migrate init <dir> --project-id <projectId>` — use an existing 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:
+Setup (`fimo migrate init` or `fimo link`, chosen in Initialized target
+precondition) makes only the remote writes listed in Target setup. 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 link`: project creation or selection plus the in-place adoption of a
-  copied source target.
 - `fimo deploy` / `fimo publish` — owner-approved only.
 
 ## Migration loop
@@ -312,7 +326,7 @@ writes go through the normal commands against the linked target:
    edit, or move environment values until the user answers every consent gate.
 2. 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
+   the source framework; the `fimo migrate init` path chooses 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 —
@@ -404,8 +418,8 @@ Use one final status:
 
 Never call a migration complete when CMS entries, media mappings, forms, route
 coverage, or migration-induced content-delivery regressions are unknown. Local
-QA remains the acceptance gate. If
-`fimo migrate init` created a new Fimo project, run one `fimo deploy` after QA
+QA remains the acceptance gate. If setup created a new Fimo project
+(`fimo migrate init` or `fimo link`), run one `fimo deploy` after QA
 and return its preview and dashboard links; skip it when the user said not to
 deploy or `FIMO_MIGRATION_NO_DEPLOY=1` is set. For an existing linked project,
 offer the deployment and wait for approval. Never run `fimo publish` without an

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

@@ -10,7 +10,7 @@ items.
 
 Every data-plane write in this contract targets the linked project from
 workflow Phase 0. Planning and payload authoring need no link; running the
-writes does. When no owner-supplied target exists, the writes stay unresolved
+writes does. When setup cannot produce a linked target, the writes stay unresolved
 owner actions; do not fake a link to make them pass.
 
 ## Media Files

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

@@ -182,6 +182,13 @@ check is the acceptance evidence.
      or imprint.
    - `links-resolve`: every internal link rendered on the inventoried routes
      points at an inventoried route or an explicitly allowed path prefix.
+   - `editable-text` (required in every inventory): every visible body text node
+     sits inside an element a Fimo primitive renders, so an editor can change it
+     in Studio. A faithful port is not editable yet: text still typed in the code
+     shows "Nothing to edit". Move it to a label or a CMS field. List in `allow`
+     only the exact text the owner keeps in code, such as a brand glyph or a
+     legal line, and record why in the migration report. Assistive and hidden
+     text does not count.
 
    Internal links are resolved against the final document URL and any
    `<base href>`; query and fragment do not change route identity. An `allow`
@@ -203,14 +210,18 @@ check is the acceptance evidence.
          "source": "<owner decision>"
        },
        { "id": "footer-privacy", "kind": "required-link", "href": "/legal/privacy", "source": "<source navigation>" },
-       { "id": "nav-resolves", "kind": "links-resolve", "allow": ["/blog"], "source": "<source navigation>" }
+       { "id": "nav-resolves", "kind": "links-resolve", "allow": ["/blog"], "source": "<source navigation>" },
+       { "id": "editable-text", "kind": "editable-text", "allow": [], "source": "Fimo: visitors' text is editable" }
      ]
    }
    ```
 
 2. The validator observes the rendered application, not files in the
-   repository. For a server-rendered target, run the check with `--base-url`
-   while the built app serves locally. For a client-rendered target, save each
+   repository, with Fimo editing metadata on: build and serve with
+   `FIMO_EDITING_METADATA=true`, or observe the dev server. Without it no text is
+   marked editable and `editable-text` fails as unmeasured. For a
+   server-rendered target, run the check with `--base-url` while the app serves
+   locally. For a client-rendered target, save each
    hydrated document from the browser pass as `<captures>/index.html` and
    `<captures>/<route>.html` and pass `--captures`. Save a JSON sidecar next to
    each HTML file, such as `index.html.json` or `legal/privacy.html.json`:

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

@@ -5,7 +5,10 @@ handoff. Do not import entries or rewrite application consumers.
 
 1. Trace active source clients, endpoint/query declarations, frontend types,
    and every consumer before designing schemas. Then inspect their
-   content-bearing files, inline values, APIs, or CMS sources.
+   content-bearing files, inline values, APIs, or CMS sources, and the visible
+   text typed in route and component code: headings, paragraphs, buttons, link
+   and navigation text, alt and placeholder text. Each is an item, even when no
+   data source holds it.
 2. Classify each value as collection content, single content, an
    editor-visible label, or application-owned code. Repetition is evidence,
    not an automatic collection rule. Assistive text, identifiers, and values

package/assets/skills/fimo-migration/references/workers/validator.md

@@ -23,9 +23,10 @@ passed.
 Verify:
 
 - every source route renders with expected status and representative content;
-- the rendered guardrail inventory passes: brand, legal, compliance, and
-  navigation rules are proven on rendered HTML or a running local server with
-  `scripts/check-rendered-guardrails.mjs`, never by grepping target source.
+- the rendered guardrail inventory passes: brand, legal, compliance,
+  navigation, and `editable-text` rules are proven on rendered HTML or a running
+  local server with `scripts/check-rendered-guardrails.mjs`, never by grepping
+  target source. An inventory without an `editable-text` rule is incomplete.
   Browser captures include the response metadata required by `references/qa.md`;
 - schemas, entries, singles, labels, media, forms, and locales exist through
   CLI read-back;

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

@@ -62,8 +62,8 @@ other after it. Do not add a metadata format for a small overlap.
 
 ## Coordinator gates
 
-1. Run `fimo migrate init` and inspect the real target paths before workers
-   write.
+1. Pass the setup gate in SKILL.md "Initialized target precondition" and
+   inspect the real target paths before workers write.
 2. Start runtime/routes/content-planner/locales together, or the framework
    worker plus content planner/locales in conversion mode.
 3. Wait for every discovery receipt to become terminal, then perform one fan-in

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

@@ -15,32 +15,22 @@ ask a generic optimization question.
 
 ## Phase 0: Initialize the target
 
-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:
-   - 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). 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
-     copying an arbitrary `--template-root`, invent a project ID, or hand-write
-     `.fimo/project.json`.
-3. Inspect the target's real `package.json`, `.fimo/config.json`, framework config, and route
+1. Pick the setup row in SKILL.md "Initialized target precondition", run it,
+   and pass its gate before workers start. Framework and `--source-platform`
+   rules for `fimo migrate init` live in SKILL.md "Target setup".
+2. 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. 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.
-6. Keep source material in `.fimo/migration/source` or another explicit source
-   location. Do not copy source files over the initialized target root.
+3. Verify dependency provenance before workers start. The target pins the
+   CLI artifact that set it up: an exact published release with matching
+   companion packages, or the exact dev artifact from SKILL.md "CLI
+   provenance". Stop when the target records an absolute package-manager cache
+   path, a `file:` link, an unapproved `latest`, or a CLI and API from
+   different runtime channels; do not let the producer repair release setup
+   inside the migration.
+4. When `fimo migrate init` scaffolded the target, keep source material in
+   `.fimo/migration/source` or another explicit source location. Do not copy
+   source files over the scaffolded target root.
 
 Write a short `.fimo/migration/migration-plan.md` containing the source
 location, selected framework, actual target directories, worker owners, and

package/assets/skills/fimo-migration/scripts/check-rendered-guardrails.mjs

@@ -26,7 +26,7 @@ const USAGE =
   'Usage: node check-rendered-guardrails.mjs [project-root] [--inventory .fimo/migration/guardrails.json] ' +
   '(--captures <dir> | --base-url <http://localhost:port>) [--output .fimo/migration/guardrails-report.md]';
 
-const RULE_KINDS = ['required-text', 'forbidden-text', 'required-link', 'links-resolve'];
+const RULE_KINDS = ['required-text', 'forbidden-text', 'required-link', 'links-resolve', 'editable-text'];
 
 async function main() {
   const args = parseArgs(process.argv.slice(2));
@@ -318,6 +318,8 @@ function evaluateRules(inventory, observations) {
         return linkRule(rule, observed);
       case 'links-resolve':
         return linksResolveRule(rule, inventory, observed);
+      case 'editable-text':
+        return editableTextRule(rule, observed);
       default:
         return result(rule, false, observed.length, [`unknown rule kind ${rule.kind}`]);
     }
@@ -382,6 +384,105 @@ function linksResolveRule(rule, inventory, observed) {
   return result(rule, failures.length === 0, observed.length, failures, `${internal.length} internal links`);
 }
 
+// FIMO-3141: text a visitor reads that no Fimo primitive renders shows "Nothing to edit" in Studio, so a faithful
+// port is not done until each such text node is a label, a CMS field, or an `allow` entry the owner accepts in code
+// (a brand glyph, a legal line). Fimo marks editable text only when editing metadata is on (the dev server, or a
+// build with FIMO_EDITING_METADATA=true); a route with no mark at all is unmeasured, never passed.
+/** @param {Rule} rule @param {Observation[]} observed */
+function editableTextRule(rule, observed) {
+  const allow = new Set(asArray(rule.allow).filter(isNonEmptyString).map(normalizeText));
+  const failures = [];
+  let editable = 0;
+  let typed = 0;
+  let unmarked = 0;
+  for (const item of observed) {
+    const nodes = textNodes(item.html ?? '');
+    // A route with no mark at all is a site with no label or CMS text yet, or editing metadata that is off: its text
+    // is still listed, so a reviewer sees what would move, and the route never counts as measured.
+    if (!nodes.marked) {
+      unmarked += 1;
+      failures.push(
+        `no Fimo-marked text on ${item.route}: the site renders no label or CMS text yet, or editing metadata is off (capture the dev server or a build with FIMO_EDITING_METADATA=true)`
+      );
+    }
+    editable += nodes.editable;
+    for (const text of uniqueArray(nodes.typed)) {
+      if (allow.has(normalizeText(text))) continue;
+      typed += 1;
+      failures.push(`"${text}" on ${item.route} is typed in the code`);
+    }
+  }
+  const summary = `${editable} editable, ${typed} typed in the code${unmarked > 0 ? `, ${unmarked} routes with no Fimo mark` : ''}`;
+  return result(rule, failures.length === 0, observed.length, failures, summary);
+}
+
+const VOID_ELEMENTS = new Set([
+  'area',
+  'base',
+  'br',
+  'col',
+  'embed',
+  'hr',
+  'img',
+  'input',
+  'link',
+  'meta',
+  'param',
+  'source',
+  'track',
+  'wbr',
+]);
+
+// Body text nodes with at least two letters: those inside an element Fimo marks (`data-fimo-source`,
+// `data-fimo-richtext`) are editable; the rest are typed in the code. Assistive and hidden text is skipped: it is
+// not a label (see references/decision.md).
+/** @param {string} html @returns {{marked: boolean, editable: number, typed: string[]}} */
+function textNodes(html) {
+  const cleaned = html
+    .replace(/<!--[\s\S]*?-->/g, ' ')
+    .replace(/<[!?][^>]*>/g, ' ')
+    .replace(/<(script|style|noscript|template|head)\b[^>]*>[\s\S]*?<\/\1\s*>/gi, ' ');
+  const marked = /\sdata-fimo-(?:source|richtext)\b/i.test(cleaned);
+  /** @type {{tag: string, editable: boolean, hidden: boolean}[]} */
+  const stack = [];
+  let editable = 0;
+  /** @type {string[]} */
+  const typed = [];
+  for (const match of cleaned.matchAll(/<(\/?)([a-zA-Z][\w:-]*)([^>]*)>|([^<]+)/g)) {
+    const [, closing, rawTag, attributes = '', text] = match;
+    const parent = stack.at(-1);
+    if (text !== undefined) {
+      const value = normalizeText(decodeEntities(text));
+      if (parent?.hidden || (value.match(/\p{L}/gu) ?? []).length < 2) continue;
+      if (parent?.editable) editable += 1;
+      else typed.push(value);
+      continue;
+    }
+    const tag = rawTag.toLowerCase();
+    if (closing) {
+      const index = stack.map((entry) => entry.tag).lastIndexOf(tag);
+      if (index !== -1) stack.length = index;
+      continue;
+    }
+    if (VOID_ELEMENTS.has(tag) || attributes.trim().endsWith('/')) continue;
+    stack.push({
+      tag,
+      editable: Boolean(parent?.editable) || /\sdata-fimo-(?:source|richtext)\b/i.test(attributes),
+      hidden:
+        Boolean(parent?.hidden) ||
+        /\shidden\b/i.test(attributes.replace(/=\s*(?:"[^"]*"|'[^']*')/g, '')) ||
+        /\saria-hidden\s*=\s*["']?true\b/i.test(attributes) ||
+        /\sclass\s*=\s*["'][^"']*\b(?:sr-only|visually-hidden)\b/i.test(attributes),
+    });
+  }
+  return { marked, editable, typed };
+}
+
+/** @param {string} value */
+function normalizeText(value) {
+  return value.replace(/\s+/g, ' ').trim();
+}
+
 /** @param {Rule} rule @param {boolean} passed @param {number} observed @param {string[]} failures @param {string} [extra] @returns {Result} */
 function result(rule, passed, observed, failures, extra) {
   return { id: rule.id, kind: rule.kind, passed, observed, failures, extra: extra ?? null };

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

@@ -36,7 +36,7 @@ Use plain, friendly language. Describe what users see, where they click, and wha
 
 - **Header (desktop):** the site menu (site name; History is here) and the Branch switcher, then the workspaces: Chats, Getting started, Preview, Content, Assets, Analytics, Settings. Only workspaces the user can access appear. Workspaces that do not fit move into **More**. On the right: Earn free credits, Invite, Clone, Publish, and Merge on a Branch.
 - **Phone:** bottom tabs for Chat, Preview and Settings. Invite, Earn free credits and Clone ("Work on this site locally") move into the site menu.
-- **Settings:** General, Domains, Knowledge, SEO and Languages are listed directly. Models, Environments, Variables, Secrets, Schedules, Webhooks and Connections are under **Advanced settings**.
+- **Settings:** General, Domains, Knowledge, SEO, Integrations and Languages are listed directly. Models, Environments, Variables, Secrets, Schedules and Webhooks are under **Advanced settings**.
 - **Shortcuts:** Alt+1 Preview, Alt+2 Content, Alt+3 Assets, Alt+5 Settings, Alt+E edit mode, Cmd/Ctrl+K command palette.
 
 When a reference says "open X", X can be inside **More** on a narrow window.
@@ -59,7 +59,7 @@ Read the relevant reference file when the user's question matches a topic.
 | Variables & Secrets      | references/variables-and-secrets.md     | "Where do I put an API key?", "Public or private variable?"            |
 | 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"                               |
+| Integrations             | references/integrations.md              | "Connect a service", "Add an MCP server", "Slack channels"             |
 | Preview & Responsive     | references/preview-and-responsive.md    | "How does it look on mobile?", "How do I test sizes?"                  |
 | Visual Editing           | references/visual-editing.md            | "Can I edit visually?", "How do I change colors?"                      |
 | Version History          | references/version-history.md           | "How do I undo?", "How do I go back?"                                  |
@@ -76,7 +76,7 @@ Read the relevant reference file when the user's question matches a topic.
 | Adding images           | Media Library, AI Chat, Edit Mode                                    |
 | Content/CMS             | AI Chat, Media Library                                               |
 | Webhooks                | Site secrets, Forms, Publishing                                      |
-| Connections             | AI Chat, Site secrets                                                |
+| Apps                    | AI Chat, Site secrets                                                |
 | Schedules               | Site secrets, Environments                                           |
 | API keys                | Variables (private), Site secrets                                    |
 | Visual changes          | Edit Mode (CMS content), AI Chat (layout, styling, and code changes) |