Move the parity suite onto the pipeline's file interface and make it a plain jar #129

Parent

#127

What to build

The parity suite decides every case from the files a run leaves behind, and holds no EMF type. With the imports gone the module needs nothing from the target platform, so it stops being an Eclipse bundle and builds as a plain jar. Its src/main helpers stay as they are; neither touches EMF.

Two gates have to survive the change rather than quietly stop enforcing. ArchitectureTest sees the other modules only because the manifest requires them, and with withOptionalLayers(true) an empty import makes EMF-010 and EMF-011 pass while proving nothing. A module that declares no dependency is also ordered by its reactor position alone, so the suite can run before the files it reads exist.

Decided in 0120.

Acceptance criteria

• No test in the module imports a type from cli or metamodel; every case is decided from files and an exit code.
• The module is jar packaging, with its META-INF/MANIFEST.MF and build.properties gone, and builds without the target platform.
• The module rules assert their imported class set is non-empty, and a fixture that empties the import fails them.
• EMF-010 and EMF-011 each fail on a fixture that breaks the rule, as 0104 requires.
• The layered rule no longer names the parity layer as a permitted accessor of the five bundles.
• Each case asserts its expected output file exists before comparing it, and a missing one fails as a missing file, not a skipped case.
• emf/docs/architecture.md's Parity section describes this, with no "proposed, not landed" note left on it.

Blocked by

• Write the parsed intent, the diagnostics and the descriptor as files the build leaves behind #128