Build in public logTracker line

Server: the small JSON files are read exactly (fix/product-small-json-readers-exact; the follow-up to the stamp and size heads): origins.json (server/masterOrigins.ts), the Home and Tokens samples (server/homeSample.ts) and the Drift sample (server/driftSample.ts) read the file's text on every call and keep only the parse, by the text itself, so no time stamp and no size is trusted. Stamp and size could not tell apart two files of one length written inside one clock tick; this can. An unchanged Drift sample still answers with the same object, which server/drift.ts relies on. The larger reads keep stamp and size (the content hashes, the picture fit, the Pen reads, the HTML pages' key), where exact would mean a hash or megabytes on every read. Tests written first and failing on develop on macOS: three in tests/unit/stamp-keyed-caches.test.ts, two files of equal length under one stamp (3 failed of 6 before, 6 pass after).

Time
2026-10-13 11:49
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 766
Session: highfi-product-fidelity
Brought to main by
a1558ea994 Merge pull request #463 from lenilsonjr/develop (2026-10-13 14:27)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)