feat(plugins): validate native execution in the managed replay registry

TH
2h ago
+343-34

Summary

Introduce optional replay execution registry contracts for #3871, preserving backend identity, transient recovery and disposal fencing.

Unpublished candidate: 8f2ac64f935d4fbf740c5de02d3c5a8b779a5a6e. 12 files / 385 gross lines above DATA; 333 / 9,141 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 8f2ac64f935d4fbf740c5de02d3c5a8b779a5a6e, pinned frozen install/build and full-repository format passed. Exact affected: 42 passed / 25 skipped, exactCommit=true, checkoutChanged=false; receipt c43ad7c22d01eeea3b699e4c88499cf6311aa0c8f6c5d054845884880284093e.

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 61ae2772 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.