feat: repo-to-runtime intent and drift contract - #111
Draft
teckedd-code2save wants to merge 2 commits into
Draft
teckedd-code2save wants to merge 2 commits into
teckedd-code2save wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #110.
Adds the first repo-to-runtime contract primitive: parsing/validation for a
groundcontrol.yamlv1 intent manifest and deterministic drift findings against GroundControl's existing project topology. The first drift set covers missing project/service, port mismatch, and missing domain, with typed risk, evidence, reversible-action metadata, and Vitest coverage.This is deliberately a foundation for Loop, not a competing engine. Next wiring step is feeding manifest-derived intent into the existing intelligence/change-ledger/recovery flow.