Interaction responses leak runner uptime internals and default-value noise #1077

Observed while dogfooding Bluesky: a default (no-flag) press @ref response includes:

"gestureEndUptimeMs": 1418719052.338875,
"gestureStartUptimeMs": 1418718741.4275,
"currentUptimeMs": 1418719052.9,
"count": 1, "intervalMs": 0, "holdMs": 0, "jitterPx": 0, "doubleTap": false

The uptime fields are runner-internal timestamps with microsecond precision — meaningless to an agent, and burned on every tap. (They feed the recording touch-overlay correlation, so they cannot simply be deleted — but they should stay internal to the daemon/recording pipeline rather than ride every wire response; check src/daemon/handlers/interaction-common.ts's visualization result building and the recording telemetry consumer before moving them.) The always-present default-value tap options (count: 1, intervalMs: 0, ...) are pure token noise when they equal defaults.

Expectation: default responses omit runner uptimes (keep them under --debug or in the recording pipeline only) and omit tap-option fields at their default values. This is a wire-shape change, so per #1008 it needs provider-integration verification and a check of replay/recording consumers.