fix(ios): analyze the timed receiver after delivery acknowledgement

Craft 0.0.428 iOS template compilation failed independent analysis after the actual XCTest passed: https://github.com/craft-native/craft/actions/runs/41503996760/job/125478438917.

Retained artifact 13172192149, 546865 bytes, SHA-256 05bb1427c63279c918560f10e1308a9d9cb1f6a746e11098970f22793a5bbeb4, verified against GitHub. The exported immediate receiver receipt has zero phases/callbacks, but XCTest subsequently passed its existing exact 24 began/24 ended/zero cancelled and 24 callback assertions. The capture precedes those receiver acknowledgements. Native playback completion alone does not establish receiver observation.

Keep the immediate capture for diagnostics and retain a separate canonical receiver snapshot after the unchanged delivery assertions acknowledge all events. Analyze that final receipt from the same single attempt. Preserve all 24 names, the 80ms/25ms schedule, the 50ms timing tolerance, no warm-up taps, no sleeps, no retry combination and the compressed negative fixture. Missing acknowledgements or final evidence must fail. This correction does not explain or close the original intermittent missing callbacks in https://github.com/craft-native/craft/issues/432.

The catch path also attempts to copy the already retained xcresult again and emits EEXIST, although the first result bundle is present. Retention should be idempotent within one attempt, without accepting evidence from another run.

Related: https://github.com/craft-native/craft/issues/443 and https://github.com/stacksjs/hq.training/issues/318.

The retained exact-source xcresult reports XCTest Passed, one test, zero failures/skips. Its immediate receiver attachment contains an empty journal, while the subsequently executed unchanged value assertions require all 24 began/ended phases and all callback names. This supports correcting snapshot ordering; it does not establish that the original missing callbacks in /craft-native/craft/issues/432 are fixed. No schedule, timing tolerance or input dispatch change is proposed.