Align AQE embedding setup, host configuration, and verification - #230
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
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.
AQE could be installed and registered while no semantic embedding backend was usable. This adds persisted backend selection, explicit local MiniLM provisioning, and owned environment updates for Claude, Codex, and OpenCode. Setup stops with actionable guidance when the selected backend is unavailable; existing choices and explicit opt-outs survive subsequent setup and sync.
Verification now uses the installed AQE runtime in isolation, compares stored SQLite provenance against its actual initialized identity, and distinguishes RVF contention from initialization/storage failures. Local-only transformer probes use the same ESM conditional export as AQE, preventing a second module instance from bypassing the no-download setting. Existing vectors are never relabelled or migrated.
The changes are split into intent, runtime verification, host projections, provisioning/lifecycle, documentation/clean-install CI, probe safety, and hosted-evidence commits. ADR-0055 and the user guide document the new-user default and alternatives. Native Ollama must be installed and running before selecting the local default; setup discloses the approximately 45 MB model download. OpenCode updates its owned AQE entry immediately without changing plugins or permissions.
Validation:
Ollama does not expose atomic create-if-absent for aliases. The installer rechecks inventory after download and preserves observed existing aliases, but cannot eliminate a concurrent alias-creation race.