Build in public logTracker line

fix/core-shipq-no-solo, the ship queue takes `--no-solo`: a queued solo item may ride a train again (the nine solo items into main could not ride when trains came on at 10:08; requeuing kept solo, and a hand edit of the state file is refused); `--solo` with `--no-solo` is refused; tests/unit/shipq-no-solo.test.ts rehearses two solo items requeued with `--no-solo` leaving as one train.

Time
2026-10-15 10:10
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 861
Session: highfi-core-ship-hardening
Brought to main by
8a2a3edb86 Ship queue: --no-solo lets a queued solo item ride trains again (#525) (2026-10-15 11:28)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)