Repository navigation
Publish NLPBridge 0.2 ONNX and catalog improvements - #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.
Publish the pending NLPBridge 0.2 implementation: compact operation cards, portable vector-cache encoding, catalog readiness diagnostics, model-bundle integrity checks and optional Python/Rust ONNX embedding adapters. Preserve the published
nlpbridgedistribution, public selection API and both CLI aliases; keep worktrees, leases and runtime state out of release archives.Validation: Python suites passed with both the Rust and Python index backends (66 tests each, including optional ONNX); Rust workspace passed 9 tests; the local execution example, built-wheel metadata/API/CLI checks, archive exclusions and all bundled checksums passed. Existing E5 measurement reports remain historical evidence, not a new semantic-quality or end-to-end LLM benchmark.
Ticket:
.planfile/tickets/ticket-002.yaml. The primary checkout and its staged files remain preserved; delivery is isolated onticket/002-publish-v02.