Repository navigation
0.7: Extract qualification schemas while preserving gate contracts #300
Description
Activity
The schema work is prepared and reviewed in an isolated local draft, held for runtime prerequisite #299. No integration or completion is claimed yet.
Production commit
bb29556bfe3871bb9154ce77eadace6cb978474aadapts Pierre's8a146e35048c220adf12e9ccdd1c3a60483e034afrom #291, preserving Pierre Tholoniat's author identity, original author date and explicit provenance. The separate Elie-authored test commit isba76171fd3aee1f5de72827ea25e924ea1a0f6e4. The local draft worktree is clean.Four current qualification/audit class definitions move unchanged. Current runtime, image-pin, qualification, release-pairing and transition contracts remain intact; canonical functional models are re-exported rather than duplicated.
SourcePackageConfigsupports handwritten packages while all three generated SDK owners still requirespecification.Verification:
- RED: 14 assertion failures with 46 existing controls passing before implementation.
- GREEN: 62 config tests, 176 focused checks and 207 selected module-import checks.
- All 1,386 Citadel checks, configured Ruff and actual whole-builder strict Ty passed.
- Real current config values and 14 declared Linux-host plans match baseline across labels, edges, rendered commands, environments, artifact ownership and execution attributes.
- The sole schema difference is the inherited SDK required-field order:
specificationmoves from third to last and remains mandatory. Current production SDK checks read these fields by name; this difference is explicitly reviewed and tested. - Both production modules remain below the 300-line ceiling.
Declared-plan parity does not execute opaque callbacks or prove VM, package, publication or physical macOS behavior. The issue remains open pending #299, integration verification and the required final gates. The full sequence remains tracked under #289.
Parent: #289. Inspect source: #291.
Work boundary 2/13 from the approved 0.7 → clients → Inspect sequence.
Dependencies: #299.
Carry the schema extraction from #291 with Pierre’s authorship; preserve imports, serialized contracts, strict validation and gate topology.
Acceptance criteria:
Planned PR boundaries: Schema-only refactor before Inspect integration.
Implementation progress and evidence: Sprinty in the isolated
integration/0.7-clients-inspectworktree. Focused tests during development; fast checks/Citadel per PR; relevant black-box proof for runtime, credential or image boundaries. Respect the active release and machine locks.