PiClaw v2.6.14 — "Time Bandits"

A small release about time, meters, and fewer unnecessary disappearing acts.

Features

Agent replies now carry persisted timing metadata and expose it on the message timestamp tooltip, so hovering the timestamp shows when the reply was sent, when the run started, and how long the agent took to produce the terminal reply.
The same timestamp tooltip now includes per-reply token statistics when the provider supplies usage metadata, including total, input, output, and cache token counts, because guessing whether a reply was expensive is an excellent way to lose an afternoon.

Relaxed the system meters compact breakpoint from 900px to 600px, because the chart view was being hidden on tablets despite there being perfectly adequate room for it. CSS, naturally, had opinions.

Added structured agent_timing content blocks for finalized terminal agent replies, avoiding a database schema migration while keeping timing and usage data available in timeline payloads.
Threaded assistant-message usage from message_end through AgentTurnCoordinator, runAgentPrompt, web terminal reply persistence, and timestamp tooltip rendering.
Added regression coverage for timing formatting, token-stat formatting, turn usage propagation, and the 600px meters compact breakpoint.
Post timing fixture tests now resolve source paths from the checkout instead of assuming /workspace/piclaw, because CI runners cruelly insist on using their own directories.
Project-trust session fixtures now use an isolated cwd, because upstream session validation quite reasonably dislikes directories that only exist in the test author’s imagination.
Rebuilt the web bundle so the timestamp tooltip, token stats, and breakpoint changes ship in static assets.

Older messages do not have persisted agent_timing blocks, so their timestamp tooltip only shows the sent time.
Native browser title tooltips are still a desktop-first affordance; tablets may need a later tap/long-press timing popover if we want this to be fully touch-native.