Build in public logTracker line

drift-scale on CI: the cause was a superseded first-page answer (useFetch shared one alive flag, so StrictMode's first run still landed) resetting the appended pages after page 2, with no request left to make; useFetch drops superseded answers, Drift keys later pages to their first page and checks again after each page; a regression test holds the late answer (fix/drift-scale-spec)

Time
2026-10-08 05:21
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 232
Session: highfi-product-fidelity
Brought to main by
734c47b082 Demo re-recorded from ab1c3816 (#141) (2026-10-08 06:43)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)