rollout — скилл для Claude Code: деплой всего сайта в AEM
Скилл rollout разворачивает целиком мигрированный сайт в AEM Edge Delivery Services за один прогон. Инвентаризирует дерево страниц, дедуплицирует блоки, запускает deploy на каждую страницу и отслеживает, что развёрнуто, а что осталось.
Apache-2.0 318 установок ★ 335 обновлён 2026-11-14
npx skills add adobe/skills --skill rollout -a claude-codeЧто делает rollout
Скилл строит реестр всех страниц из stardust/migrated/, сворачивает повторяющиеся блоки в единый набор и гонит deploy по очереди на каждую. Трекает статус каждой страницы: доставлено, устарело, ждёт контент. Работает в двух режимах: полный (все страницы мигрированы) и только архетипы (когда мигрированы шаблоны, а остальное регистрируется как content-pending и разворачивается позже).
Требует Node 22+, Playwright с Chromium в PATH и установленный скилл impeccable из того же репозитория. Без скаффолдинга проекта EDS/AEM, DA_TOKEN и пушабельной ветки код не запустится. Поддерживает режим hands-off: все фазы выполняются автоматом, без пауз между ними, но валидация и гейты работают как обычно.
В режиме gated-archetype (flow: replica) архетип типа страницы должен пройти гейт на всех заданных breakpoint, прежде чем его страницы можно публиковать. Архетип, который не гейтился или превысил порог без записанных residual, блокирует весь тип: скилл выведет команду для запуска гейта и не тронет ни одну страницу этого типа.
Какие задачи решает
- развернуть весь мигрированный сайт в AEM за один запуск
- отследить, какие страницы уже задеплоены, а какие нет
- дедуплицировать блоки перед конверсией
- зарегистрировать страницы как content-pending и задеплоить код блоков без полной миграции контента
- возобновить деплой с того места, где остановился
Примеры запросов агенту
- Разверни весь сайт в AEM — инвентаризируй страницы из
stardust/migrated/и запусти деплой на каждую - Построй coverage и план деплоя для всех страниц
- Задеплой только архетипы, остальное зарегистрируй как content-pending
Как установить rollout
1Через Skills CLI (Vercel)
npx skills add adobe/skills --skill rollout -a claude-code2Вручную: положить файлы
~/.claude/skills/rollout/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/rollout/
1Через Skills CLI (Vercel)
npx skills add adobe/skills --skill rollout -a codex2Вручную: положить файлы
.agents/skills/rollout/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add adobe/skills --skill rollout -a cursor2Вручную: положить файлы
.cursor/skills/rollout/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install adobe/skills plugins/stardust/skills/rollout2Вручную: положить файлы
.github/skills/rollout/SKILL.md1Через Skills CLI (Vercel)
npx skills add adobe/skills --skill rollout -a gemini-cli2Командой платформы
gemini skills install https://github.com/adobe/skills --path plugins/stardust/skills/rolloutВручную: положить файлы
.devin/skills/rollout/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add adobe/skills --skill rollout -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о rollout
Как установить rollout в Claude Code?
Выполни npx skills add adobe/skills --skill rollout -a claude-code, затем открой ~/.claude/skills/rollout/SKILL.md.
Что делает rollout?
Разворачивает целиком мигрированный сайт в AEM Edge Delivery Services, инвентаризируя дерево страниц, дедуплицируя блоки и запуская deploy на каждую страницу с отслеживанием статуса.
Что нужно для работы rollout?
Node 22+, Playwright с Chromium в PATH, скилл impeccable из того же репозитория, готовый проект EDS/AEM с DA_TOKEN и пушабельной веткой, а также дерево stardust/migrated/ хотя бы с одной страницей.
Исходный текст
SKILL.md · Apache-2.0
---
name: rollout
description: Deploy a WHOLE redesigned site to AEM Edge Delivery Services — the full-site, bulk sibling of `deploy` (which ships one page). Use to roll out, bulk-deploy, or publish an entire migrated stardust site at once ("deploy all pages", "full site deployment", "deploy the whole/entire website to AEM"), not just a single page. Inventories the migrated tree (stardust/migrated/ + _meta.json) into a delivery ledger, dedups blocks, drives `deploy` per page, verifies, and tracks what's done and what's left. Supports archetypes-only mode — when only the template archetype pages are migrated, it deploys all block code immediately and registers the rest as content-pending.
license: Apache-2.0
compatibility: Requires Node 22+, Playwright with Chromium resolvable from the project, and the impeccable skill (github.com/pbakaus/impeccable) installed alongside stardust.
---
# stardust:rollout — whole site → AEM (Edge Delivery Services)
`deploy` converts **one** page to AEM. `rollout` delivers the **whole site**: it
inventories the agnostic output of `migrate`, then drives `deploy` across every
page, tracking delivery coverage so you always know what's done and what's left.
`rollout` is **delivery-only** — it does not redesign. The page-by-page redesign
(`extract → direct → prototype → migrate`) and `deploy` itself are **unchanged**;
`rollout` is the across-pages layer on top. Design rationale, coverage model, and
phasing are in [`notes/rollout/PLAN.md`](../../notes/rollout/PLAN.md). The flow
runs **A→I** below.
## When to use
**Full mode** — the user has a fully migrated site at `stardust/migrated/`
(per-page HTML + `_meta.json` from `stardust migrate`), an EDS/AEM project + DA
destination (the same target `deploy` needs), and wants the **entire** site
delivered, incrementally and resumably.
**Archetypes-only mode** — the user has one migrated archetype per template plus a
full page inventory in `stardust/state.json` (with `type` per page), and wants to
ship all block code immediately without waiting for every page to be migrated.
Sibling pages register as `content-pending` and get their content later via a
separate track.
If there is no `stardust/migrated/` tree at all, recommend `stardust migrate` on at
least the archetype pages first. For a single page, use `stardust deploy` directly.
## Setup
1. Run the master skill's setup (`skills/stardust/SKILL.md` § Setup). **Flow
guard:** `stardust/state.json` without `flow` on a migration ask → do not
roll out; print the master's two-flow table and hand back to its routing
(`skills/stardust/reference/state-machine.md` § Flow keys).
2. Verify `stardust/migrated/` exists with at least one `*.html` page (full mode:
all pages; archetypes-only: the archetypes + a `state.json` with `type`
populated). If not, recommend `stardust migrate` on the archetypes and stop.
**Gated-archetype precondition (`flow: replica`).** Read
`stardust/replica/progress.json`: a page type may ship only when its
archetype has a gate result at every configured breakpoint that is
`pass: true`, or over the bar with every residual carrying a `cause`
(`skills/replica/reference/source-fidelity-gate.md` § Residual logging
format — a documented residual is a pass with an asterisk). A page type
whose archetype was never gated, or is over the bar with no residual
entries, is **blocked**: list it with its archetype slug and the command
to gate it (`$stardust replica <archetype>`), and neither fan out its
siblings nor `POST /live/` any of them. Accepting logged residuals under
hands-off is not a bypass for an ungated archetype. Thresholds are the
gate's, unchanged. (Recorded: 2,207 pages published at 24–28 % diff from
an archetype that never passed; a 3,366-page re-import after a random
review found what a gate would have.)
3. Verify the EDS/AEM target is ready exactly as `deploy` requires (project
scaffolding, `DA_TOKEN`, code branch pushable). `rollout` adds no new transport.
4. If `state.json.handsOff` is true (`skills/stardust/SKILL.md` § Hands-off
mode), run full-auto: no per-phase pauses. Every gate and verify step below
runs unchanged — hands-off removes waiting, not validation.
## Procedure
### Phase A — Inventory (build the coverage)
```bash
node skills/rollout/scripts/inventory.mjs --site-url <source-url>
# defaults: --migrated stardust/migrated --out stardust/rollout
# archetypes-only mode: add the full page roster from state.json
node skills/rollout/scripts/inventory.mjs --site-url <source-url> --state stardust/state.json
```
Writes `coverage/pages.json` (one row per page: slug, delivered `path`,
`templateId`, `blocks`, `sourceHash`, `delivery` status), `coverage/templates.json`
(pages grouped by template), and `rollout.json` (target + DA config + `lastRun`).
**Archetypes-only mode** (`--state`): pages with a `_meta.json` are seeded as in
full mode; pages present only in `state.json` are seeded with `templateId` from
`type`, `blocks` from the archetype sidecar, and `delivery.status:
content-pending`.
Inventory is **idempotent and incremental**: delivery status is preserved; a page
whose migrated HTML changed after delivery is re-flagged `stale` (never a
pinned row: replica's first page first). Fill in the DA
coordinates in `rollout.json` (`site.da.org`, `site.site`, `site.da.ref`,
`site.liveHost`) if not inferred.
### Phase B — Block dedup plan (FIRST-CLASS, before any conversion)
```bash
node skills/rollout/scripts/blocks.mjs # → coverage/blocks.json (the dedup unit)
node skills/rollout/scripts/plan.mjs # → plan.json + a readable conversion plan
```
- `blocks.mjs` collapses every block instance (per-page `modules`, `widgets` + chrome)
into the **distinct** set, assigns each a canonical `edsBlockName` (kebab, reserved-class
guarded) and records `usedByPages` / `instanceCount`. Chrome (`header`/`nav`/`footer`)
is `kind: chrome` → site-wide authored documents (`/nav`, `/footer`). A widget
(`kind: widget`, from the sidecar's `widgets[] {id, href}`) needs no document rows:
its code ships at `widgets/<path>/<name>.html` and the page carries one
`/widgets/…html` link (#133). In archetypes-only mode the archetype sidecars
determine the block set; `content-pending` pages add none. A module that maps to
EDS **default content** (title, text, image, button, separator) needs no block: record
it `update-coverage.mjs --block <id> --status converted --eds-name default-content`;
such a row is never counted pending, whatever its status.
- `plan.mjs` orders pages **representative-first per template** and gives each
distinct block a **single conversion point**: the first page that uses it
CONVERTS it, every later page REUSES it by name. The per-page `convert`/`reuse`
lists are `deploy`'s Step-7 brief input. `content-pending` pages are always `convert: []`.
> Extending a delivered site: audit `blocks/` and `widgets/` first — a "new template" is
> usually a new composition of them (`reference/operational-learnings.md`).
### Phase B2 — Dynamic surface (PRE-IMPORT GATE — verify the inventory)
**Before Phase C.** `stardust/dynamic-features.md` (from prepare-migration 4.5 or replica
Phase 2) must exist with a disposition on every row; verify it against fresh evidence here —
`dynamics-detect.mjs --from-state … --reach stardust/current` and `dynamics-plan.mjs
--target-origin <live host> --migrated stardust/migrated` (host-bound APIs, rows the capture
already delivered). New evidence → new rows. The listings contract (per-type `<meta>` fields +
`helix-query.yaml`) is emitted by Phase C's `deploy` brief per page: retrofitting metadata across
published pages is a second migration. Missing inventory → run the stardust `dynamics` skill Phases 1–3 now.
Contract: `skills/dynamics/reference/triage.md`, `reference/listings.md`.
### Phase C — Deliver the site (drive `deploy` per page, per the plan)
**Blocked on Phase B2** — author each page's metadata contract into its metadata
block during delivery, so the indexes are rich at import time.
Walk `plan.json.steps` in order (representative pages first). For each page:
1. **Convert + push** the migrated HTML (`source.migratedHtml`) to AEM via the
`deploy` methodology. **Pass the plan step into deploy's brief**: create only the
blocks in `convert`; for each block in `reuse`, REUSE the existing block by its
`edsBlockName` (do not recreate). **The brief MUST carry the Experience Workspace
editability contract** (deploy SKILL.md § 8, EW1–EW10): every converted block
moves authored elements into wrappers (never rebuilds from text) and passes the
EW gate (`block-roundtrip --ew`) before it counts as delivered — a brief without
it skipped the contract on 27/27 blocks of a real site. **The brief also carries
the archetype's `captureState[].restoreAtDelivery` list** (replica `progress.json`):
a freeze the gate needed (video at frame 0, carousel on slide 1) is a behaviour to
deliver, never the spec (`../replica/reference/recreation-procedure.md § Carousels`).
**Deploy first, judge on the preview origin.** The local harness
(`build-harness.mjs` → `qa-gate.mjs`, `block-roundtrip.mjs --ew`) serves the
structural asserts only; every pixel or visual judgment — replica's
source-fidelity gate, the header/footer `crop-compare` bands, the deployed
eyeball — runs against the page's preview URL after `PUT → preview`, never
against the harness before the first PUT (deploy SKILL.md § Local QA before
deploy, § Step 10). A recorded delivery session iterated CSS against a local
harness pixel diff for its whole budget and delivered no page.
**Chrome and fragment documents carry `Robots | noindex`.** `content/nav.html`,
`content/footer.html`, every per-locale `nav-*` / `footer-*` document and any
locale shell that is not a page get one more metadata block row at write time —
`<div><div>Robots</div><div>noindex</div></div>` (renders
`<meta name="robots" content="noindex">`). Without it the platform's index of
published documents, and the `/sitemap.xml` it serves, list them as pages: a
recorded hands-off run served 58 sitemap urls for a 36-page site (every page
plus 22 chrome documents). Phase D verifies the served sitemap.
**`content-pending` pages** (archetypes-only): no migrated HTML — skip the
document push entirely (no shell/placeholder), record `content-pending`, surface
as "awaiting content track." Their block code is already deployed via the
archetype.
2. **Static contract lint (pre-PUT, deterministic).** Before the push, run the
delivery-contract linter — it catches the cheap, deterministic failures
(wrapper, one-CTA-per-`<p>`, trailing-slash, path-safety, `/img/` src,
`about:error`) offline so a broken page never reaches preview. Mechanics in
`reference/delivery-lint.md`. **A P0/P1 blocks the PUT.**
```bash
node skills/rollout/scripts/delivery-lint.mjs --file <html> --path </da/path>
node skills/rollout/scripts/media-reconcile.mjs --file <html> --deploy-host <branch>--<repo>--<owner>.aem.live [--media-ledger <file>] [--apply]
```
`media-reconcile` resolves every non-hosted image on the network and decides
optimize/keep/rewrite/omit (`skills/migrate/reference/media-reconciliation.md`)
— the authoritative form of the image-fidelity gate below. A content-host URL
(`content.da.live`) is the `hosted` decision instead: checked offline against the
media ledger (`--media-ledger <file>`, auto-detected), never fetched anonymously
(`401` by design); missing from the ledger fails the gate.
3. **Run the delivery gates** before flipping a page to `deployed`. Each is a
one-line rule here; mechanics + helpers in `reference/delivery-gates.md`:
- **Source-fidelity** — don't add sections the source lacks; never fabricate
facts. `node skills/rollout/scripts/section-fidelity.mjs --file <html> --source <url>`
(a static outline check on the authored file — not replica's pixel
source-fidelity gate, which runs on the published origin after `deployed`)
- **Image-fidelity** — every authored `<img>` src must return 200 or be omitted;
never ship `<img src="about:error">`. Run `media-reconcile.mjs` (step 2).
- **Path-safety** — `reference/delivery-gates.md` § Gate 3; record
original→normalized in `stardust/redirects.tsv`. (delivery-lint flags violations.)
- **Source-content hygiene** — skip dead source URLs; author bodyless/PDF-only
sources thin and faithful (tier `thin`,
`skills/migrate/reference/fidelity-tiers.md`), don't pad with invented prose.
- **Fidelity tier declared** — record each page's `fidelityTier`
(archetype/sibling/thin) so coverage shows what was craft-gated vs cloned
(`skills/migrate/reference/fidelity-tiers.md`).
4. **Record outcomes** with the state-writer (never hand-edit the ledger):
```bash
node skills/rollout/scripts/update-coverage.mjs <slug> --status converting
node skills/rollout/scripts/update-coverage.mjs --block <id> --status converted --eds-name <name>
node skills/rollout/scripts/update-coverage.mjs --block <id> --status converted --eds-name default-content # maps to default content, no block
node skills/rollout/scripts/update-coverage.mjs <slug> --status deployed --url <branch-preview-url>
node skills/rollout/scripts/update-coverage.mjs <slug> --status content-pending # no document push
```
**Publish in the loop (`PUT → preview → live`), don't stop at preview** — any
query-index (Phase D2) builds from the **live** tree, so a preview-only delivery
leaves indexes empty. On failure: `--status failed --error "<reason>"` and
continue (one page's failure never aborts the rollout).
**Foundation-first gate (hard block, once per rollout).** When the FIRST
archetype page flips to `deployed`, stop and prove the foundation before
authoring any second page: run the stardust `diff` skill (both probes) against its
prototype, **plus computed-style invariants in a headless render** — grid
containers compute `display: grid` (not stacked single-column), sections are
full-bleed where the design says so, and the CTA/button classes are actually
styled (per `stardust/runtime-contract.json`, `skills/deploy/SKILL.md`
§ Runtime-detection probe). `deployed` means after PUT + preview: the gate's
probes run against the page's preview URL, never a local harness — a
pre-deploy harness pixel diff is NOT this gate. A wrong runtime assumption (block wrapper class,
button classes) is silent and sitewide — typography still looks fine while
every grid stacks. This one gate is the difference between fixing one page
and rebuilding every template. The same gate runs `qa.mjs --checks metadata`
against the origin: `favicon-default` means the site's icon never shipped
(deploy Step 3 § Favicon) — recorded first passes served the boilerplate
icon while `/favicon.ico` answered 200. **Archetype first, per template (#126):** the
template's archetype is deployed and passes its full gate row on the preview URL
(`gate-all.mjs --only`, cap 3 fix rounds) before any of its siblings is rendered
or converted — the recorded unit `C-archetype` (handoff contract § 3, row C).
**Execution model: waves.** Deliver in waves of parallel **author-only** agents
— each agent curls its source pages and writes files only, never deploys or
edits blocks — template clusters concurrently (non-overlapping pages),
representative-first so blocks exist to be reused; then a **central deploy**
per page; then background batches with a per-page OK/FAIL ledger, re-driving
FAILs only. For clusters of 6–20+ siblings, the full flow is
`reference/delivery-gates.md` § Batched delivery (it also names the one
variant where cluster agents deploy themselves — replica's Phase 5 fan-out,
per-cluster deploy ledgers, lock-safe shared ledgers). The central deploy step
should run the bundled, resumable driver rather than a serial loop:
`node skills/deploy/scripts/deploy-batch.mjs --org <org> --repo <repo>
--branch <branch> --content <dir>` (concurrency pool, persistent ledger that skips
already-live pages, retry/backoff, append-only log, delivered-`.plain.html` check).
The driver and every batch run in the background; its log and ledger are the
progress file. Check them at most every 4 minutes and never with a fixed `sleep`
of 5 minutes or more (the prompt-cache window) — the master skill's wait
discipline; recorded batch waits of 9–10 minutes re-wrote a ~650k prefix each time.
After a transient blip, re-run the same command — it re-drives only the FAILs.
Then reconcile the ledger into coverage with `update-coverage.mjs`.
**Foundation first:** lint AND commit `styles.css`, header/footer CSS and the
contract file BEFORE the first agent spawns; no token or custom-property rename
after fan-out (a recorded rename under three running agents cost seven
coordination messages). **Disjoint clusters spawn concurrently** — a wave waits
only on a real dependency (a recorded second wave idled 14 min behind an
unrelated first). **Every tool call stays under 4 minutes, the main agent's
included** (the prompt cache holds 5; calls of 5.2 and 6.6 min re-wrote the whole
context, and so did one 338 s foreground turn on the main agent that ran a pixel
loop beside a deploy-batch start + wait): a long instrument (gate rounds, pixel
loops, Playwright captures, deploy batches) goes through `run-bg.mjs start`, and
`wait` is the NEXT tool call — it returns within its `--max` (100 s by default); never two long instruments
as parallel tool calls in one turn, never two `wait`s in one command.
### Phase D — Site assembly (whole-site artifacts)
```bash
node skills/rollout/scripts/assemble.mjs # → rollout/site/{sitemap.xml,robots.txt,manifest.json} — the EXPECTED set
node skills/rollout/scripts/assemble.mjs --verify-origin https://<branch>--<repo>--<owner>.aem.live # vs the SERVED /sitemap.xml; exit 1 on a mismatch
```
Generates site-wide artifacts: `sitemap.xml` + `robots.txt` from delivered paths,
and a fragments manifest mapping chrome blocks to the authored chrome documents
(`content/nav.html`, `content/footer.html`) with their `canon/*.html` source
(`deploy` authors + deploys the documents through the normal content chain —
they MUST be published or the chrome 404s sitewide).
**The assembled sitemap is never the served one.** `stardust/rollout/` is in
`.hlxignore`, so `site/sitemap.xml` is a local artifact — the EXPECTED url set.
The platform serves its own `/sitemap.xml`, built from its index of every
published document, chrome documents included unless each carries `Robots |
noindex` (Phase C). A recorded hands-off run read the local file, reported
"sitemap 36 urls" and shipped a served sitemap of 58 (36 pages + 22 `nav` /
`footer` documents). Two remedies, the first required:
- **Authoring:** every chrome/fragment document — `/nav`, `/footer`, per-locale
`nav-*` / `footer-*`, locale shells that are not pages — carries the metadata
row `Robots | noindex`; a document already published without it is re-authored
and re-published (preview → live) before the check below.
- **Configuration (alternative, additive):** when the code branch is writable, a
`helix-sitemap.yaml` at the project root (`sitemaps.default.include: ['/**']`,
`exclude: ['/nav', '/footer', '/**/nav*', '/**/footer*', '/fragments/**']`,
`properties.lastmod: lastModified`) keeps chrome out of the served sitemap even
when a document lacks the row; the same `exclude` globs go into
`helix-query.yaml` (Phase D2) so the index never carries them either.
**Verify the SERVED sitemap, never the local file.** `assemble.mjs --verify-origin
<live-origin>` compares the served `<loc>` paths with the coverage rows and
exits 1 on any difference. An extra
path is a chrome document without `noindex` or a page built outside the migrated
tree with no coverage row (`update-coverage.mjs --new`, Phase D2); a missing path
is a page not published live. Re-run after the fix until it exits 0. The `D-site`
ledger `end` line names the SERVED count, never the assembled one — e.g.
`--detail "sitemap served 36 = assembled 36; redirects wired; / 200"`.
**DA library (#160).** Without a `library` tab in its site config, a migrated
site shows authors an inherited or empty block library, never the blocks it
shipped. Run `node skills/rollout/scripts/da-library.mjs` (one document per block
variant and per template, the sheets, and only the Blocks / Templates config rows)
whenever a block, variant or template ships — in archetypes-only mode once the
archetypes are delivered.
**D-site checklist** (all before the `D-site end` line): `assemble.mjs
--verify-origin` exits 0 · every chrome document carries `Robots | noindex` and is
published · the redirects sheet is published (below) · `da-library.mjs` exits 0 ·
`curl -sIL <origin>/` ends in 200.
**Redirects:** if Phase C's path-safety gate emitted `stardust/redirects.tsv`, wire
it into the EDS redirects mechanism here so original inbound URLs don't 404 — the
redirects sheet at the content root (on a DA-backed site `/redirects.json`, columns
Source / Destination; PUT through the admin API, then preview + publish it like a
page). The root MUST answer: when the source root serves a page, deliver it as
the root `index` document (the pipeline serves `/` from it — `/index` ≡ `/`;
never also a `/` Source row, which would shadow it); only when the source root
itself redirects (`curl -sI <source-url>`, follow the Location chain) does the
sheet carry `/` and `/index.html` → the landing page. Then verify
`curl -sIL https://<branch>--<repo>--<owner>.aem.page/` ends in 200: a 404 on
`/` fails the whole delivery after every phase has passed (recorded — a sheet
with a row for every `.html` path and
none for `/`).
### Phase D2 — Dynamic features (`dynamics` Phases 4–5)
Implement the plan's reproducibility-`self` rows from the pattern catalogue
(`skills/dynamics/reference/patterns.md` — index-backed listings and search, modal loader,
media as URL, client-compute blocks, owner-facing tag config disabled, off-origin data tiers,
sheet sync); emit every other row as **one owner decision batch** and ship its interim tier.
Query indexes build from the **published** tree — publish per page in Phase C, then poll `total`.
Each feature ends with a parity row in `stardust/dynamics/parity.json` carrying a replayable check;
`dynamics-check.mjs --origin <live host>` runs before Phase H and the report carries its table.
Failed replays are `dynamic-gap` / `api-dependency` learnings, never silent passes.
Index-backed listings ship **document-first** (authored rows, index for non-text and top-up —
`dynamics/reference/listings.md`); the deploy AI-readability gate runs on every listing page.
**A missing query index is a code-branch gap, not a configuration-service problem.**
`/query-index.json` answering 404 means the project ships no `helix-query.yaml`. Author it
at the code branch root (a spec's `knowledge/helix-query.yaml` is the draft), publish the
pages LIVE and poll: `skills/dynamics/reference/listings.md` § Getting an index at all. A
403 from the configuration service is expected; only an unwritable code branch ships the
sheet-backed interim index (recorded `interim`, decision named).
**Search parity is count + titles, not presence.** The results block ranks title
matches first and consults description, then body text, only while fewer than N title
hits exist (N = the source's visible count for the probe term), dedupes by title +
description and caps the typeahead at N — N, the top titles and one known hit are read
from the SOURCE during detect and recorded on the `search-query` check (`expectCount`,
`expectTitles`, `expectIncludes`); `dynamics-check.mjs` fails the check on a count
mismatch (`skills/dynamics/reference/patterns.md` § search-index-backed).
**Pages built here enter coverage.** A results page (or any page without a capture)
has no inventory row, so it stays outside `verify.mjs --all`, `optimize.mjs` and the
assembled sitemap unless registered:
```bash
node skills/rollout/scripts/update-coverage.mjs --new search --path /search --template search --origin dynamics --title "Search"
```
then record its status like any page. `inventory.mjs` keeps such rows on a re-run (the
origin marker in `source.migratedHtml` identifies them; status untouched), so the line
runs once.
### Phase D3 — Multilingual (per-language trees) — optional
When the source has language trees (`/fr/…`, `/en/…`), add them as parallel content
trees that REUSE the same block library — only authored content and a little wiring
change (language-routed chrome documents, per-language indexes, per-language path-safety).
See `reference/multilingual.md`.
### Phase E — Full-site verify
```bash
node skills/rollout/scripts/verify.mjs # uses rollout.json site.liveHost
# or: --base <url> (explicit host) | --root <dir> (offline, against a local export)
```
For every delivered page, `verify` confirms HTTP 200, no `about:error` (deploy
#75), and that every internal `href="/…"` resolves to a known delivered path — then
flips each page to `verified` or `failed`. Exits non-zero if any page failed.
**Headless render check (per template).** A 200 `.plain.html` can still render
blank — decoration failures (missing script, wrong block wrapper class, 404
chrome) are invisible to a text check. On the FIRST delivered page of each
template (home included), load the live URL in a headless browser and assert
decoration ran: the runtime's `body.appear` class is set (per
`stardust/runtime-contract.json`), `main .section` count > 0,
zero `pageerror` events, zero broken images, and every `restoreAtDelivery`
entry of the template's archetype holds: an `autoplay` `<video>` at least a
quarter visible is playing (`!paused`, `currentTime` advancing — not merely
present), a rotating carousel advances without interaction.
**Published-origin gate over the roster (#125).** `verify` proves the pages render; the
DELIVERY verdict is replica's `gate-all.mjs` (pixel + height + clip + content per deployed page,
`../replica/reference/source-fidelity-gate.md` § The all-pages published-origin gate).
`update-coverage.mjs --gate stardust/replica/gates/all-<w>/summary.json` writes each row into
`delivery.gate` and flips a failing page to `failed`; `verify` never marks it `verified` while the
gate fails — completion derives from one place, never from the pixel number alone. In C-deliver
the roster run is the recorded unit `gate-all` (handoff contract § 3, row C).
### Phase E2 — Link-audit completeness
`verify.mjs` checks the links on delivered pages; this phase closes the set of
link **targets** a roster-driven batch misses
(`reference/operational-learnings.md` § Two verify checks):
- **Nav/footer/landing targets are NOT archetype siblings.** Enumerate every
`href` in the `/nav` + `/footer` documents plus each section's index/landing
page and confirm each is **deployed + published + verified** — and that the
chrome documents THEMSELVES are published — otherwise they get
committed but never published, their links 404, and the dashboard still
reads 100%.
- **Localize source-site bounce links** with the deploy stage, not by hand:
`node skills/deploy/scripts/localize-links.mjs --source-host <live-host>
--content content --redirects stardust/redirects.tsv` rewrites every
source-host href whose path exists in the content tree (header/footer/home
included) to the canonical root-relative form and lists the ones it kept
absolute (no local page — a bounce beats a 404). **Re-run over the WHOLE
tree after every wave**: earlier waves' pages gain newly valid targets only
when a later wave ships them. `--check` is the gate (exit 2 = localizable
links remain).
- **Link every internal page at its served URL** (`deploy/scripts/eds-path.mjs`):
no `.html`, a slash only on a folder index (`/x/`). `.html` and a leaf's
slash 404 while `.plain.html` passes. Repoint `.html` links with no local
page at the working source URL.
- **The audit GETs each href against the LIVE tree**: the ledger alone misses
slash and case defects.
- **Targets missing from the capture.** Two cases, both recorded in
`direction.md` as a named decision with the list: a target the direction's
caps meant to include is a CAPTURE GAP — crawl it first (capture → migrate →
gate, never authored from a live read) and deliver when the gap is ≤ 12
pages, else repoint to the source site and list it as scope debt; a target
outside the declared caps is SCOPE EXTENSION — repoint regardless of count.
External targets: repoint to the source site; other-locale targets: repoint
ONLY when that locale root was never captured. Any captured page — a `stardust/state.json` row, including
`duplicateOf` shells and locale roots — is in scope and is delivered, never
repointed (the ≤ 12 rule is for UNcaptured pages; a recorded run dropped ten
captured locale roots by citing it). Never leave a 404 (a recorded audit
found 10 uncaptured in-scope pages — delivering them was the right call).
### Phase F — Optimize: multi-source audit + gate (delivery quality)
The in-flow **quality gate**. optimize aggregates findings from **existing audit
skills** into one ledger (`optimize/findings.json` + `optimize/scorecard.json`),
tags each by **fixability**, and gates the rollout. Sources (full mapping in
`reference/audit-sources.md`):
1. **`rollout:baseline`** — built-in deterministic detectors:
```bash
node skills/rollout/scripts/optimize.mjs # uses rollout.json site.liveHost
# or: --base <url> | --root <dir> | --slug <s> | --all
```
2. **`impeccable:critique` + `impeccable:audit`** — design quality + a11y/perf.
3. **The marketing SEO skills** — `seo-audit`, `schema`, `ai-seo`,
`site-architecture`.
4. **`stardust:tensions`** — mechanical design tensions from
`sta...
© adobe · Apache-2.0 · adobe/skills