Build in public logTracker line

fix/core-shipq-remove-final-pins, the runner removes a pin once its item has shipped (a stopped item keeps its pin and results for its lane): its own node_modules link out, then a plain git worktree remove, never --force; a pin with a change or a refusal stays with one log line, a held item and a branch queued again keep theirs, the branch stays (240 pins of no live item had stopped the queue on disk that morning); tests/unit/shipq-remove-final-pins.test.ts rehearses a shipped, a stopped and a dirty pin.

Time
2026-10-15 11:32
Where it was logged
context-log/living/05-TRACKER-LOG.md, line 873
Session: highfi-core-ship-hardening
Brought to main by
06081bac7f Train of 2 heads: Phone: Drift cards and Tokens scroll to their last row at 390; Ship queue: SIGTERM in waits, and shipped pins go away, riders and carried heads too (#531) (2026-10-15 15:04)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)