Repository navigation
Add four-document quality and context tooling - #3
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.
The shared quality and context toolchain now covers all four supplied specifications: bounded real-code retrieval, native opt-in OpenRouter Qwen3 embeddings/rerank, a durable local queue, offline token/asset processing, design checks, and project clients. Previously, the server had only partial adapters and the applications had no project-owned quality registry.
The four source documents are copied verbatim and keep their Markdown hard breaks via a narrowly scoped Git attribute. The new release builder creates a manifest-verified directory. A separate local activation has now switched the shared server launcher to that release, with the previous release and launcher retained for rollback; no website deployment was triggered.
Verification:
make verifypassed HIGH risk, 29/29 checks and 285 unit tests, with no skips. Real public-code OpenRouter smoke made four calls ($0.00049824 total), reused vectors on a changed query, and made zero calls on an exact repeat. The active release subsequently made native embedding and rerank calls on pinned public Redis code, and a repeated search made zero OpenRouter calls. Release v4, both project clients, offline U2Net cutout, and scratch old/new/old rollback were exercised. Seedocs/four-document-quality/completion.mdandacceptance.jsonfor the 142-section mapping and limits.A follow-up commit corrects the verification base on the first push of a new branch. The original push run compared the full repository tree and failed its whitespace/changed-secret gates; the PR run passed. The exact zero-SHA and normal-push selection paths, plus the full local HIGH gate, pass after the fix. GitHub
pushand PR verification checks passed on the follow-up commit.The user explicitly declined the repository's independent Sol review and requested integration/push. No such review is claimed. The canonical server
mainhas unrelated unpublished local commits and is not part of this push.