Repository navigation
Closed
Labels
area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.homelab-deploy, deploy-v2, manifests, and rollout flow.component: configConfiguration schema, defaults, or repo settings.Configuration schema, defaults, or repo settings.component: testsUnit, integration, system, or contract test concern.Unit, integration, system, or contract test concern.priority: P1High; important and should be handled in the current iteration.High; important and should be handled in the current iteration.status: ready-for-agentFully specified; an agent may take it with nobody watching.Fully specified; an agent may take it with nobody watching.type: featureNew user-facing or operator-facing capability.New user-facing or operator-facing capability.
Description
Parent
What to build
The first path through the whole Java seam: an authored project file in, a canonical parsed intent out, compared with the committed oracle.
- The Project Intent metamodel in hand-written Ecore, covering only what
minimaluses, with names fromCONTEXT.md. Genmodel Java is generated at build time. - The Xtext grammar for the YAML subset
minimaluses, importing that metamodel. - The
metamodel,syntaxandclimodules. The pipeline entry takes a case and yields the canonical intent. - The parity suite, table-driven over cases, asserting each oracle kind a case carries through the pipeline entry. Today that is one case and one kind.
- The Ecore and Xtext smoke tests from the walking skeleton are deleted.
Acceptance criteria
- The Java canonical output for
minimalequals its committed intent oracle byte for byte. - Changing one field in
minimal's project file fails the parity suite. - YAML outside the grammar's subset is refused with a diagnostic, never a guess.
- Every scaffold gate holds over the new modules.
Blocked by
Metadata
Metadata
Assignees
Labels
area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.homelab-deploy, deploy-v2, manifests, and rollout flow.component: configConfiguration schema, defaults, or repo settings.Configuration schema, defaults, or repo settings.component: testsUnit, integration, system, or contract test concern.Unit, integration, system, or contract test concern.priority: P1High; important and should be handled in the current iteration.High; important and should be handled in the current iteration.status: ready-for-agentFully specified; an agent may take it with nobody watching.Fully specified; an agent may take it with nobody watching.type: featureNew user-facing or operator-facing capability.New user-facing or operator-facing capability.
Activity