Split the compiler's mixed modules by concept, with no change of behaviour #376

Parent

Rewrite the spec and the compiler in place, release 1.0.0, and hand over every Project

What to build

The compiler takes the structure Decide the compiler's structure after the rewrite settled: stage folders and their dependency rules stay, and inside the model, check and resolve stages each concept chapter has one module. After it, a chapter pull request edits at most one module per stage.

This pull request moves code and changes no behaviour.

Acceptance criteria

• The six modules that carry five or six concepts are split by concept chapter, and the Kubernetes adapter's render module is split by object kind.
• Outputs that are not Deliverables (the Flux pin sources, and the generator of the node contract, the label set and the host data) sit in one new step that imports the model and the object types and no other step. Its name is settled against CONTEXT.md.
• The architecture document follows the code: the four ports it names and nothing declares leave it, the adapter registry is described as closed and in-tree, and concept modules inside the stages are stated.
• One new check holds the architecture document's Layers table to the dependency rules, with a ledger row and a failing fixture.
• RULE-046 and RULE-047 are enforced, each with a fixture, and the rule ledger has no pending row.
• The coverage thresholds are raised to what the suite reaches.
• 0056 and 0058 are rewritten in place; 0058's file is renamed to match what it now decides.
• The suite, the rendered trees and the resolved artifacts are byte-identical before and after, and no test file is edited.
• One full mutation run shows no test lost its target.

Blocked by

• Reshape the decision register: retired numbers, three folds, and citations checked in code