refactor(maestro): load the engine as a managed replay plugin

TH
2h ago
+2016-451

Summary

Extract managed Maestro into its v2 optional plugin for #3377, retaining selected-package loading and explicit host routing.

Unpublished candidate: 79c2006edca27fd335a939d02b1aad38c0ed1ff8. 104 files / 2,472 gross lines above PREP; 273 / 7,420 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 79c2006edca27fd335a939d02b1aad38c0ed1ff8, pinned frozen install/build and full-repository format passed. Exact affected: 42 passed / 25 skipped, exactCommit=true, checkoutChanged=false; receipt 7063f85786a69c0c8b4fa923828f12b615def3d74982f9fc9e14bd794bea4f41. Full: 41 passed / 25 skipped; receipt 7e1f19f6ecb5c4551041126f11f738a438f914bbb5b9869e2a009edb85835e5e.

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 924a0bd3 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.