Build in public logTracker line

fix/core-shipq-network-retry, a runner that ends on a network stop starts a runner again by itself after 300 s, at most 12 times in a row (counted in highfi-shipq/network-retry.json, cleared once anything ships), so a queued item never waits on a queue command (train 10 stood 28 h from 22:05 on the 15th); tests/unit/shipq-network-retry.test.ts takes origin away under a ship and gives it back.

Time
2026-10-17 02:21
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 895
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)