Move retrieval and integrations to Lean with checked contracts - #1
Merged
Merged
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.
Eggshell now runs retrieval selection, setup decisions, plugin packaging, and the independent harness adapters in Lean. Python is limited to FastEmbed inference and the existing NumPy kernels; the Codex engine does not import the adapter package. The README describes the experimental adapter boundary and the unchanged scope of the published token measurements.
The production functions carry 29 audited Lean contracts covering selection bounds and identity, preserved configuration, adapter ownership, terminal journaling, and delivery acknowledgements. Process tests cover interrupted saves, stalled search, chat isolation, compaction, four adapter protocols, and installation ownership. OS, numerical, and host-delivery boundaries are documented explicitly.
Validation on macOS: all core, lifecycle, package/setup, and adapter tests passed; all 24 legacy-provider comparisons passed across lexical, semantic, and hybrid modes; OpenCode output tests and all five public sample tests passed. Linux and macOS CI must also pass before the 0.1.0 runtime refresh.