Feature: task completion efficiency / retry rate tracking

[AgentSeal]

Track how many turns it takes to complete a coding task, not just how much it costs.

Example: implementing stripe auth - did it one-shot or take seven rounds of edit/test/fix cycles before it worked?

Useful metrics:

• average turns per task type before completion
• one-shot vs multi-attempt rate per category
• edit/test/fix cycle detection (edit -> bash test -> edit again = retry)

[AgentSeal]

Shipped in d202815.

One-shot rate now shows in the By Activity panel for categories that involve code edits. Detects edit/test/fix retry cycles within each turn.

Per-task lifecycle tracking (turns to complete a full task across multiple requests) isn't feasible from the JSONL data alone - there's no completion signal. The per-turn efficiency metric is what we can measure with confidence.