igneum/tools/site-redesign
igneum-labs 540717d5ec site-redesign: the package's look 1:1, header and footer included
The owner, 12:4x UK: "some things look different on the live site vs the one I sent you, match it 1:1". site/site.css is
now the package's design system as delivered (tokens, type, chrome, components, breakpoints) with self-hosted fonts, the
two text tokens for contrast on light surfaces, and a compatibility layer for the data pages' vocabulary. The header
and footer are the package's (status bar, logo with the ember stop, the six items, the Discover dropdown, the theme
toggle, the Download button, the burger and its sheet; the footer grid with the three icon links, Run, Read, Explore
and the legal line). The home, miner and wallet pages carry the package's markup on our content; the live page, the
explorer, the litepaper, the faucet, the MetaMask page and the generated pages take its values in their own blocks.
The theme is always set (stored, else the OS), so the package's light theme applies. Side-by-side sheets before and
after at 1440 px from tools/site-redesign/sheets.mjs; no sample data, no review chrome, the hero loop continuous.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-07 10:57:32 +00:00
..
tests site-redesign: the full-site redesign on our content, 22 pages served 2026-10-07 10:30:18 +00:00
engine.js site-redesign: the full-site redesign on our content, 22 pages served 2026-10-07 10:30:18 +00:00
README.md site-redesign: the full-site redesign on our content, 22 pages served 2026-10-07 10:30:18 +00:00
sheets.mjs site-redesign: the package's look 1:1, header and footer included 2026-10-07 10:57:32 +00:00

The redesign package's feed adapter and its tests

engine.js is the full-site redesign package's observer adapter as delivered on 7 October 2026 (the /api/live contract validator, the read-only Feed with its backoff, and the package's explicit sample generator). The served site does not load it: the pages use site/scenes/feed.js and site/live-dag.js 2.0.2, which normalise the observer reply themselves, and no sample data is served anywhere. The file is kept here, unserved, so the package's contract tests keep running in the gate (tools/ci/pre-push.sh: "redesign package data tests") against the /api/live shape the site depends on.

node tools/site-redesign/tests/data-tests.cjs