fimo 2.10.1-staging.2 → 2.10.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/fimo-cli/SKILL.md +2 -2
- package/assets/skills/fimo-cli/SKILL.studio.md +42 -0
- package/assets/skills/fimo-cli/references/branches.md +43 -106
- package/assets/skills/fimo-cli/references/content/bulk.md +3 -12
- package/assets/skills/fimo-cli/references/content/localized.md +1 -1
- package/assets/skills/fimo-cli/references/content/sql.md +3 -10
- package/assets/skills/fimo-cli/references/deploy.md +35 -126
- package/assets/skills/fimo-cli/references/domains.md +38 -131
- package/assets/skills/fimo-cli/references/init.md +36 -170
- package/assets/skills/fimo-cli/references/projects.md +1 -1
- package/assets/skills/fimo-code/references/design.md +42 -126
- package/assets/skills/fimo-migration/SKILL.md +114 -408
- package/assets/skills/fimo-migration/references/content-delivery.md +67 -0
- package/assets/skills/fimo-migration/references/frameworks/nextjs.md +1 -1
- package/assets/skills/fimo-migration/references/qa/browser.md +41 -0
- package/assets/skills/fimo-migration/references/qa/guardrails.md +95 -0
- package/assets/skills/fimo-migration/references/qa/results.md +78 -0
- package/assets/skills/fimo-migration/references/qa.md +102 -383
- package/assets/skills/fimo-migration/references/questions-and-improvements.md +77 -168
- package/assets/skills/fimo-migration/references/setup.md +90 -0
- package/assets/skills/fimo-migration/references/workers/validator.md +2 -2
- package/assets/skills/fimo-migration/references/workers.md +1 -1
- package/assets/skills/fimo-migration/references/workflow.md +117 -171
- package/assets/skills/fimo-studio/SKILL.md +4 -1
- package/assets/skills/fimo-studio/references/ai-chat/agents.md +46 -0
- package/assets/skills/fimo-studio/references/ai-chat/default-agents.md +57 -0
- package/assets/skills/fimo-studio/references/ai-chat/routines.md +53 -0
- package/assets/skills/fimo-studio/references/ai-chat.md +39 -76
- package/assets/skills/fimo-studio/references/custom-domains.md +2 -2
- package/assets/skills/fimo-studio/references/publish-and-deploy.md +1 -1
- package/dist/cli/bundle.json +2 -2
- package/dist/cli/index.js +32 -11
- package/package.json +8 -8
- package/release.json +2 -2
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -1,394 +1,113 @@
|
|
|
1
|
-
# Migration QA
|
|
1
|
+
# Migration QA gate
|
|
2
2
|
|
|
3
|
-
Run this gate before
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
3
|
+
Run this gate before you report completion. It is read-only and starts after
|
|
4
|
+
every other worker has a terminal report. It never repairs: a failure becomes a
|
|
5
|
+
bounded repair task or an unresolved item. A check that observed nothing
|
|
6
|
+
(zero routes, links, or rules) failed.
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
Three parts are required, each on its own page:
|
|
9
|
+
|
|
10
|
+
- Rendered guardrails → `qa/guardrails`. Brand, legal, navigation, and
|
|
11
|
+
`editable-text` rules are proven on the rendered app, never by a source grep.
|
|
12
|
+
- Browser smoke and visual checks → `qa/browser`. A build and HTTP 200 are not
|
|
13
|
+
enough.
|
|
14
|
+
- Import counts and the report → `qa/results`.
|
|
9
15
|
|
|
10
|
-
|
|
11
|
-
- The source route surface is preserved: routes were not restructured to
|
|
12
|
-
shrink the migration, and no group of source pages was replaced by a generic
|
|
13
|
-
static shell.
|
|
14
|
-
- Every imported schema, entry, single, and label has a consuming target route
|
|
15
|
-
or component. Content that exists in Fimo but is not rendered by the
|
|
16
|
-
application is unwired, not covered.
|
|
17
|
-
- Every source content item is represented in the target: a content type, a
|
|
18
|
-
field, a block, a reference, a label, or an explicit unresolved item.
|
|
19
|
-
- The editorial model is Fimo-native and not silently flattened. Structured or
|
|
20
|
-
repeatable editorial sections are blocks, rich bodies are richtext, and
|
|
21
|
-
categories, authors, related items, and repeated taxonomies are references -
|
|
22
|
-
not hardcoded strings, raw IDs, or opaque JSON. Every `json` field carries a
|
|
23
|
-
recorded reason that no Fimo-native model fits.
|
|
24
|
-
- Editable shared chrome (header, footer, navigation, site settings) has a
|
|
25
|
-
singleton or other content model an owner can edit, and labels are limited to
|
|
26
|
-
small UI copy and reusable translations.
|
|
27
|
-
- Content type, field, and block names are semantic and editor-facing: no markup
|
|
28
|
-
tags, HTML attributes, locale suffixes, or column indexes.
|
|
29
|
-
- Modeling did not redesign the site: the migrated routes render the same
|
|
30
|
-
content, order, and copy as the source, and the text plan records the
|
|
31
|
-
source-to-Fimo mapping.
|
|
32
|
-
- Media alt text is attached to the media (asset metadata and media value), with
|
|
33
|
-
no standalone alt field in a content schema. Alt is never the filename, and a
|
|
34
|
-
generated fallback is recorded as generated.
|
|
35
|
-
- Every planner `sourceFile`/`sourceKey` maps to its original consumer. Imported
|
|
36
|
-
labels or prose that are only appended elsewhere, including an additive
|
|
37
|
-
“Page content” section, are unwired gaps. Use existing literal-key extraction
|
|
38
|
-
for a bounded read-only comparison when it is sound; otherwise report every
|
|
39
|
-
unmapped key from the planner consumer map. Do not build a generic AST or
|
|
40
|
-
codemod system for this check.
|
|
41
|
-
- Every CMS export file is mapped to a schema, ignored with a reason, or unresolved.
|
|
42
|
-
- Source entry counts match imported counts (entries created in Fimo), excluding
|
|
43
|
-
documented skips/unresolved. Generated seed JSON alone does not satisfy this.
|
|
44
|
-
- Every media item referenced by routes, CMS entries, SEO, or forms is uploaded to
|
|
45
|
-
the Fimo media library (Fimo asset id/URL) or has an unresolved item. A local
|
|
46
|
-
`public/` copy is not an upload mapping.
|
|
47
|
-
- Every obligation in the coordinator's consolidated media list, including
|
|
48
|
-
schema media fields and nested richtext/Tiptap image nodes, has a mapping or
|
|
49
|
-
explicit disposition; the media worker's completion claim alone is not
|
|
50
|
-
evidence. Reconcile the list against every discovery lane's media findings.
|
|
51
|
-
- Every visible form has a Fimo replacement, a preserved third-party
|
|
52
|
-
integration, or an unsupported note. A form became Fimo-native only when the
|
|
53
|
-
Fimo form matches the source behavior 1:1.
|
|
54
|
-
- The detected source framework, router, runtime, and configuration are
|
|
55
|
-
preserved. React Router/Vite remains React Router/Vite; any Next.js conversion
|
|
56
|
-
has the user's explicit choice. Unsupported or unclear hosting is unresolved,
|
|
57
|
-
not hidden by a conversion or deleted configuration.
|
|
58
|
-
- In conversion mode, the framework gate passed before content code work: the
|
|
59
|
-
conversion worker's self-checks and the coordinator's independent rerun of
|
|
60
|
-
the build and representative route checks are both recorded. A gate failure
|
|
61
|
-
caps the status at draft-only or leaves the affected routes unresolved; no
|
|
62
|
-
route was replaced by a generic shell or another framework as a fallback.
|
|
63
|
-
- Every preserved third-party integration keeps its original wiring, and the
|
|
64
|
-
credential environment keys it needs are recorded by name. A missing secret
|
|
65
|
-
is an unresolved user follow-up, never silently removed behavior.
|
|
66
|
-
- SEO title, description, canonical URL, share image, slugs, dates, authors,
|
|
67
|
-
categories, tags, redirects, and locales are preserved when present.
|
|
68
|
-
- Existing SEO, OG, and social behavior - including dynamic OG image routes -
|
|
69
|
-
is preserved or explicitly reported as a gap.
|
|
70
|
-
- Editor-owned SEO remains connected to its setting, entry, or singleton.
|
|
71
|
-
Inspect the implementation lane's before/after edit-and-render receipt from
|
|
72
|
-
an authorized isolated target, including preserved intentional overrides and
|
|
73
|
-
required rebuild/cache steps. If absent, report freshness unproven and hand
|
|
74
|
-
back a bounded test; this read-only validator does not mutate content.
|
|
75
|
-
`fimo validate` and matching initial tags do not prove later edits propagate.
|
|
76
|
-
- When the source has no low-risk SEO or social value, safe defaults derived
|
|
77
|
-
from verified page/site data are present or the missing behavior is reported;
|
|
78
|
-
the migration must not invent marketing claims.
|
|
79
|
-
- Redirects and security headers stay in the source framework config when the
|
|
80
|
-
target keeps the source runtime and host, or are translated with a recorded
|
|
81
|
-
note in the text migration report when the target runtime or host requires
|
|
82
|
-
it.
|
|
83
|
-
- Every provider-specific rule is classified as preserved, replaced, safely
|
|
84
|
-
unnecessary implementation detail, or unresolved. A deletion has evidence of
|
|
85
|
-
redundancy or the user's accepted loss.
|
|
86
|
-
- Public behavior is verified independently: blog routes and 404s, Markdown
|
|
87
|
-
negotiation, RSS, sitemap, `llms.txt`, OG/social metadata, redirects,
|
|
88
|
-
security headers, and forms where present. Cloudflare cache storage, purge,
|
|
89
|
-
and revalidation internals need no copy when proven externally irrelevant.
|
|
90
|
-
- Each content/data lane records its source-access class. Local files/exports
|
|
91
|
-
and public APIs were read under their simple access rules; private sources
|
|
92
|
-
used a user export or narrowly scoped server-side credential. Missing access
|
|
93
|
-
is unresolved for that lane, and no content was guessed.
|
|
94
|
-
- Each content family moved from local or bundled files to Fimo records its
|
|
95
|
-
build-time, request-time, or browser delivery mode before and after migration.
|
|
96
|
-
Build-time and server-rendered source content did not become a browser API
|
|
97
|
-
waterfall.
|
|
98
|
-
- Detail routes use a direct generated-client lookup when available. Indexes use
|
|
99
|
-
bounded pagination and projection. Shared reads are deduplicated, independent
|
|
100
|
-
reads start together, and page-only reads do not block a shared root layout.
|
|
101
|
-
- Production evidence labels cold and warm navigation separately and records
|
|
102
|
-
observable Fimo/API request counts, duplicates, order, and longest blocking
|
|
103
|
-
read. Development-only timing is never presented as production proof.
|
|
16
|
+
## Coverage
|
|
104
17
|
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
18
|
+
- **Routes.** Each source route is implemented, ignored with a reason, or
|
|
19
|
+
unresolved. Routes were not restructured and no page group became a generic
|
|
20
|
+
shell.
|
|
21
|
+
- **Content wired.** Each source content item is a content type, field, block,
|
|
22
|
+
reference, label, or unresolved item. Each imported schema, entry, Single,
|
|
23
|
+
and label has a consuming route or component; content in Fimo that the app
|
|
24
|
+
does not render is unwired. Each planner `sourceFile`/`sourceKey` maps to its
|
|
25
|
+
original consumer; content only appended elsewhere (an extra "Page content"
|
|
26
|
+
section) is an unwired gap. Do not build a generic AST or codemod system for
|
|
27
|
+
this check.
|
|
28
|
+
- **Fimo-native model.** Repeatable sections are blocks, rich bodies are
|
|
29
|
+
richtext, and categories, authors, related items, and taxonomies are
|
|
30
|
+
references, not strings, raw ids, or JSON. Each `json` field has a recorded
|
|
31
|
+
reason. Header, footer, navigation, and site settings are editable (a Single
|
|
32
|
+
or other model); labels hold only small UI copy. Names are semantic: no markup
|
|
33
|
+
tags, attributes, locale suffixes, or column indexes. Routes render the same
|
|
34
|
+
content, order, and copy as the source.
|
|
35
|
+
- **Counts.** Each CMS export file maps to a schema, is ignored with a reason,
|
|
36
|
+
or is unresolved. Source entry counts match the entries created in Fimo,
|
|
37
|
+
minus documented skips. Seed JSON alone does not count.
|
|
38
|
+
- **Media.** Each media item used by routes, entries, SEO, or forms is in the
|
|
39
|
+
Fimo media library or unresolved; a `public/` copy is not an upload. Each
|
|
40
|
+
obligation in the consolidated media list has a mapping or a disposition.
|
|
41
|
+
Alt text is on the media value, never the filename, never a separate schema
|
|
42
|
+
field; a generated alt is recorded as generated.
|
|
43
|
+
- **Forms and integrations.** Each visible form has a Fimo form that matches
|
|
44
|
+
the source 1:1, a preserved integration, or an unsupported note. Each
|
|
45
|
+
preserved integration keeps its wiring and lists its environment key names.
|
|
46
|
+
- **Framework.** The source framework, router, runtime, and config are kept,
|
|
47
|
+
or the owner chose a conversion. In conversion mode, the framework gate
|
|
48
|
+
passed before content code, with the worker's checks and the coordinator's
|
|
49
|
+
own rerun recorded.
|
|
50
|
+
- **SEO and host behavior.** Titles, descriptions, canonical URLs, share
|
|
51
|
+
images, slugs, dates, authors, tags, redirects, locales, and dynamic OG
|
|
52
|
+
routes are kept or reported as gaps. Editor-owned SEO stays connected to its
|
|
53
|
+
entry or Single: read the implementation lane's edit-and-render receipt from
|
|
54
|
+
an authorized isolated target, with intentional overrides kept and the
|
|
55
|
+
rebuild or cache steps named. If it is missing, report freshness unproven and
|
|
56
|
+
hand back a bounded test (`fimo validate` and matching first tags prove
|
|
57
|
+
nothing). Safe defaults come from verified data, never invented
|
|
58
|
+
claims. Redirects and security headers stay in the source config, or are
|
|
59
|
+
translated with a note when the runtime or host changes. Blog routes, 404s,
|
|
60
|
+
Markdown negotiation, RSS, sitemap, `llms.txt`, and OG output are verified.
|
|
61
|
+
Provider cache internals (storage, purge, revalidation) need no copy when
|
|
62
|
+
they are proven invisible to visitors.
|
|
63
|
+
- **Provider files.** Each is preserved, replaced, safely unnecessary, or
|
|
64
|
+
unresolved; a deletion has proof or the owner's accepted loss.
|
|
65
|
+
- **Source access.** Each content lane records its access class. Missing
|
|
66
|
+
access is unresolved, and no content was guessed.
|
|
67
|
+
- **Delivery.** Each content family moved to Fimo records its delivery mode
|
|
68
|
+
before and after, per `content-delivery`. Detail routes use direct lookups,
|
|
69
|
+
indexes are paginated and projected, and reads are deduplicated and parallel.
|
|
70
|
+
Production evidence labels cold and warm navigation separately; development
|
|
71
|
+
timing is never production proof.
|
|
109
72
|
|
|
110
73
|
## Hosting
|
|
111
74
|
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
- The target starts locally
|
|
115
|
-
|
|
116
|
-
- The runtime report covers local startup,
|
|
117
|
-
resolved Fimo connection, header translations, and integration
|
|
118
|
-
|
|
119
|
-
- With a browser
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
`fimo publish inspect <id> --json
|
|
128
|
-
|
|
129
|
-
unavailable after the deployment is reclaimed.
|
|
130
|
-
- When an approved preview deploy fails, capture `fimo logs --json` before
|
|
131
|
-
replacing or retrying the sandbox. Repair from that evidence, then make one
|
|
132
|
-
bounded retry.
|
|
75
|
+
The runtime lane owns these; the gate checks them read-only.
|
|
76
|
+
|
|
77
|
+
- The target starts locally without startup errors. Fimo Preview renders it in
|
|
78
|
+
Studio, and Edit Mode works.
|
|
79
|
+
- The runtime report covers local startup, Preview embedding, build, the
|
|
80
|
+
resolved Fimo connection, header translations, and integration key names,
|
|
81
|
+
each with evidence.
|
|
82
|
+
- With a browser, record `browserProof` (rendered route and console state) for
|
|
83
|
+
startup, Studio embedding, and Edit Mode. Without one, use deterministic
|
|
84
|
+
HTTP, header, process, and log checks and mark visual proof unavailable.
|
|
85
|
+
- A linked Next.js target needs no Fimo env file: `FimoProvider` resolves the
|
|
86
|
+
connection from `.fimo/project.json` and the git branch.
|
|
87
|
+
- A deploy is never a QA step; deployment smoke needs the owner's opt-in.
|
|
88
|
+
- When an approved preview deploy fails, run `fimo logs --json` before you
|
|
89
|
+
retry, then make one bounded retry. When an approved publish fails, run
|
|
90
|
+
`fimo publish inspect <id> --json` and `fimo publish logs <id> --json`
|
|
91
|
+
first.
|
|
133
92
|
|
|
134
93
|
## Behavior
|
|
135
94
|
|
|
136
|
-
- Dependencies are installed
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
landmarks, and the target has exactly one app tree.
|
|
145
|
-
- Collection listing/detail pages work with imported data, seed data, or explicit
|
|
95
|
+
- Dependencies are installed. The recorded CLI and companion package pins
|
|
96
|
+
work outside the local package cache and match the runtime channel.
|
|
97
|
+
- The project builds, and local dev starts without loader, schema, or form
|
|
98
|
+
generation errors. Main routes render without console or runtime errors.
|
|
99
|
+
- In conversion mode, each route in the worker's route map renders locally
|
|
100
|
+
with the expected status (404 included) and its source text, and there is one
|
|
101
|
+
app tree.
|
|
102
|
+
- Collection listing and detail pages work with imported data or explicit
|
|
146
103
|
empty states.
|
|
147
|
-
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
- Missing integration secrets do not block these checks: build, dev, and route
|
|
158
|
-
render run with the integration inert, and the missing key is a recorded
|
|
159
|
-
follow-up.
|
|
160
|
-
- Unsupported app behavior is not hidden behind broken UI.
|
|
161
|
-
|
|
162
|
-
## Rendered guardrails (required)
|
|
163
|
-
|
|
164
|
-
Brand, legal, compliance, and navigation rules are proven on the final rendered
|
|
165
|
-
application, never by grepping the target source. Once copy moves into Fimo the
|
|
166
|
-
strings leave the repository: a source grep for a forbidden phrase passes
|
|
167
|
-
because nothing is there, and a grep for the brand name fails for the same
|
|
168
|
-
reason. Worker reports, manifests, and coverage tables are diagnostics; this
|
|
169
|
-
check is the acceptance evidence.
|
|
170
|
-
|
|
171
|
-
1. Before the validation wave, the coordinator writes the guardrail inventory to
|
|
172
|
-
`.fimo/migration/guardrails.json` for the deterministic checker. List every
|
|
173
|
-
route the migration must prove and every rule the source, owner, or accepted
|
|
174
|
-
scope imposes. Every rule includes `source`: the source page, file, or owner
|
|
175
|
-
decision that requires it. A rule without a citation is an invention, not a
|
|
176
|
-
recovered project guardrail.
|
|
177
|
-
- `required-text`: copy that must render, such as the brand name or a
|
|
178
|
-
legally required notice.
|
|
179
|
-
- `forbidden-text`: copy that must never render, such as an old brand name,
|
|
180
|
-
placeholder text, or a claim the owner withdrew.
|
|
181
|
-
- `required-link`: a link every page must carry, such as the privacy policy
|
|
182
|
-
or imprint.
|
|
183
|
-
- `links-resolve`: every internal link rendered on the inventoried routes
|
|
184
|
-
points at an inventoried route or an explicitly allowed path prefix.
|
|
185
|
-
- `editable-text` (required in every inventory): every visible body text node
|
|
186
|
-
sits inside an element a Fimo primitive renders, so an editor can change it
|
|
187
|
-
in Studio. A faithful port is not editable yet: text still typed in the code
|
|
188
|
-
shows "Nothing to edit". Move it to a label or a CMS field. List in `allow`
|
|
189
|
-
only the exact text the owner keeps in code, such as a brand glyph or a
|
|
190
|
-
legal line, and record why in the migration report. Assistive and hidden
|
|
191
|
-
text does not count.
|
|
192
|
-
|
|
193
|
-
Internal links are resolved against the final document URL and any
|
|
194
|
-
`<base href>`; query and fragment do not change route identity. An `allow`
|
|
195
|
-
prefix exempts a destination family deliberately outside the accepted scope.
|
|
196
|
-
|
|
197
|
-
Scope a rule with `routes` only when it is not global. When the source has
|
|
198
|
-
no rule of a kind (for example no legal page), say so in the migration
|
|
199
|
-
report rather than leaving the inventory thin without explanation.
|
|
200
|
-
|
|
201
|
-
```json
|
|
202
|
-
{
|
|
203
|
-
"routes": ["/", "/about", "/legal/privacy"],
|
|
204
|
-
"rules": [
|
|
205
|
-
{ "id": "brand-name", "kind": "required-text", "text": "<target brand>", "source": "<source page or file>" },
|
|
206
|
-
{
|
|
207
|
-
"id": "no-old-brand",
|
|
208
|
-
"kind": "forbidden-text",
|
|
209
|
-
"text": ["<previous brand>", "Lorem ipsum"],
|
|
210
|
-
"source": "<owner decision>"
|
|
211
|
-
},
|
|
212
|
-
{ "id": "footer-privacy", "kind": "required-link", "href": "/legal/privacy", "source": "<source navigation>" },
|
|
213
|
-
{ "id": "nav-resolves", "kind": "links-resolve", "allow": ["/blog"], "source": "<source navigation>" },
|
|
214
|
-
{ "id": "editable-text", "kind": "editable-text", "allow": [], "source": "Fimo: visitors' text is editable" }
|
|
215
|
-
]
|
|
216
|
-
}
|
|
217
|
-
```
|
|
218
|
-
|
|
219
|
-
2. The validator observes the rendered application, not files in the
|
|
220
|
-
repository, with Fimo editing metadata on: build and serve with
|
|
221
|
-
`FIMO_EDITING_METADATA=true`, or observe the dev server. Without it no text is
|
|
222
|
-
marked editable and `editable-text` fails as unmeasured. For a
|
|
223
|
-
server-rendered target, run the check with `--base-url` while the app serves
|
|
224
|
-
locally. For a client-rendered target, save each
|
|
225
|
-
hydrated document from the browser pass as `<captures>/index.html` and
|
|
226
|
-
`<captures>/<route>.html` and pass `--captures`. Save a JSON sidecar next to
|
|
227
|
-
each HTML file, such as `index.html.json` or `legal/privacy.html.json`:
|
|
228
|
-
|
|
229
|
-
```json
|
|
230
|
-
{ "status": 200, "url": "http://localhost:3000/legal/privacy", "error": null }
|
|
231
|
-
```
|
|
232
|
-
|
|
233
|
-
Record the actual final navigation response status and document URL,
|
|
234
|
-
including its trailing slash. Record navigation or capture failures in
|
|
235
|
-
`error`; never infer a successful status from HTML or fill in missing
|
|
236
|
-
evidence. Missing, malformed, non-200, or error metadata fails the route.
|
|
237
|
-
Captures are supplied evidence: the checker cannot authenticate them or
|
|
238
|
-
recognize every error page served with status 200. The browser smoke below
|
|
239
|
-
must still prove representative content and working controls.
|
|
240
|
-
|
|
241
|
-
Count visitor-visible body text and readable attributes (`alt`, `title`,
|
|
242
|
-
`aria-label`, `placeholder`, and `meta` content); script, style, and comment
|
|
243
|
-
strings do not count.
|
|
244
|
-
|
|
245
|
-
```bash
|
|
246
|
-
node node_modules/fimo/assets/skills/fimo-migration/scripts/check-rendered-guardrails.mjs <target> \
|
|
247
|
-
--base-url http://localhost:3000 --output .fimo/migration/guardrails-report.md
|
|
248
|
-
```
|
|
249
|
-
|
|
250
|
-
3. The check fails closed and caps the gate at `draft-only` when the inventory
|
|
251
|
-
or rendered evidence is empty, a route is missing or non-200, a final URL
|
|
252
|
-
does not match the inventoried route, or a rule observes nothing. Nothing
|
|
253
|
-
observed is failed, never passed.
|
|
254
|
-
|
|
255
|
-
4. Copy the emitted `## Guardrails` block unchanged into the validator's
|
|
256
|
-
worker report and the migration report. Acceptance is `Result: passed` with
|
|
257
|
-
every inventoried route rendered and every rule observed on at least one
|
|
258
|
-
route. Each failure names the route and the phrase or link involved, so the
|
|
259
|
-
repair owner needs no rerun to locate it.
|
|
260
|
-
|
|
261
|
-
## Browser smoke (required)
|
|
262
|
-
|
|
263
|
-
Build success and HTTP 200 responses are not sufficient evidence: a page can
|
|
264
|
-
build, return 200, and still render blank labels or an empty collection. Run
|
|
265
|
-
one bounded, scriptable browser pass (Playwright, agent-browser, or
|
|
266
|
-
equivalent):
|
|
267
|
-
|
|
268
|
-
1. Start the app and wait for hydration, not just the HTTP response.
|
|
269
|
-
Do not use `networkidle` against dev/HMR servers; wait for expected visible
|
|
270
|
-
content and image readiness.
|
|
271
|
-
2. Open a representative set of pages: home, one collection listing, one
|
|
272
|
-
collection detail, one static page.
|
|
273
|
-
3. Exercise one representative interaction (open the nav menu, an accordion,
|
|
274
|
-
or a filter) and assert its visible result.
|
|
275
|
-
4. Assert expected visible text on each opened page and at least one dynamic
|
|
276
|
-
collection item rendered from imported Fimo data.
|
|
277
|
-
5. Assert globally rendered label/button text (header/footer nav, CTAs, cookie
|
|
278
|
-
banner) is non-empty; blank text usually means the component is mounted
|
|
279
|
-
outside the label provider.
|
|
280
|
-
6. Assert visible text and attributes contain no source-absent serialization
|
|
281
|
-
sentinels such as `undefined`, `null`, `[object Object]`, or `NaN`.
|
|
282
|
-
7. Inspect the browser console and server output for runtime errors.
|
|
283
|
-
|
|
284
|
-
Keep it bounded: representative pages and one interaction, not an interactive
|
|
285
|
-
walk of every route or a multi-hour visual audit. The Visual section below
|
|
286
|
-
remains a separate spot check.
|
|
287
|
-
|
|
288
|
-
## Visual
|
|
289
|
-
|
|
290
|
-
Visual checks need a browser. When none is available, run the deterministic
|
|
291
|
-
Hosting checks instead and mark visual proof explicitly unavailable in the
|
|
292
|
-
report; never claim a visual check that did not run.
|
|
293
|
-
|
|
294
|
-
- Compare source and migrated site at desktop and mobile sizes.
|
|
295
|
-
- Prioritize layout, typography, content hierarchy, media, and brand tokens.
|
|
296
|
-
- Remove generated placeholder copy from visible UI.
|
|
297
|
-
- Verify media aspect ratios and no broken images on primary routes.
|
|
298
|
-
- Compare representative component bounds; whole-page height can hide a local
|
|
299
|
-
geometry regression.
|
|
300
|
-
- Compare image loading before and after scroll. Record eager/lazy and preload
|
|
301
|
-
counts, response formats, and representative transfer sizes; an optimizer
|
|
302
|
-
URL alone is not delivery proof.
|
|
303
|
-
|
|
304
|
-
## Import Verification
|
|
305
|
-
|
|
306
|
-
Record:
|
|
307
|
-
|
|
308
|
-
- schemas pushed
|
|
309
|
-
- entries created/updated per content type
|
|
310
|
-
- media uploaded/failed
|
|
311
|
-
- forms pushed
|
|
312
|
-
- redirects/locales imported or unresolved
|
|
313
|
-
- the exact CLI used for the run, recorded in the report's Source section (see
|
|
314
|
-
"CLI provenance" in `SKILL.md`)
|
|
315
|
-
|
|
316
|
-
Counts belong in `.fimo/migration/migration-report.md` and the relevant worker
|
|
317
|
-
reports. Do not create a JSON QA registry just to store them.
|
|
318
|
-
|
|
319
|
-
Media, entries, and forms are blocking checks. Entries generated as seed JSON but
|
|
320
|
-
not created in Fimo, and media bundled under `public/` but not uploaded to the
|
|
321
|
-
Fimo media library, are NOT covered: the gate fails to `draft-only` unless each
|
|
322
|
-
gap has an explicit, owner-visible unresolved item. The bundled report script
|
|
323
|
-
enforces this - `cms-counts` requires imported (or skipped/unresolved) entries,
|
|
324
|
-
`schemas-pushed` requires the content type registered, and `media-covered`
|
|
325
|
-
requires a Fimo asset id/URL.
|
|
326
|
-
|
|
327
|
-
## Report
|
|
328
|
-
|
|
329
|
-
Write `.fimo/migration/migration-report.md` with:
|
|
330
|
-
|
|
331
|
-
```md
|
|
332
|
-
# Migration Report
|
|
333
|
-
|
|
334
|
-
## Status
|
|
335
|
-
|
|
336
|
-
complete | complete-with-unresolved | draft-only
|
|
337
|
-
|
|
338
|
-
## Source
|
|
339
|
-
|
|
340
|
-
## Coverage by dimension
|
|
341
|
-
|
|
342
|
-
## Routes
|
|
343
|
-
|
|
344
|
-
## Content
|
|
345
|
-
|
|
346
|
-
## Media
|
|
347
|
-
|
|
348
|
-
## Forms
|
|
349
|
-
|
|
350
|
-
## SEO and OG
|
|
351
|
-
|
|
352
|
-
## Redirects and Headers
|
|
353
|
-
|
|
354
|
-
## Integrations
|
|
355
|
-
|
|
356
|
-
## Hosting
|
|
357
|
-
|
|
358
|
-
## Content Delivery
|
|
359
|
-
|
|
360
|
-
## Guardrails
|
|
361
|
-
|
|
362
|
-
## Timing
|
|
363
|
-
|
|
364
|
-
## Checks
|
|
365
|
-
|
|
366
|
-
## Unresolved
|
|
367
|
-
|
|
368
|
-
## Next Actions
|
|
369
|
-
```
|
|
370
|
-
|
|
371
|
-
`Coverage by dimension` is one row per migration surface (routes, content,
|
|
372
|
-
forms, SEO/OG, redirects/headers, integrations, hosting, media, labels, and
|
|
373
|
-
locales) with `gate`,
|
|
374
|
-
`discovered`, `migrated`, `verified`, `unresolved`, `unsupported`,
|
|
375
|
-
`denominator`, and `coverage`. Never collapse it into a single score: full route
|
|
376
|
-
coverage must not average away a missing entry or an unuploaded asset. Timing is
|
|
377
|
-
a separate section copied from the worker reports, so it never dilutes coverage.
|
|
378
|
-
|
|
379
|
-
`Guardrails` is the unmodified block emitted by
|
|
380
|
-
`scripts/check-rendered-guardrails.mjs`. A report without it, or with
|
|
381
|
-
`Result: failed`, cannot be `complete` or `complete-with-unresolved`.
|
|
382
|
-
|
|
383
|
-
Cache freshness is a report check whenever migration changes the content
|
|
384
|
-
transport or rendering mode. Do not fail a migration for omitted provider cache
|
|
385
|
-
mechanics alone, but do fail stale Fimo edits caused by the target's migrated
|
|
386
|
-
read path.
|
|
387
|
-
|
|
388
|
-
Use `complete` only when all required checks pass. Use
|
|
389
|
-
`complete-with-unresolved` when the migrated site is usable and all gaps are
|
|
390
|
-
owner-visible. Use `draft-only` when import or verification has not happened.
|
|
391
|
-
|
|
392
|
-
Write the report directly as text. A later evaluator may calculate the table
|
|
393
|
-
from it, but the migration does not need a manifest or report-generation
|
|
394
|
-
registry to run.
|
|
104
|
+
- Each content-code batch moved at least one non-empty imported item across
|
|
105
|
+
each Server-to-Client or plain-JSON boundary; a build over empty data fails.
|
|
106
|
+
- Server-rendered content is in the first server response and is not fetched
|
|
107
|
+
again after hydration.
|
|
108
|
+
- Navigation and footer links go to migrated routes or recorded external URLs.
|
|
109
|
+
`links-resolve` checks internal routes; the validator checks external
|
|
110
|
+
destinations separately.
|
|
111
|
+
- A missing integration secret blocks no local check: build, dev, and render
|
|
112
|
+
run with the integration inert, and the key is a follow-up.
|
|
113
|
+
- Unsupported behavior is not hidden behind broken UI.
|