Build in public logTracker line

shipq-network-retry.test.ts waits for network-retry.json itself to be cleared, not for the queue's lock, which the runner releases before it settles and clears the count (CI #563's one failure; fix/core-shipq-retry-test-race)

Time
2026-10-17 19:45
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 940
Session: core-ship-hardening
Brought to main by
115a5a581e Ship queue: the network-retry test waits for the retry file, not the lock (#581) (2026-10-18 07:54)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)