Split emf/ into a bundle tier and a test tier #130

Parent

#127

What to build

The listing says which modules a course examiner opens. bundles/ holds the five Tycho builds Eclipse imports; tests/ holds the parity tier Maven alone runs. Directory names stay short, since Eclipse names an imported project from its artifactId regardless.

Every document that names a module by its old path moves with it in the same commit. The rule ledger is the one that breaks the build if it is forgotten: Ledgers.checkRules fails the moment a row's named file is not where the row says.

Decided in 0121.

Acceptance criteria

• The reactor names bundles/… and tests/…, and ./mvnw -B -ntp verify is green from emf/.
• test/emf-wiring.test.ts passes unchanged, since it reads the reactor's entries rather than assuming a depth.
• The rule ledger, the witness list, the root architecture, the refusal examples' README and the two root tests that name a parity path all name the new one.
• emf/README.md carries one table: artefact, where it lives, which course task grades it, and how an examiner opens it.
• emf/docs/architecture.md's Modules section describes the two tiers, with no "proposed, not landed" note left on it.
• CodeQL's Java configuration and .github/CODEOWNERS still match the tree.

Blocked by

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