Build in public logTracker line

fix/core-shipq-status-head, a queue call fetches each named branch and stores the head origin has on its item, so --status shows the head an update moved it to (settings-home-paths read 852e53fe8c while origin was d52681091f); a failed fetch is said and the head stays; tests/unit/shipq-status-head.test.ts.

Time
2026-10-17 02:25
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 897
Session: highfi-core-ship-hardening
Brought to main by
7b7e248504 Train of 4 heads: Licence: paste a key in Settings; a test key reads as a test key; Ship queue: a runner that ends on a network stop starts again by itself; Site: a Where we are belt, one big figur... (#545) (2026-10-17 05:13)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)