#3493 test(maestro): characterize intentional parent-center activation

Summary

Closes #1718.

Document Maestro parent-center activation as an intentional compatibility waiver and remove the resolved open-gap entries. Eight files add a sealed vector from pinned Maestro 2.5.1 Maestro.tap, owning atomic/coordinate dispatch assertions, and a lifecycle test correction required by the coverage failure. Ordinary selectors retain the shared parent-owned resolver.

The upstream point (120,160) lies inside the interactive child and differs from the child's center. No production dispatch behavior changes.

Validation

Tested commit: 78b8dee5d8610c61d6113db40c4d69f4f969e901.

• pnpm check:affected --run passed.
• pnpm test:coverage:ci passed: 14,615 tests plus 11 fuzz tests, no unhandled errors. Changed-line coverage and touched-function CRAP checks passed.
• Owning runtime/contracts tests: 26 passed; unchanged upstream conformance fixture: 62 passed.
• Regenerated the upstream fixture with SHA-verified pinned jars, Gradle 8.10.2, and JDK 17.
• Mutation replacing the delivered parent center with an inset corner fails both new dispatch tests; source restored.
• Background prewarm is mocked at its established host port, preventing a late native import after test teardown. Covered owning/sibling lifecycle tests: 25 passed without unhandled errors; restoring the old mock fails all three port assertions. The original CI timing race did not reproduce locally.
• Independent reviews cleared the characterization and lifecycle fix. CI coverage passed on this head; remaining PR checks pending.