feat(trace): trace ordinary tool calls

[rgao-coreweave]

Summary

Trace ordinary tool calls as children of their owning turn.

• ToolLifecycle correlates exact tool_use_id values, ignores duplicate terminal hooks, recovers restart-first results, and closes tool spans before their parent turn.
• HookHandler handles ordinary pre- and post-tool hooks.
• Session keeps turns open while their tool children are active.
• Restart-first tool hooks recover their owning transcript turn by exact tool_use_id; completed historical turns are bounded so later responses cannot leak into them.

The special Agent tool remains deferred to its dedicated lifecycle.

Validation

• npm run check
• 88 tests pass

[ro31337]

after a daemon restart, could this create an empty turn and miss the prompt and the model response that triggered the tool?

For example, if the transcript already has one response, responseOffset will be 1 and userText will be undefined, so the recovered turn will miss both the prompt and that response, right?

[rgao-coreweave]

Good catch! Matching SessionEnd currently repairs the turn, but Stop, a subsequent prompt, or shutdown can finalize it first. I’ll recover the owning transcript turn by exact tool_use_id, retain the fail-closed fallback when no match exists, and add regression coverage.