Model the Resolved Deployment target metamodel in Ecore #87

Parent

#78

What to build

(Amended 2026-09-14 for the revised proposal, #102.) The target metamodel, due for Task 1 because Task 2 transforms into it and Task 3 generates from it. The proposal defines two metamodels, so there is no Deliverable Set package: the Deliverable Set is the generated files.

• A hand-written Resolved Deployment package holding every derived value of layer 2 together with the typed Kubernetes and extension resources, identities and output paths the templates write.
• A hand-written target model for minimal, kept inside emf/ as test input for the templates (Tracer bullet for Task 3: render the minimal case with Acceleo from its hand-written target model #94) and as the expected output of the transformation tracer (Tracer bullet for Task 2: resolve the minimal case with QVT-Operational #90). It is not an oracle.
• A canonical JSON export of the resolved dependency edges, the parity contract's dependencies.json shape.
• The target package is not part of the descriptor, which covers the source metamodel only.

Acceptance criteria

• The hand-written minimal target model validates against the metamodel, and its exported dependency edges equal minimal's committed dependencies.json.
• Every resource family in the proposal's generated-resources table has a typed class the templates can walk.

Blocked by

• Prove the five tools run headless: the walking skeleton #81
• Fix the oracle layout and commit the minimal case's oracles #82