Add scoped lineage declaration inspection - #72
Draft
Odenknight wants to merge 9 commits into
Draft
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.
Kosmos needs to distinguish unresolved lineage declarations without exposing hidden targets. This adds a read-only Engine adapter over parser-owned candidate tiers using a trusted host-supplied readable node set. Hidden targets behave like physical absence; output contains declaration coordinates and scoped status, without raw references or private candidate keys.
Validation: typecheck and build passed. The complete current lane reported 1,135 tests: 1,132 passed and three failed on the new export allowance and candidate inventory. Those contracts were corrected explicitly without changing frozen historical fixtures; all 20 relevant compatibility, inventory, and lineage tests then passed. Kosmos integration also passes its shared-native-bundle hidden/absent check. Hosted checks remain queued; installed-runtime qualification remains pending.