Prove the examiner's Eclipse import, before the Task 1 deadline

[ExtraToast]

Parent

#78

What to build

emf/README.md tells an examiner to set the target platform, import every module as an existing Maven project, open a metamodel, validate a model against its OCL document and run two launch configurations. Nobody has done that on a clean machine, so the instructions are untested where it matters most: they are read by a grader, once, under time pressure, and a red workspace is what the metamodelling report is read beside.

One known risk to settle rather than assume. Typed Java is generated from the genmodel during generate-sources by exec-maven-plugin, which has no m2e lifecycle mapping, so an import may leave the workspace full of unresolved types until a terminal build runs. Either the import works, or emf/README.md names the command to run first and says why.

This needs a human with Eclipse Modeling Tools; an agent cannot drive the IDE, which is why it carries no status: ready-for-agent.

Acceptance criteria

• A clean import of emf/ into Eclipse Modeling Tools, following emf/README.md verbatim, is recorded in a comment here: what worked, what did not.
• The workspace compiles, or emf/README.md names the step that makes it compile and why it is needed.
• The metamodels open, and the OCL document reports its invariant on the model the README names.
• Both committed launch configurations run and write their output.
• emf/README.md matches what actually happened, including the Eclipse version and the SDKs installed.

Blocked by

• None (can start immediately). Due before the Task 1 deadline, 2026-09-25.