Fix live voice leg correlation

[dimavrem22]

Executive Summary

Makes live voice validation select the recipient-owned call leg precisely when paired-call correlation is available, while retaining a strict compatibility lookup for older responses.

Description

• Reads the driver call's optional paired_call_id after completion.
• Queries the recipient identity with that value and rejects missing or ambiguous matches.
• Requires both remote and local speech on the recipient leg.
• Restricts the driver-leg transcript assertion to driver-local speech.
• Keeps the compatibility lookup bounded by baseline IDs, direction, endpoints, timestamps, and uniqueness.
• Names the caller as the explicit SMS recipient and, on a timed corrective turn, makes the hosted agent edit the same persisted action before readback while keeping the strict marker assertion.
• Gives realtime responses a 30-second media-peer window while retaining mandatory two-way transcript proof.
• Places the recipient and run marker first in the spoken request and uses longer speech-safe marker words across TTS/PSTN/STT.

Reason

A managed call produces separate records for the driver and recipient. Requiring recipient speech on the driver-owned transcript validates the wrong record and can fail despite a successful two-way conversation.

Decisions

• Preserve every existing intent, action, call-status, and speech-mode assertion.
• Fall back only when the installed SDK/API response does not expose paired correlation.
• Reject ambiguous fallback results instead of accepting the newest nearby call.
• Coordinate typed correlation support with inkbox#138.

Testing

• Full local suite: 443 passed, 23 skipped.
• Added unit coverage for paired lookup, compatibility lookup boundaries, ambiguity rejection, and owned-leg transcript assertions.
• Updated workflow YAML parses successfully.