Redesign an existing website to make it better. Built on top of impeccable.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Everything the replica Phase 5 executor needs from the three sibling skills — rules, commands, exact ledger strings — so no sibling document is read whole. Paths are relative to this file.
For depth, fetch the cited section with node stardust/scripts/replica/section.mjs <doc> '<heading regex>', never the whole document: the § text of every citation is the heading (or its regex-safe leading words) and is passed verbatim as the regex.
Siblings inherit the archetype's source-fidelity gate; they re-check only what varies per page: content, media, the delivery contract (../../migrate/reference/fidelity-tiers.md § The three tiers). The reflex for "page N of a template" is fork the archetype, never re-author. Order (#126): a template's siblings render only after its archetype is LIVE and gated at the published origin (§ 3 row C, unit C-archetype) — the fork inherits a proven encoder, not a prototype; a recorded run migrated 78 siblings from unproven archetypes and re-deployed whole families after the fix program.
| # | Step | Rule | Source |
|---|---|---|---|
| 1 | Variance probe — once per template, BEFORE cloning | node stardust/scripts/replica/sibling-variance.mjs <archetype-live-url> <sibling-url>… --probe hero=<sel> --probe card=<sel> --width 1440 (pass the archetype's own block selectors; --headed on bot-managed sites). Exit 0 = clone as-is; exit 2 = deltas per sibling, each budgeted as a block VARIANT class on the sibling's content — never a per-page block fork. Keep the JSON next to the fan-out brief; list variants in _meta.json variants[]. | ../../migrate/reference/fidelity-tiers.md § Sibling variance probe |
| 2 | Structural clone (Path A′) — the ENCODER INPUT, never a gated prototype | Fork the archetype's structure, inject this page's typed slots, adapt only where content does not fit; canon chrome verbatim. The render is the slot-typed input of the template's encoder (the deploy convert step proven on the archetype); where it flattens a composition the encoder reads the hydrated capture stardust/current/pages/<slug>.html instead — the recorded run's encoders converged only from the capture. No local pixel number is taken on it. Declare in _meta.json: fidelityTier: "sibling", archetypeSource and template (both the archetype's slug — rollout groups by template; the archetype's own sidecar leaves it null and groups under its slug), modules[] (this page's block ids, on archetypes too — composite sections only; title, text, image, button and separator are default content — rollout's Phase B dedups from these; empty lists cost a session a hand census), widgets[] ({id, href} per a[data-widget] mount, derived by the driver) and gatesPassed[]. | ../../migrate/reference/migration-procedure.md § Three render branches; ../../migrate/SKILL.md § Phase 2 — Per-page render |
| 3 | Content fidelity | Verbatim: headings, body, paragraph boundaries (block-level nodes, never split on newlines), CTA labels + hrefs, nav labels, form fields, alt text, order. Transform only internal-link paths, asset paths, whitespace. Drop only tracking tags, consent banners, chat widgets, polyfills, empty sections. Every deviation → contentDeviations[] {kind, source, target, reason}. | ../../migrate/reference/content-preservation.md § Preserve verbatim; § Transform with rules; § Drop deliberately |
| 4 | Content-count acceptance — per page, at import time | Compare role-classified counts (headings, body/list nodes, CTAs + hrefs, images) between stardust/current/pages/<slug>.json (the reference — never a fresh live hit) and the rendered page. Any drop not covered by a logged contentDeviations[] entry fails the page: fix the importer/template, re-run. Record "content-count" in gatesPassed[]. Both sides renderable → node stardust/scripts/diff/content-diff.mjs <capture-url> <rendered-url> --profile generic --main <root>; pass = looks-same 🔴 0 · nothing-lost 🟡 0 on its Tiers: line (source-fidelity-gate.md § Pass bar item 1). That command covers the main root AND the chrome roots (header, footer) on every gate page — the default, no chrome flag to add; the report has one block per root and every finding line names its root ([header]). content-diff also pairs placeholder / aria-label / title values and icons (small images by file name, inline svg, icon-font glyphs by ::before/::after content): a dropped placeholder on an interactive element, a wrong flag inside a locale link or an empty icon box inside a link is a structural 🔴 like a missing CTA; a dropped aria-label (anywhere), lost sr-only text or a heading flattened to body is a nothing-lost 🟡 that fails the page; a glyph-vs-svg technique swap, the same icon at another anchor (ICON MOVED — e.g. a text-less accordion button hosting the source's item glyph) and a missing title are 🟡. | ../../migrate/reference/fidelity-tiers.md § Content-count acceptance |
| 5 | Gate row — per sibling, both widths, AFTER PUT + preview (never before) | The sibling's first and only counting number is its row in the pixel table, in the published regime: the cluster subagent runs node stardust/scripts/replica/gate-all.mjs --only <slug,…> --eds-host <preview host> (and --width 360) over its pages; the bar is the archetype's (pixel ≤ 10 %, | Δh |
| 6 | Delivery lint — static, pre-PUT | node stardust/scripts/rollout/delivery-lint.mjs --file <html> --path </da/path>; any P0/P1 blocks the PUT (wrapper, one <h1>, one CTA per <p>, about:error, /img/ src, trailing slash / .html, path safety). | ../../rollout/reference/delivery-lint.md § Run it; § What it checks |
| 7 | Media reconcile — after lint, before PUT | node stardust/scripts/rollout/media-reconcile.mjs --file <html> --deploy-host <branch>--<repo>--<owner>.aem.live [--media-ledger <file>] [--apply]: optimize (same-origin) / keep (external 200, block skips createOptimizedPicture) / hosted (URL on the site's content host — content.da.live, admin.da.live — verified OFFLINE against stardust/deploy/media-ledger.json, auto-detected or --media-ledger <file>, never fetched anonymously: the host is auth-gated, an anonymous GET is 401 by design and says nothing about the image; a content-host URL absent from an existing ledger FAILS the gate — the uploader never recorded it; no ledger file → pass with a NOTE) / rewrite (?-delimiter, host) / omit (definitive 4xx, drop the <img>); unresolved (5xx/timeout) is never auto-deleted and holds the gate. The published-origin check — every visible image clientWidth > 0 (§ 2) — stays the real media gate; a recorded run skipped this row on every sibling because the anonymous 401 read as unresolved. | ../../migrate/reference/media-reconciliation.md § The decisions; § Run it |
| 8 | Validation | Strict (refuse to write): :root block first in the first <style>, required data-*, provenance first child of <head>, slots filled, colour reservations, well-formed _meta.json, no output-path collision. Soft (log): template shape, canon deviations, broken internal links. | ../../migrate/reference/migration-procedure.md § Validation |
| 9 | Driver | node stardust/scripts/migrate/migrate.mjs render <slug…|--all> [--archetype <slug>=<archetype>] [--branch-b a,b] [--force] does the mechanics of rows 1–4 and 6–8 per page (page map, URL-literal path, links, assets, <head>, strict validation, sidecar, idempotent skip; the gate row, row 5, is gate-all's after PUT); the judgments go on the sidecar with node stardust/scripts/migrate/migrate.mjs gate <slug> <gate> [--evidence <text>] and node stardust/scripts/migrate/migrate.mjs modules <slug> <id…> (also deviation, decision, variant). It never advances pages[].status — state.mjs advance does. The phase runs as RECORDED UNITS in stardust/migrate/progress.json (the C-deliver unit ledger's shape, § 3 row C; the per-unit order in § 5): one plan unit, one render unit per template cluster of at most ~8 siblings (migrate.mjs render <slug…> takes the cluster's slug list), one assets unit when media is rehosted here, one report unit (state-and-report) — a recorded run rendered 31 siblings through five parallel builders as ONE unit inside one session, the most expensive session of the run, with no resume point between the plan and the final report. | ../../migrate/scripts/migrate.mjs --help; ../../migrate/SKILL.md § Phase 2 — Per-page render (Recorded units) |
Acceptance: gatesPassed = ["variance-probe", "pixel-gate-1440", "pixel-gate-360", "delivery-lint", "media-reconcile", "content-fidelity", "content-count"] — the two pixel gates come from the page's row in gates/all-<w>/summary.json (published regime), so they are earned in C-deliver, never before; media-reconcile is required only once the page's delivered content/<path>.html exists (gate-evidence.mjs --content <dir>, default content); until then the sidecar reads n/a: no delivered content file yet and --check does not demand it — it is row 7 / row C's gate, not the prototype gate's; a page with an uncovered count drop or a strict failure stays out of migrated (../../migrate/reference/fidelity-tiers.md § Declaration; ../../migrate/SKILL.md § Phase 4 — State and report). Bodyless or PDF-only pages go tier thin with a declared contentGap, never padded (../../migrate/reference/fidelity-tiers.md § The three tiers). Any block JS written for a sibling obeys EW1–EW10 and passes block-roundtrip --ew before the page is done (../../migrate/reference/fidelity-tiers.md § Content-count acceptance, closing paragraph). stardust/scripts/replica/gate-evidence.mjs fills the measured gates — pixel-gate-<width> (withheld while the overflow assert fires), content-count, media-reconcile (once the delivered content file exists), delivery-lint and, for siblings, variance-probe — from the run-bg job state and logs plus an in-process delivery-lint run, each with a one-line gateEvidence pointer; content-fidelity stays the agent's declaration (migrate.mjs gate <slug> content-fidelity --evidence …) and is never written by the collector.
stardust/migrate/progress.json — the migrate unit ledger (row 9): the same shape as the C-deliver ledger (§ 3), written by the main agent when a unit starts (running) and when it ends (done / failed), always BEFORE the checkpoint commit — units.<name>: {status: pending|running|done|failed, kind: plan|render|assets|report, templates[], pages: n, startedAt, endedAt, verdict}. A render unit is named after its template cluster (<template>, or <template>-1, <template>-2 when a template has more than ~8 siblings); verdict is the driver's final rendered N, unchanged N, refused N, passthrough N line for that unit's slugs. Per unit, in this order: the progress.json write → the checkpoint commit → the next unit; a unit end is a safe resume point, never by itself a reason to end the session. A session resumed inside migrate reads the file and runs only the units not done; a unit left running re-renders its slugs — migrate.mjs is idempotent and skips unchanged pages, so the re-run costs only the pages the ended session never wrote.
Editability contract — node-slotting, never value-slotting (../../deploy/SKILL.md § Experience Workspace editability contract):
h1–h6 / p / ul / ol / pre / blockquote / picture / img with append()/prepend(); never rebuild from textContent/innerHTML, never cloneNode + discard, never retag, never .trim() displayed text; capture nextElementSibling before append()..headline :is(h2, h3)), never a class on it, never > / :first-child / :nth-child on the path to it.<p>. EW4 presentational clones get stripInstrumentation(). EW5 exempt text is declared @ew-exempt <reason> in the block JSDoc, never dropped. EW6 card-as-link unwraps the inner anchor after reading href. EW7 no <button>/<summary> hosts authored text. EW8 reabsorbed section heads move the wrapper's children. EW9 decorate() is re-entrant. EW10 default-content selectors follow the same rules.slot.textContent = cell.textContent, ${text} template interpolation — renders pixel-perfect and is 100 % uneditable (../../deploy/SKILL.md § Anti-patterns).Decode tier per section (../../deploy/SKILL.md § 2b. Section schema; record the tier in stardust/eds-conversion-log.md):
rows[N]; segment on the most frequent heading tag; consume every element type or end with a leftovers pass (../../deploy/SKILL.md § 8. Block JS scaffold).node stardust/scripts/deploy/section-schema.mjs <protoURL> --out stardust/eds-schema/<page>.json → write rows and decorate() from it → per block node stardust/scripts/deploy/block-roundtrip.mjs <protoURL> content/<page>.html --blocks <name> --ew exit 0 (0 structural 🔴, 0 DEAD TEXT / DROPPED CONTENT / DUPLICATED INDEX) → one whole-page run without --blocks before any PUT (../../deploy/SKILL.md § Local QA before deploy).DA media protocol (../../deploy/SKILL.md § Images: editorial):
PUT https://admin.da.live/source/{org}/{repo}/media/<scope>/<file> — multipart, field name data, correct Content-Type; JPG/PNG/webp source only; SVG only if pure-vector and under ~40 KB. One command does the whole folder or manifest and prints the URL to author per file: DA_TOKEN=… node stardust/scripts/deploy/da-media-upload.mjs --org <org> --repo <repo> --scope <name> --dir stardust/current/assets/media (--scope is the folder UNDER media/, never media/<name> — the path would double and the script refuses it; § 4 table; never a hand-rolled PUT loop).<img src="https://content.da.live/{org}/{repo}/media/<scope>/<file>" alt="…"> in the cell; never /img/… in content, never imagery baked into block JS by index. Decorative = CSS only.content.da.live / admin.da.live URLs — a 401 there is normal and ingests fine. Verify post-preview only: delivered .plain.html has 0 about:error and the expected <img> + alt count (../../deploy/da-deploy-protocol.md § Deploy .DA Source API, step 3b).stardust/current/assets/media/); omit only on a true 404 after the rendition / ?-delimiter repairs; verify with an in-page fetch from a browser context of the tier _crawl-log.json#discovery.fetchTechnique names (chrome, chrome-escalated, chromium-fallback; older logs headed-chrome), never a bare curl.../../deploy/SKILL.md #161 — mp4 ≤ 36 MB via da-media-upload.mjs, authored root-relative; never its content.da.live URL.DA deploy protocol (../../deploy/SKILL.md § Deploy .DA Source API; ../../deploy/da-deploy-protocol.md § Deploy .DA Source API):
POST https://admin.hlx.page/code/$ORG/$REPO/$BRANCH/* → 202 and poll when edited blocks 404); host label <branch>--<repo>--<org> ≤ 63 chars; DA_TOKEN preflighted (JWT exp) and re-checked before each batch — a mid-batch 401 checkpoints the ledger and halts with one instruction, never fails pages red.localize-links.mjs --source-host <live-host> over the WHOLE tree, then --check exit 0 → davids-model-lint.mjs exit 0 → sanitise.js → PUT https://admin.da.live/source/<org>/<repo>/<path>.html (multipart data, type=text/html, expect 201) → POST https://admin.hlx.page/preview/<org>/<repo>/<branch>/<path> (200) → GET .plain.html: 200, <body> wrapper, one <h1>, 0 about:error, no /img/ → ai-readability.mjs code score ≥ 98 → computed-style guard once per template (grid/flex blocks compute grid/flex, main .section > 0, data-block-name present, 0 pageerror, every visible image clientWidth > 0) → only then deployed. Admin 200 ≠ delivered.PUT → preview → live; deploy-batch.mjs without --no-publish), as ../../rollout/SKILL.md § Phase C requires — query indexes and chrome build from the live tree.deploy-batch.mjs, never a hand-rolled loop; after a transient blip re-run the same command (the ledger skips live pages).Boilerplate lint — satisfy it up front, not at commit time. Blocks and styles lint under the project's own config; never add an .eslintignore for runtime files (../../deploy/SKILL.md § Target runtime). For the stock boilerplate that is ESLint airbnb-base + Stylelint standard, both blocking: kebab-case CSS class names and selectors; one statement per line — expand one-line multi-statement rules and arrow bodies, the recorded failure class (boilerplate .eslintrc.js and .stylelintrc.json, --all). Once before the checkpoint commit: the boilerplate's own npm run lint:fix (its lint:js -- --fix && lint:css -- --fix, over . and blocks/**/*.css + styles/*.css), then npm run lint — paste only the remaining errors into the conversion log. Target breakpoints set (DESIGN.json extensions.breakpoints.target): C0 adds "lint:breakpoints": "node stardust/scripts/replica/breakpoint-lint.mjs" to package.json and appends && npm run lint:breakpoints to lint, so every lint pass of deploy and rollout fails on an off-target @media width or JS threshold (preserve-direction.md § 4).
Final gate runs against the PUBLISHED origin, per delivered page, judged in the published-origin regime — harness numbers understate (source-fidelity-gate.md § The published-origin gate) — and never on the harness before the first PUT: the local harness feeds the structural asserts above (qa-gate.mjs, block-roundtrip.mjs --ew) and nothing pixel-shaped; the delivery pipeline folds section metadata and serves the media the harness cannot, so a harness pixel number is not a verdict and iterating CSS against it is budget spent without a page (../../deploy/SKILL.md § Local QA before deploy, scope boundary). The order is: deploy the representative page first, judge it on the preview origin, fix, redeploy — block CSS/JS rides the code-branch push, a content fix re-PUTs that one page, and the ledger skips pages already live (deploy-batch.mjs, above). Header and footer bands each ≤ 2 % via crop-compare.mjs, at least once per template (../../deploy/SKILL.md § Step 10 — Reconcile on the DEPLOYED URL).
../../rollout/SKILL.md § Procedure)Ledger phase strings are NOT named in ../../rollout/SKILL.md or its scripts (script headers use an unrelated numeric scheme); the only documented example is "phase": "C-deliver" (../../stardust/reference/run-status.md § Line shape). The strings below follow the convention derived from it — <Letter>-<first word of the phase heading, lowercased> — and are the exact rollout vocabulary ../../stardust/scripts/ledger.mjs accepts (--strict rejects anything else). Supervisors tail the ledger for the rollout line I-dashboard + end — that string is load-bearing. Every gate runs unchanged under hands-off (../../rollout/SKILL.md § Setup).
| Phase heading | phase | Produces (under stardust/rollout/) | Driver (stardust/scripts/rollout/ unless noted) |
|---|---|---|---|
| A — Inventory | A-inventory | coverage/pages.json, coverage/templates.json, rollout.json (fill site.da.org, site.site, site.da.ref, site.liveHost) | inventory.mjs --site-url <source-url> [--state stardust/state.json] |
| B — Block dedup plan | B-block | coverage/blocks.json (distinct blocks → edsBlockName), plan.json (representative-first; per page convert / reuse = deploy's brief input) | blocks.mjs, then plan.mjs |
| B2 — Dynamic surface | B2-dynamic | stardust/dynamic-features.md verified against fresh evidence — pre-import gate, blocks C | stardust/scripts/dynamics/dynamics-detect.mjs, stardust/scripts/dynamics/dynamics-plan.mjs --target-origin <host> (dynamics skill, § 4 copy step) |
| C — Deliver the site | C-deliver | ONE ledger phase (a single C-deliver start/end pair) run as RECORDED UNITS in stardust/rollout/progress.json (shape below), so a session that has to end (a hard blocker, an owner decision, a wait longer than the master's wait discipline allows) ends at a unit end and a resumed one runs only the units not done — a recorded run spent 118 turns in one C-deliver session and grew its context from 177k to 520k while its four cluster reports were about 1k characters each. Every page still goes through § 2's chain in this per-page order: convert (brief carries the plan step AND EW1–EW10) → delivery-lint.mjs + boilerplate lint → media-reconcile.mjs → davids-model-lint.mjs → sanitise.js → decoration asserts on the local harness (qa-gate.mjs, block-roundtrip.mjs --ew; structural exit codes only) → PUT → preview → .plain.html checks → deployed → THEN the visual gates against the PUBLISHED origin — replica's source-fidelity gate (pixel), crop-compare.mjs header/footer bands, chrome parity (§ 2, final paragraph; ../../deploy/SKILL.md § Step 10 — Reconcile on the DEPLOYED URL) → update-coverage.mjs. The units: C0 foundation — ONE foundation subagent authors AND deploys the foundation under the same fan-out rules (below): stardust/runtime-contract.json, styles/, fonts, favicon, the header and footer blocks, the per-locale nav/footer documents and locale shells when the site has them; lint; PUT → preview → publish; .plain.html checks — and hands back ONE verdict line plus the list of foundation files. The MAIN agent then runs the foundation-first gate on the shell template against the published origin — pixel at both widths, crop-compare header/footer bands, chrome parity (the gate runs after PUT + preview, its probes against the preview URL — ../../rollout/SKILL.md § Phase C); it fixes nothing itself — a failing gate goes back to the foundation subagent as one message carrying the numbers — then foundation-freeze.mjs freeze, the checkpoint commit, unit foundation recorded done (a recorded run's main agent authored the foundation itself and grew from 107k to 337k tokens of context inside this one unit, more than its four cluster units together). C-archetype, one unit per template, before its cluster (#126) — the cluster subagent deploys the template's GATED archetype first: convert (the encoder it will reuse for every sibling) → the chain → PUT → preview → the full gate row on the preview URL (gate-all.mjs --only <archetype> --eds-host <preview host>, both widths) → fix rounds, cap 3 (source-fidelity-gate.md § What a failing row means; a fourth round is the re-prototype decision) → unit done; only then migrate.mjs render for the template's siblings (§ 1 row 9) and the cluster unit below. C1…Cn, one unit per template cluster — ONE subagent per cluster, clusters spawned concurrently (disjoint blocks + pages): the subagent runs the WHOLE chain above for its blocks and pages — through the local structural asserts, then PUT → preview → .plain.html checks → the published-origin gates on the preview URLs (pixel on the archetype + one sibling per width, crop-compare, chrome parity) → gate-all.mjs --only <its pages> --eds-host <preview host> over its own pages, in parallel with the other clusters (#125: the added wall time stays inside the fan-out) → its coverage rows — writing its page list to stardust/rollout/units/<cluster>.paths (one DA path per line) and driving deploy-batch.mjs --paths stardust/rollout/units/<cluster>.paths --ledger stardust/deploy/ledger-<cluster>.json --log stardust/.work/rollout/<cluster>/deploy.log --concurrency 2 through run-bg.mjs (--concurrency 1 when more than three clusters run at once — several clusters PUT together and the admin API tolerates about 4–6 PUTs in flight site-wide). The ledgers are lock-safe, so clusters deploy at once without clobbering each other (fan-out discipline below); DA_TOKEN is read from its file at each call and never copied into a brief; a 401 halt is recovered by re-running the same command once the token file is fresh — the batch ledger resumes it (the deploy card's DA_TOKEN lifecycle rule, ../../deploy/SKILL.md § Deploy (DA Source API, from a local agent)). The subagent reports ONE verdict line: <cluster>: pages n/n live, blocks k, gate 1440 x% / 360 y%, requests r (a recorded 36-page hands-off run delivered 36/36 this way with zero 401s, its coordinator at or below 131k tokens of context across three cluster units). The main agent is a coordinator — spawn, wait, record the unit in progress.json, commit the checkpoint — and never runs a page instrument or edits CSS during the wave. After EACH unit is recorded and committed, C0 included, the run has a safe resume point; it continues with the next unit — a unit end is never by itself a reason to end the session (the master's turn-end rule: end only on completion, a hard blocker, an owner decision, or a wait longer than ~45 minutes). A session resumed inside C-deliver reads progress.json and runs only the units not done; a unit that was in flight is re-run from its recorded state — pages already live are re-verified, not re-authored. C-final (main agent) — foundation-freeze.mjs check; the queued stardust/rollout/foundation-requests.md lines applied ONCE; the published gate re-run on each affected template's archetype at both widths; then unit gate-all (kind final, recorded running → done in progress.json like every unit): gate-all.mjs --skip-existing over the whole roster through run-bg.mjs — the captures the clusters took are reused, so the pass is compares + probes only; still 30–45 min per 64 pages, the longest single step of a run, so a session may end at its unit boundary and resume after it; then update-coverage.mjs --gate stardust/replica/gates/all-<w>/summary.json (a page the table failed reads failed, never verified, until it passes or carries a documented override); then the single C-deliver end ledger line. Rollout's own pre-PUT gates are static, not pixel: section-fidelity.mjs outline (informs, never decides), image (= media-reconcile), path-safety, hygiene, tier declared (../../rollout/reference/delivery-gates.md). No pixel or visual gate runs on the local harness before the first PUT — the harness serves the structural asserts only; its pixel numbers are not a verdict (../../deploy/SKILL.md § Local QA before deploy). A recorded delivery session iterated CSS against a local harness diff for its whole budget and delivered no page. | delivery-lint.mjs, media-reconcile.mjs, section-fidelity.mjs, update-coverage.mjs, stardust/scripts/deploy/deploy-batch.mjs, stardust/scripts/replica/foundation-freeze.mjs |
| D — Site assembly | D-site | site/{sitemap.xml,robots.txt,manifest.json}; wire stardust/redirects.tsv into the redirects sheet at the content root (on a DA-backed site /redirects.json, columns Source / Destination; PUT via the admin API, preview + publish); the root MUST answer: when the source root serves a page, that page is delivered as the root index document (the pipeline serves / from it — /index ≡ /; never also a / row in the sheet, which would shadow it); only when the source root itself redirects (curl -sI <source-url> and follow the Location chain) does the sheet carry / and /index.html → the landing page; 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 per .html path and none for /); /nav + /footer published; the assembled site/sitemap.xml is the EXPECTED set only — stardust/rollout/ is in .hlxignore, the platform serves its own /sitemap.xml from its index of published documents (a recorded hands-off run reported "sitemap 36 urls" from the local file while the served one listed 58: every page plus 22 chrome documents); every chrome/fragment document (/nav, /footer, per-locale nav-* / footer-*, locale shells that are not pages) carries a Robots | noindex metadata row and is re-published when it lacked one; then assemble.mjs --verify-origin https://<branch>--<repo>--<owner>.aem.live MUST exit 0 (served <loc> path set == coverage rows; an extra path is a chrome document without noindex or a D2-built page without a coverage row, a missing path is a page not published live); the D-site end line's --detail names the SERVED count — "sitemap served 36 = assembled 36; redirects wired; / 200" — never the assembled one | assemble.mjs, assemble.mjs --verify-origin <live-origin> |
| D2 — Dynamic features | D2-dynamic | stardust/dynamics/parity.json — one replayable row per feature; a 404 on /query-index.json is answered by helix-query.yaml in the code branch FIRST (skeleton ../../dynamics/reference/listings.md § Getting an index at all): commit, push, publish the pages live, poll no more often than every 5 s for at most 10 minutes until total settles — no configuration-service write is involved (a 403 there with the migration token is expected), the sheet-backed interim index only when the code branch is not writable (recorded interim, decision named); every search-query row carries the source's expectCount + expectTitles (+ expectIncludes) read at detect time and the replay fails on a count mismatch; every page built here (the search results page) gets a coverage row — update-coverage.mjs --new <slug> --path </path> --template <id> --origin dynamics [--title …], kept across inventory.mjs re-runs | dynamics skill Phases 4–5, stardust/scripts/dynamics/dynamics-check.mjs --origin <host> |
| D3 — Multilingual (optional) | D3-multilingual | per-language content trees reusing the block library | ../../rollout/reference/multilingual.md |
| E — Full-site verify | E-full-site | each page verified / failed (a delivery.gate.pass: false from the pixel table never reads verified); headless render check on the first page of each template, including every restoreAtDelivery entry (an autoplay video ≥ ¼ visible is playing — currentTime advancing; a rotating carousel advances unpoked) | verify.mjs [--base <url>]; the table: update-coverage.mjs --gate stardust/replica/gates/all-<w>/summary.json |
| E2 — Link-audit completeness | E2-link-audit | nav/footer/landing targets deployed + published + verified; internal hrefs root-relative, extensionless; every href GET against the live tree. Internal targets missing from the capture split two ways, 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 (it enters the roster through 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; 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 default applies to UNcaptured in-scope pages only (a recorded run dropped ten captured locale roots by citing this row; another delivered 10 uncaptured in-scope pages — the right call); never leave a 404; the locale-root subtrees the crawl never captured are already listed in stardust/state.json site.captureGaps (extract copies them from _crawl-log.json#captureGaps and names the counts in its end ledger line) — a gap listed there was decided at Phase 1 and crawled before C-deliver, never discovered here | stardust/scripts/deploy/localize-links.mjs --source-host <host> --content content --redirects stardust/redirects.tsv, then --check |
| F — Optimize | F-optimize | optimize/findings.json, optimize/scorecard.json; gate exits non-zero on any open in-scope P1 | optimize.mjs, findings.mjs record / resolve |
| G — AEM autofix | G-aem | EDS project edits for fixable findings → re-deploy → re-run verify + optimize | autofix-aem.mjs --project <eds-root> --dry-run, then without |
| H — Report | H-report | the summary block (pages / templates / blocks / quality / to-deliver) + stardust/learnings.md entries | read rollout.json.lastRun + optimize/scorecard.json |
| I — Dashboard | I-dashboard | dashboard/index.html + dashboard/data.json | dashboard.mjs |
stardust/rollout/progress.json — the C-deliver unit ledger (row C): one object per unit, written by the main agent when the unit starts (running) and when it ends (done / failed), always BEFORE the checkpoint commit, so a session that has to end loses nothing and a resumed one reads the file and runs only the units not done. foundation is C0, final is C-final, a cluster unit carries its cluster's name; verdict is the subagent's one-line report verbatim; gates holds the published-origin numbers behind it (per width the archetype and sibling pixel percentages, the crop-compare bands, the chrome-parity delta count). A targeted edit of the one units.<name> object, never a rewrite of the file.
{ "units": { "<name>": { "status": "pending|running|done|failed", "kind": "foundation|archetype|cluster|final",
"templates": ["<template>", "…"], "pages": n, "blocks": n, "gates": { "1440": {…}, "360": {…}, "crop": "…", "chrome": "…" },
"startedAt": "<ISO>", "endedAt": "<ISO>", "verdict": "<cluster>: pages n/n live, blocks k, gate 1440 x% / 360 y%, requests r" } } }Fan-out discipline (C-deliver, main agent + subagents) — re-read at every session start:
node stardust/scripts/replica/foundation-freeze.mjs freeze + the checkpoint commit; until C-final nobody edits a frozen file — styles/, fonts/, head.html, scripts/, blocks/header/, blocks/footer/ (the script's default set; --paths when a project's foundation lives elsewhere). A main-agent edit after fan-out is the recorded failure: one foundation value changed and one body-class rule added under four running clusters cost two coordination messages and 23 minutes of rework in one cluster.stardust/rollout/foundation-requests.md — - <unit> | <what> | <evidence: instrument + numbers> | <templates affected>; the cluster ships with a scoped override inside its OWN block CSS and does not wait; never a rule on a frozen file. The main agent applies the queue ONCE at C-final (row C).foundation-freeze.mjs check runs at every unit end and at C-final start; exit 1 blocks the unit until the file is reverted (git checkout -- <file>) or the change becomes a request line.styles.css, header/footer CSS and the contract file BEFORE the first CLUSTER subagent spawns (during C0 the foundation subagent is the only agent running); no edit of a frozen file after fan-out (a recorded rename under three running agents cost seven coordination messages and re-reads).captureState[].restoreAtDelivery list (replica progress.json) verbatim and the unit implements every entry — autoplay muted loop, rotation interval, marquee speed — before done; "poster + paused video" or "static first slide" is never a deliverable (recreation-procedure.md § Carousels and animated sections). Phase E's render check and qa's video-not-playing row assert playback, dynamics-check.mjs video-plays asserts it per parity row.--fix a file another agent is editing.#!/usr/bin/env node, ESM import only (no require), run .mjs with node, --help prints usage and exits without touching any file; prefer a shipped script (../../stardust/reference/scripts-index.md) to writing one.stardust/.work/<skill>/probes/ (the master card's scratch rule; the template stardust/.gitignore ignores .work/), never in the worktree root, the EDS scripts/ dir or /tmp (lost at reboot, invisible to a resume) — the checkpoint stages every file the project's stardust/.gitignore does not exclude, and a helper named after a credential trips any secret scan at every checkpoint (a recorded run: ten times, from a stale ignore file). Name helpers after what they probe, never after a token.coverage/*.json + rollout.json (update-coverage.mjs), the media ledger (da-media-upload.mjs) and the batch ledger (deploy-batch.mjs) are rewritten under a cross-process lock with re-read-and-merge and a tmp + rename, so clusters may record at once; never edit one by hand or with node -e mid-wave (no lock, last writer wins), and never delete a *.lock directory while a writer runs.sleep before run-bg.mjs wait; a propagation wait is a bounded curl -sf poll, ≤ 5 s apart, inline.run-bg.mjs wait returns within its --max, 100 s by default and 110 s at most — inside the shell tool's ~2-minute default timeout, which applies only to a call that declares none; a declared longer timeout is honoured): a long instrument (gate.sh rounds, pixel loops, Playwright captures, deploy batches) goes through run-bg.mjs start, and wait is the NEXT tool call; never two long instruments as parallel tool calls in one turn, never two waits in one command (a recorded run paid one cache re-write for a 338 s foreground turn on the main agent — a 291 s pixel loop beside a batch start + wait).This card owns the Phase 5 copy step (replica Setup step 4 covers the Phase 1–4 sets): copy ../../deploy/scripts/ → stardust/scripts/deploy/, ../../rollout/scripts/ → stardust/scripts/rollout/ and ../../dynamics/scripts/ → stardust/scripts/dynamics/, whole directories (each imports only its siblings), beside the stardust/scripts/replica/, stardust/scripts/diff/ and stardust/scripts/stardust/ copies Setup made. The rule is Setup's: run the copies, never plugin paths, and never into the project-root scripts/ (../SKILL.md § Setup, step 4; ../../deploy/SKILL.md § 8. Block JS scaffold, "Copy set"). Migrate ships one script, ../../migrate/scripts/migrate.mjs → stardust/scripts/migrate/ (replica Setup step 4 copies it). The master's ledger.mjs (stardust/scripts/stardust/) and extract's thumb.mjs (stardust/scripts/thumb.mjs, copied beside crawl.mjs in Phase 1) are listed too because this phase uses them. Flags below are from each script's usage header.
| Script | Invocation (node …) | Prints / writes |
|---|---|---|
stardust/scripts/deploy/ai-readability.mjs | --origin <live-origin> [--paths <file> | /path …] [--min 98] [--token-env <ENV> | --auth-header "…"] [--exclude-blocks a,b] [--allowlist <f.json>] [--json <out>] [--verbose] | per page strict / code / servedGap + cause table; exit 1 when code < --min |
stardust/scripts/deploy/block-roundtrip.mjs | <protoURL> content/<page>.html [--blocks a,b] [--map <name>=<sel>] [--styles <css>] [--blocks-dir <dir>] [--width <px>] [--profile eds|generic] [--ew|--no-ew] [--json] | per-block role diff + editable N/M, dead K, duplicated D, exempt E; exit 2 on any 🔴 or decorate error |
stardust/scripts/deploy/build-harness.mjs | content/<path>.html stardust/.work/harness/page.html [--root <dir>] [--media-ledger <json>] | builds the local doc for the structural asserts only (qa-gate.mjs, block-roundtrip.mjs) — never a pixel verdict; strips the metadata block, folds section-metadata blocks into section classes / data-* attributes the way the delivery pipeline does, rewrites /img/ root-relative; --media-ledger <json> (auto-detected at stardust/deploy/media-ledger.json under --root) points editorial content.da.live image URLs back at the captured local files, because that host is auth-gated for anonymous loads |
stardust/scripts/deploy/content-inventory.mjs | library — shared role classifier; no CLI | imported by block-roundtrip, section-schema, content-diff |
stardust/scripts/deploy/da-media-upload.mjs | DA_TOKEN=… --org <org> --repo <repo> --scope <scope> (--dir <dir> | --manifest <json>) [--token-env <NAME> | --token-file <path>] [--concurrency 4] [--ledger <path>] [--retries 4] [--dry-run] | uploads editorial images to media/<scope>/, prints the content.da.live URL to author per file; mp4 per #161; SKIP other non-images, FAIL svg-unsafe, source 403 (bot wall, rehost) vs 404 (missing, omit); resumable ledger; an expired JWT exits 3 before any request; a 401 that persists after its retries halts the batch (exit 3, never a per-file FAIL) with the re-run instruction; the token comes from the variable named by --token-env (default DA_TOKEN) or from --token-file (read once at start), and the expiry / HALT / re-run lines name that variable or file, never the value |
stardust/scripts/deploy/davids-model-lint.mjs | content/ | content/<page>.html [--json] [--source-host <host[,host]> [--content-root content]] | 🔴 / 🟡 table (D1, D2, D4, D14, D15, <hr>); exit 2 on any 🔴 |
stardust/scripts/deploy/deploy-batch.mjs | DA_TOKEN=… … --org <org> --repo <repo> --branch <branch> --content content [--paths <list.txt>] [--concurrency 4] [--no-publish] [--force] [--ledger <path>] [--log <path>] [--token-env <NAME> | --token-file <path>] | PUT → preview → live per page; persistent content/.deploy-ledger.json, append-only log, skips pages already live; a 401 retries like a 429, one that persists halts the batch with the exact re-run command (never a per-page FAIL); exit 0 all live, 1 some pages failed (the same re-run re-drives them), 3 = token halt (expired JWT before any request, or a persistent 401 — refresh the token in the variable or file the halt line names, re-run the same command); the token flags are the uploader's, same semantics |
stardust/scripts/deploy/diff-profiles.mjs | library — eds / generic message profiles; no CLI | imported by the diff and round-trip scripts |
stardust/scripts/deploy/ew-editability-probe.mjs | --content content/<page>.html [--blocks-dir <dir>] [--styles <css>] [--width <px>] [--simulate-editor] [--exempt a,b] [--verbose] [--json] or <url> [<url>…] | per block editable / dead / duplicated / exempt, edit-mode style + height drift; exit 1 dead or duplicated |
stardust/scripts/deploy/localize-links.mjs | --source-host <host[,host]> [--content content] [--redirects stardust/redirects.tsv] [--dry-run] [--check] [--json] | rewrites source-host hrefs to root-relative, lists kept absolutes; --check exit 2 if any remain |
stardust/scripts/deploy/qa-gate.mjs | http://localhost:3000/stardust/.work/harness/page.html --schema stardust/eds-schema/<page>.json [--design DESIGN.json] [--maxw <px>] [--full-bleed a,b] | decoration-contract asserts (boot, one <h1>, blocks loaded, schema unit counts, the content cap at DESIGN.json's probeWidth); exit 1 on FAIL |
stardust/scripts/deploy/render-harness.mjs | content/<path>.html <out.png> [<block>…] [--styles <css>] [--blocks-dir <dir>] [--width <px>] [--ew] [--simulate-editor] | screenshot of local decoration; --ew survivor table, exit 1 on dead/duplicated |
stardust/scripts/deploy/sanitise.js | content/<page>.html (in place; ONE file per call — never more than two args) | non-ASCII → HTML entities |
stardust/scripts/deploy/section-schema.mjs | <protoURL> [--out <file>] [--width <px>] [--profile eds|generic] | per-section role inventory + repeat groups + editableTexts JSON |
stardust/scripts/deploy/style-fingerprint.mjs | "file:///abs/path/<prototype>.html" | JSON variation groups per section — run BEFORE block code |
stardust/scripts/migrate/migrate.mjs | render <slug…|--all> [--force] [--state <f>] [--proto-dir <d>] [--current <d>] [--out <d>] [--canon-css <f>] [--inline-canon] [--source <slug>=<file>]… [--archetype <slug>=<arch>]… [--branch-b a,b] [--stardust-version <v>]; gate <slug> <gate> [--evidence <t>]; deviation <slug> --kind <k> --source <t> --target <t> --reason <t>; decision <slug> --kind <k> [--json {…}]; variant <slug> <class…>; modules <slug> <id…> | --clear; summary [--json]; pagemap | <out>/<path>.html + sidecar, assets/**, state.json.migrate; per page A <slug> → <path> (<type>; n assets, n links, n broken, n sections), unchanged <slug> → <path>, refused <slug>: strict <n> — <what> — <fix> on stderr; final rendered N, unchanged N, refused N, passthrough N → <out>/; exit 0 / 2 any refusal / 1 usage |
stardust/scripts/replica/foundation-freeze.mjs | freeze [--root <dir>] [--out stardust/rollout/foundation-freeze.json] [--paths a,b,…]; check [--root <dir>] [--manifest stardust/rollout/foundation-freeze.json] | freeze: sha256 manifest {frozenAt, root, paths[], files{<path>: <sha256>}} of the frozen set — default styles/ fonts/ blocks/header/ blocks/footer/ head.html scripts/, existing entries only; --paths replaces it (root-relative, each must exist); dot-entries and node_modules skipped, .env never read, hashes only — then frozen N files → <out>. check: foundation unchanged (N files) exit 0; else one changed <path> / missing <path> / added <path> line each (a new file under a frozen directory counts) + foundation changed: c changed, m missing, a added, exit 1. Usage error → exit 2, one stderr line; --help touches no file |
stardust/scripts/replica/gate-evidence.mjs | [--migrated stardust/migrated] [--bg stardust/.work/replica/bg] [--progress stardust/replica/progress.json] [--lint stardust/scripts/rollout/delivery-lint.mjs] [--content content] [--widths 1440,360] [--height-tolerance 8] [--slug <s>]… [--check] [--dry-run] [--json] | one row per page <slug> <tier> 1440=<pct>%/Δ<px>[/ovf+<px>] 360=… cd=… lint=… media=… gates=<n>, then gate-evidence: <n> pages, <n> sidecars updated; writes each sidecar's gatesPassed[] (existing ∪ derived, existing first) + gateEvidence{} (one line per gate ending in (<job>.log); FAIL: / OPEN: when not passing; n/a: when the gate is not yet required) and progress.json migrate {at, pages, archetypes, siblings, thin, gates, missing} + siblings{<slug>: {archetype, variants, pixel{<width>: {pct, px, heightDelta, overflowX, verdict, label, regime}}, contentDiff, deliveryLint, media, gatesPassed, migrated}}; never adds content-fidelity; --check exit 2 listing <slug>: missing <gates>; --dry-run writes nothing |
stardust/scripts/replica/measure.mjs | <url> --selectors "a,b" [--against <url>] [--width 1440,360] [--all-matches] [--json] | root line per width per side (scrollWidth, viewport, scrollHeight, ◄◄ OVERFLOW +<n>px), rect + computed props (boxSizing included) per match, img <nw>×<nh> …/<file> per image, Δ lines; exit 0 even on deltas/overflow (a measurement — gate.sh turns the root line into the verdict) |
stardust/scripts/rollout/assemble.mjs | [--out <rolloutDir>] [--canon <dir>] [--verify-origin <live-origin>] | site/{sitemap.xml,robots.txt,manifest.json} — the EXPECTED set, fragments each robots: noindex; with --verify-origin: GET <origin>/sitemap.xml (a sitemap index followed), served vs assembled counts + extra / missing paths printed, manifest.json.servedSitemap written, exit 1 on any mismatch or an unreadable sitemap (the only network call) |
stardust/scripts/rollout/autofix-aem.mjs | --project <eds-root> [--out <rolloutDir>] [--slug <s>] [--check <c>] [--dry-run] | edits EDS project files; findings → in-progress with before/after log |
stardust/scripts/rollout/blocks.mjs | [--out <rolloutDir>] | coverage/blocks.json (distinct blocks, usedByPages, instanceCount) |
stardust/scripts/rollout/dashboard.mjs | [--out <rolloutDir>] | dashboard/index.html + dashboard/data.json |
stardust/scripts/rollout/delivery-lint.mjs | --file <html> [--path </da/path>] [--type page|fragment|index] [--optimizing-blocks a,b] [--json] | P0 / P1 / P2 findings; exit 1 on P0 or P1 |
stardust/scripts/rollout/findings.mjs | record --source <s> --layer <l> --check <c> --severity P1|P2|P3 --fixability platform-migration|design-pass|out-of-scope [--scope-level page|site|template|block] --scope-ids <a,b> --evidence "…" [--recommend "…"]; resolve <id> --status fixed|accepted|wontfix|open [--note "…"] | writes optimize/findings.json + scorecard |
stardust/scripts/rollout/inventory.mjs | [--migrated stardust/migrated] [--out stardust/rollout] [--site-url <url>] [--state <state.json>] | coverage/pages.json, coverage/templates.json, rollout.json; re-flags changed pages stale (never a pinned one); keeps the rows update-coverage.mjs --new added (origin marker in source.migratedHtml), status untouched |
stardust/scripts/rollout/lib.mjs | library — IO + roll-ups; no CLI | imported by every rollout script |
stardust/scripts/rollout/media-reconcile.mjs | --file <html> --deploy-host <host> [--media-ledger <file>] [--host-rewrite <bad>=<good>] [--json] [--apply] | decision per image (optimize / keep / hosted / rewrite / omit / unresolved); exit 1 on omit, unresolved (a content-host URL with no ledger to check it against included), or a hosted URL missing from the ledger; --apply rewrites the file in place |
stardust/scripts/rollout/optimize.mjs | [--base <url> | --root <dir>] [--slug <s>] [--all] [--out <rolloutDir>] [--current <captureDir>] | optimize/findings.json + optimize/scorecard.json; exit non-zero on open in-scope P1; with the capture present (--current, default stardust/current) findings the source shares are tagged source parity: (fixability: out-of-scope, autofix unavailable) — own report section, excluded from the score, the open counts and the gate |
stardust/scripts/rollout/plan.mjs | [--out <rolloutDir>] [--pending-only] | plan.json + a printed conversion plan |
stardust/scripts/rollout/section-fidelity.mjs | --file <content.html> --source <url> | --source-file <path> | AUTHORED vs SOURCE outline + REVIEW flags; always exit 0 (informs, never decides) |
stardust/scripts/rollout/update-coverage.mjs | <slug> --status pending|content-pending|converting|deployed|verified|stale|failed [--url <deployedUrl>] [--error <msg>]; --block <id> --status pending|converted|deployed|verified|failed [--eds-name <name>]; --new <slug> --path </delivered/path> --template <id> --origin <origin> [--title <t>] [--status <s>]; --gate <summary.json> [--pin] (--pin: first page first's hand-off, first-page-first.md § Then) | writes coverage, re-derives templates.json + rollout.json roll-ups; --new adds (same slug: updates) a row for a page built outside the migrated tree — origin recorded in source.migratedHtml as <origin>:<slug>, template row created or extended, a captured slug or a taken path refused (exit 1); inventory.mjs keeps such rows on a re-run, so the line runs once |
stardust/scripts/rollout/verify.mjs | [--base <url> | --root <dir>] [--slug <s>] [--all] [--out <rolloutDir>] | flips pages verified / failed; exit non-zero if any failed |
stardust/scripts/rollout/done-check.mjs | [--out <rolloutDir>] [--ledger stardust/status.jsonl] [--live-host <host> | --offline] [--json] | the completion verdict: one gap per line (pages_unfinished, pages_failed, pages_not_live, open_p1, header_parity, rollout_incomplete); exit 0 complete, 1 gaps, 2 usage |
stardust/scripts/stardust/ledger.mjs | <skill> <phase> start|end|blocked [--detail "…"] [--artifact <p>] [--next "…"] [--owner "…"] [--strict]; tail [-n 5]; last [<skill>] | appends one status.jsonl line and echoes it; an end needs an open start for the same skill + phase (warning; --strict exit 2, nothing written, one line naming the missing start command); on end warns when stardust/journal.md has no ## heading naming the phase (never an exit-code change) |
stardust/scripts/thumb.mjs | <png|dir…> [--width 480] [--max-height 3200] [--max-bytes 150000] [--min-share 60] [--offset 0] [--out <dir>] [--suffix -thumb] | one box-filtered thumbnail per capture, <src>: <W>x<H> -> <w>x<h> [scaled to <w>px] [(cropped at <n>px of <H> = <share>%)] [for --max-bytes <b>] -> <dst> (<bytes> bytes); over --max-bytes it goes narrower first (400, 320, 240 px — the whole page), then crops by measured size, never below --min-share of the page; a share below 100 → the rest with --offset <n> (<dst> gains -<n>) — read a thumbnail into the context only after this has written it |
Ledger lines go through the master's writer — copy the master's scripts (../../stardust/SKILL.md § Setup, step 7); one command appends one conformant line to stardust/status.jsonl and echoes it. Contract: append-only; one start + one end per phase, and the start line is the FIRST command of the phase, before any script of it runs (--strict refuses an end without an open start); blocked with the reason before any halt; every end has a section in stardust/journal.md headed ## <Phase name> — <what happened> (<date>) (ledger.mjs … end warns when it is missing); file created on first write (../../stardust/reference/run-status.md § Line shape; § Rules; ../../stardust/reference/journal-format.md § Entry format). --strict turns an unknown phase into exit 2 instead of a warning.
L="node stardust/scripts/stardust/ledger.mjs"
$L replica handoff start --strict
$L rollout A-inventory start --strict; $L rollout A-inventory end --detail "<n> pages" --artifact stardust/rollout/coverage/pages.json --strict
# … one start/end pair per phase, strings from § 3: B-block, B2-dynamic, C-deliver, D-site, D2-dynamic, (D3-multilingual), E-full-site, E2-link-audit, F-optimize, G-aem, H-report …
$L rollout C-deliver blocked --detail "DA_TOKEN expired (401) — ledger checkpointed" --strict # failure path: emit, then halt
$L rollout I-dashboard end --artifact stardust/rollout/dashboard/index.html --strict # the line supervisors wait for
node stardust/scripts/rollout/done-check.mjs # exit 0 before handoff end — below
$L replica handoff end --detail "<n> pages delivered; published-origin gate <result>" --artifact stardust/rollout/ --strict
$L last rollout # read back the latest rollout line
# no project copy yet → the raw form, same fields:
printf '{"ts":"%s","skill":"stardust:rollout","phase":"I-dashboard","event":"end"}\n' "$(date -u +%Y-%m-%dT%H:%M:%SZ)" >> stardust/status.jsonlreplica handoff end only on done-check.mjs exit 0. Otherwise close each gap with its own remedy and run it again: pages_not_live → publish them; pages_failed → the C-archetype fix rounds (cap 3, then the re-prototype decision); pages_unfinished → deliver the rows; open_p1 → F-optimize; header_parity → fix the header block, re-explore the live header and re-compare (../../diff/SKILL.md § The header contract); rollout_incomplete → finish the rollout. A gap only the site owner can close is a blocked line naming it, not the end line.
Page status: pages migrate delivered advance to migrated through the lifecycle writer, never a hand edit — node stardust/scripts/stardust/state.mjs advance <slug…> --to migrated --migrated <path> --skill migrate (../../stardust/reference/state-machine.md § Page lifecycle states).
Checkpoint commit — end of the phase and, inside migrate and C-deliver, the end of every unit (below), git repos only; the ignore guard is master Setup step 6, the push is deploy's Code stage (../../stardust/SKILL.md § Hands-off mode; § Setup; ../../deploy/SKILL.md § Deploy .DA Source API):
git check-ignore -q .env && ! git check-ignore -q stardust/state.json && git add -A && git commit -qm "replica phase 5 handoff: <what landed>" && git pushC-deliver units (§ 3 row C) — per unit, in this order: the progress.json write, the mechanical check, the checkpoint commit, THEN the next unit. The unit is on disk and committed before the session could end, so a resume loses nothing: a session resumed inside C-deliver starts from stardust/rollout/progress.json and runs only the units not done (an in-flight unit re-runs from its recorded state — live pages are re-verified, not re-authored). A unit end is a safe resume point, not a stop: the session ends only for the master card's reasons (completion, a hard blocker, an owner decision, a wait longer than ~45 minutes).
# 1. stardust/rollout/progress.json units.<name> ← {status: "done", kind, templates, pages, blocks, gates, startedAt, endedAt, verdict}
node stardust/scripts/replica/foundation-freeze.mjs check # 2. exit 1 blocks the unit: revert the file or file a request (§ 3)
git add -A && git commit -qm "replica phase 5 C-deliver unit <name>: <verdict line>" # 3. the checkpoint, same ignore guard as above
# 4. next unit — the next cluster report to record, or C-final; nothing else runs on the main agent between unitsMigrate units (§ 1 row 9) — the same discipline one phase earlier: per unit the stardust/migrate/progress.json write, the checkpoint commit, THEN the next unit (plan → one render per template cluster of at most ~8 siblings → assets when media is rehosted here → report). A session resumed inside migrate starts from that file and runs only the units not done; a unit left running re-renders its slugs (migrate.mjs is idempotent — unchanged pages are skipped). A unit end is a safe resume point, not a stop.
# 1. stardust/migrate/progress.json units.<name> ← {status: "done", kind, templates, pages, startedAt, endedAt, verdict}
git add -A && git commit -qm "replica phase 5 migrate unit <name>: <verdict line>" # 2. the checkpoint, same ignore guard as above
# 3. next unit — the next render cluster, assets, or report; a resumed session skips every unit already done.tessl-plugin
skills
audit
reference
deploy
reference
scripts
test
diff
direct
dynamics
extract
migrate
prepare-migration
prototype
assets
motion
fixtures
reference
qa
replica
reference
scripts
test
reskin
rollout
spec
stardust
uplift
reference