Collector 0.7.45: safer capture and session totals

Collector 0.7.45 replaces 0.7.44. Setting up a machine now takes one command, Claude lane spend carries its work item, and history from folders that were never captured can be brought in. It also keeps every unsent row through retention, repairs busy session summaries in small pieces, and holds up when two parts of Plimsoll start at the same moment.

• Setup in one command (#428). plimsoll join registers the agent session folders it finds, starts or safely restarts the background collector, and waits for the first upload before it says the machine is connected.
• Claude lane spend carries its work item (#429). Claude Code hook and OTLP events from a dispatched lane are stamped with the lane's work item, as Codex lanes already are, so spend lines up with the work that caused it.
• Missed history can be imported (#431). plimsoll capture-roots import-history --root <id> previews, and with --apply imports, session files from before a folder was enrolled. It only imports folders that no capture path ever covered, so nothing is counted twice.
• Unsent rows survive retention (#417). Raw retention never prunes a row that still has an upload waiting.
• A fresh ledger keeps its capture roots (#426). A replaced ledger keeps each enrolled folder's saved boundary, so capture resumes where it left off.
• Busy session summaries repair in small pieces (#425). An edit to a long session repairs only its 4,096-row segment instead of rebuilding the whole summary.
• Duplicate-marked rows stop counting (#419). A row marked as a Codex duplicate after its dashboard fact exists is removed from that fact.
• Sturdier sync (#418, #420, #410, #412, #416). Sends end before the cloud's commit deadline, a crashed hook-spool unit replays exactly once, a sync pass shares one storage-retry budget, and a stuck summary recovers and says why in plimsoll status.
• Two processes can open a brand-new ledger at the same moment (#434). The daemon and a hook or CLI starting together on a new install no longer fail with "duplicate column name", and each open waits no longer than its startup deadline.
• Discovery keeps moving on a busy host (#435). A collect that has started finishes a small, bounded amount of folder discovery even when the host is slow, so new sessions are found while a large file is still being read.

Updating and rolling back:

• After the upgrade, each session that is touched rebuilds its summary once. On a copy of a Studio 5 ledger, 8 summaries were complete again in 68 seconds, with no intake loss.
• Rolling back to 0.7.44 is safe. 0.7.44 opens a ledger written by 0.7.45 and keeps its events unchanged.

Runtime CLI SHA256: cd8e8d3099a37a479ddf875465f58057c3ba5aaa3314021d38b5216ae37228ad.

Qualification: typecheck, the full proof suite and system end-to-end qualification ran on the merged commit. The published package is the qualified artifact from that run.