Collector 0.7.44: short writer holds, work links, weekly tool stats, exact Grok cost, 0.7.39 fixes, intake through updates

Collector 0.7.44 replaces 0.7.43: short writer holds, usage linked to work, weekly tool statistics, exact Grok cost, fixes for ledgers that started on 0.7.39, and intake that stays open through updates.

• Writer holds stay short (.163.102). Periodic WAL truncation no longer waits on readers, and two new indexes shorten the dashboard's usage-authority counts. On a copy of a busy host's ledger, an 11-minute replay spooled 0 of 774 steady requests; 0.7.43 spooled 103 of 777.
• Usage links to work (.163.104). A session bound to a work item charges each eligible event to that work once, and uploads carry opaque work and run references.
• Weekly tool statistics (.165.25). The collector uploads weekly tool-use counts with bounded report sizes, and later weeks stay live.
• Exact Grok cost (.165.57). Grok's vendor cost ticks ride in the upload metadata, so the cloud prices them exactly (1,200 ticks is 120 nanodollars).
• Ledgers that started on 0.7.39 (.163.108).
  • The per-source admission cap rises from 600 to 3,000 requests a minute. At 600, a busy host refused more than half of its traffic.
  • The session-sync delta uses an indexed seek; it used to time out on large ledgers.
  • The legacy session-summary rebuild runs in bounded, resumable background passes.
• Intake stays open through updates (.163.96). During a managed update, plimsoll lifecycle update starts a small listener on the collector's port that spools hook posts and OTLP exports; load-launch-agent releases it just before the new daemon starts. The new daemon replays each spooled item once, and probe events never count as spend. An update that doesn't complete releases the listener before it exits, so the restored runtime's daemon can bind the port. In the proof, 5 of 5 sends during the stop were accepted and replayed once; 0.7.43 refused all 5. The gap with no receiver fell from 16.6 s to about 3.7 s.

Updating and rolling back:

• Rollback to 0.7.43 is supported. On a disposable home that 0.7.44 had updated and run, 0.7.43 passed snapshot list and prune, status, the daemon with hook and OTLP intake, export, and session sync (38 of 38 checks). Every event and the update receipt were kept, and 0.7.44's new tables, indexes and triggers stayed in place. 0.7.44 then reopened the same ledger and accepted intake again. 0.7.43 doesn't recognise 0.7.44's update operations, so its prune keeps both 0.7.44 snapshots; nothing is lost.
• The first start builds two indexes before readiness. On an 85 GB ledger that took about 20 minutes (1,237 s), so hosts with very large ledgers should wait for the follow-up that moves this work after readiness. Check readiness time on each host after its update.
• Only managed updates are covered by the listener. Sends during any other stop are still not recorded; token usage in session files is captured again after the restart.

Runtime CLI SHA256: 6dbca6f2e57191f8d7e59762cf80ed15aaea22373056d83069da42cab808d677.

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