Chain the Java pipeline end to end

[ExtraToast]

Parent

#78

What to build

The pipeline entry runs parse, validate, compose, resolve and render in one pass. Rendering reads the transformation's output instead of the hand-written target models. The parity suite then covers every oracle kind for every case through that one seam, and the double render over the same inputs is byte-identical.

Acceptance criteria

• Every case passes every oracle kind it carries through the single pipeline entry.
• Two runs over the same inputs produce byte-identical outputs.
• No stage test reads a hand-written target model as input any more.

Blocked by

• Widen the QVT-Operational transformation to every example #91
• Widen the Acceleo templates to every example #95