Build in public logTracker line

HighFi's browser, H1: the capture and its keep path (feat/core-browser-capture, from origin/main 1ee4ebe5cb; the advisor's browser plan draft 4, section 2c, the facilitator's 04:22). One capture shape for WebKit and Chromium names its engine and the world it ran in, client or page; one with no world or an unknown one is refused, and a page-world capture keeps its world through the summary, the kept scan (siteStore captures) and the build's .highfi/site-import.json, and is never judged as client-world. Engine rules from the built-in browser spike's compare: values kept rounded to 0.01 px and matrices to 4 digits, agreeing within 1/64 px plus the rounding; boxes within 0.5 px across and, down the page, 1 px a line of text (a height by the lines in its row); Chromium is the reference. The captures map into a kept scan through snapshotFromHtml, componentCandidates, tokenCandidates, siteFonts, groupTemplates(topScreens) and keepSiteScan, with the captured pictures for the shots and no fetch; one site per import, 20 pages, 600 nodes and 2 MB of HTML a page. POST /api/import/site/capture holds a capture in memory on the session token alone (requireToken, checked before a body of up to 16 MB is read) and answers its summary with personal-data marks (emails, a name after Signed in as, account ids); POST /api/import/site/capture/keep writes the kept ones and discards the rest; both refuse on the live demo and answer only while the site components are on. Tests first: tests/unit/site-capture.test.ts (14) on the spike's canned and tamper captures in tests/fixtures/site-capture/, red on 1ee4ebe5cb; two rows in the API contract table. No UI, no Rust; the shell's post is H2b's.

Time
2026-10-29 04:31
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 1017
Session: highfi-core-lead
Brought to main by
5cc33bc774 HighFi browser H1: the capture shape, engine rules and the keep path (#637) (2026-10-29 09:58)The rows below that say "with it" describe this commit, which can carry other work from the same pull request.
Impact on decisions

Names no decision record.

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)