Build in public logTracker line

Build step (a), data side (feat/product-site-build-generator, stacked on feat/product-candidate-words e951b6e531 until it lands; the build-step plan, accepted by the advisor's call 13; the facilitator's line of 17:2x): each candidate keeps its first element's markup, sanitised and bounded to 8 KB (server/import/siteMarkup.ts; scripts, frames, objects, templates, event attributes, inline styles, form actions, script and data addresses and srcset entries on another host dropped and named; images and links keep their address, made whole, nothing fetched), and the rules of the page's own style blocks that name its classes (no linked sheet until D-154; no @import, @font-face or expression). The generator (server/import/siteBuild.ts) writes, in memory, tokens.css, a component per pick as plain JSX with a CSS module (text as string literals, never dangerouslySetInnerHTML), a template per picked template in page order, and .highfi/site-import.json; every name a valid unique identifier. The page source goes to the candidates beside the snapshot, which still keeps no text. Nothing is written yet: head (b) adds the folder, preview and build. Attributes are written as React's types want them: numbers as numbers, union values only when allowed, plain aria names, value as defaultValue only on a form field (the advisor's read of 9e564e3759). Pinned by frontend-prototype-v1/tests/unit/site-build.test.ts: a canned hostile page, and a strict type-check of every generated file against React's own types.

Time
2026-10-23 17:53
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 979
Session: highfi-product-lead
Brought to main by
b4133fb37f Build a first draft from the picked candidates, behind a flag (#604) (2026-10-24 00:55)The rows below that say "with it" describe this commit, which can carry other work from the same pull request.
Impact on decisions

Records it names:

  • D-154 The site scan may render pages in a browser, on the local install only accepted

No decision record was created or changed with it.

Scope expanded or reduced

Neither: no roadmap entry was added or removed with it.

Plan clarity

No roadmap entry's clarity score changed with it.

Milestones and metrics: roadmap entries moved

No roadmap entry's percentage moved with it.

Superseded
not recorded (tracker lines carry no supersedes field)