Restore shipped swipe response compatibility after unified gestures

[thymikee]

Problem

PR #1212 merged unified gesture planning but changed the published swipe response contract. The shipped v0.19.3 response exposed x1, y1, x2, y2, durationMs, effectiveDurationMs, timingMode, count, pauseMs, and pattern. The unified response omits several compatibility keys.

For ping-pong repetitions, the new from/to can also describe the final reversed leg rather than the authored swipe endpoints.

This was identified in coordinator review before merge: #1212 (comment)

Scope

• Preserve shipped swipe response aliases while retaining the unified gesture response.
• Report authored swipe endpoints consistently for ping-pong/repetition execution.
• Do not change the new gesture response contract unnecessarily.

Acceptance criteria

• A production daemon-route JSON regression pins all shipped swipe coordinate, timing, repetition, and pattern fields.
• Ping-pong with an even count reports authored endpoints, not the last reversed leg.
• CLI, Node client, daemon, and MCP projections remain coherent.
• Required affected checks pass.