refactor(replay): own execution and source data ports in contracts

TH
2h ago
+306-456

Summary

Move replay data contracts and their consumers together for #3871. Rename-display churn is qualified by equal no-renames content and mode streams.

Unpublished candidate: f672c34fac3f1577bec43ef767c0c8e18f4958b9. 61 files / 1,486 gross lines above C3 using -M90%; 331 / 8,820 against default-main merge-base.

Validation

Independent Codex recheck found no actionable findings within the R1 repair and preservation interactions. The two-file repair survives all four rebases; eight range-diff entries match.

At f672c34fac3f1577bec43ef767c0c8e18f4958b9, pinned frozen install/build and full-repository format passed. Exact affected: 42 passed / 25 skipped, exactCommit=true, checkoutChanged=false; receipt fbeed59e5e56830618c3e6e0009140335af59d6b370ec4e96e6fe439cf0fd4c5.

All seven new-head canonical invocations passed once, serially, under one frozen ENV. Counts overlap; skips retain their CI/manual owners. Existing refs stayed unchanged; source/logical index matched before and after each gate. Physical-index captures remain separate, with within-head byte-change causes unproven. Initial/final snapshots cannot exclude transient edits.

The candidate remains unpublished; published head 6d011ba8 is unchanged and new-head hosted checks are unverified. Node22.13 packaging and earlier ENV/ref owner dispositions still block source publication. Both plugins remain private pending maintainer placeholders, trusted publishers and usable publication. Native ADR, live/current-client, performance and security remain open. No merge clearance.