Tracer bullet for Task 2: resolve the minimal case with QVT-Operational

[ExtraToast]

Parent

#78

What to build

The first path through resolution in Java. A QVT-Operational transformation, run by the standalone executor, derives minimal's Resolved Deployment from its parsed Project Intent and the worked Platform document. The pipeline entry gains the resolve stage, and the parity suite exports the resolved dependency edges from the target model and compares them with minimal's committed dependencies.json. (Amended 2026-09-14 for the revised proposal, #102.) The model-driven Resolved Deployment holds typed resources, so it is not compared with resolved.json; a hand-written target model for minimal inside emf/ checks the transformation's output structurally. Mapping and helper names are the rule identifiers #47 defines, or provisional names noted for renaming if it has not landed. The QVTo smoke test from the walking skeleton is deleted.

Acceptance criteria

• minimal's resolved dependency edges, exported from the target model, equal its committed dependencies.json byte for byte.
• The transformation's output for minimal equals the hand-written target model kept inside emf/.
• Hashing is the only Java black-box the transformation calls.

Blocked by

• Model the Resolved Deployment target metamodel in Ecore #87