Build in public logTracker line

a unit test that leaves a temp entry behind fails CI's web job and ship's local unit check (HF_UNIT_TMP_STRICT=1, js-ci-and-test-isolation#2): six leaks fixed first, the two windows registry files (their removal now runs after the registry's own exit write), analyzer-scan, project-landing, where-own-checkout and playwright.config.ts's throwaway licence key folder; the whole unit suite strict exits 0 (fix/core-unit-tmp-strict, tests/unit/unit-tmp-strict-on.test.ts)

Time
2026-10-17 17:11
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 948
Session: core-ship-hardening
Brought to main by
c4700e8269 Train of 4 heads: Node 22 is HighFi's floor: the installer, both prompts, /start and the guide; Verify: a Pen-only component compares its master, as the drift job does; npm names Node 22 as HighFi'... (#570) (2026-10-18 00:11)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)