docs: retarget binding to the LadybugDB org repo (+ LICENSE)#2
Merged
Conversation
The binding was adopted into the LadybugDB org as LadybugDB/ladybug-dotnet. Replace all personal-repo (sergey-v9) references in the living notes, the release workflow header, and the nuget RepositoryUrl with the org repo, and document the new ci.yml native-test matrix plus the v0.17.0 ENGINE_VERSION pin.
Collaborator
Author
|
@adsharma would you mind giving me collaborator access (Write / Maintain) to that repo so I can commit it right away, or do you prefer to keep me posting changes as PRs? Next, I plan to set up NuGet native package builds separately for different platforms and configure publishing them to NuGet feed. |
Contributor
|
@sergey-v9 I've added you to this repo with write access. But let's use the PR process like all other repos. Yes, Nuget packages will be great. |
Collaborator
Author
|
@adsharma Great, thanks. Got it, I'll do all further work through PRs. |
Contributor
|
@sergey-v9 I've also setup LadybugDB org on nuget and added permissions to release.yml to publish packages via the trusted publishing path. |
sergey-v9
added a commit
to sergey-v9/ladybug-dotnet
that referenced
this pull request
Jun 29, 2026
…phiti wishes LadybugDB#2, #6) Graphiti wants to drop its brittle "Index … already exists" message-catch idempotency workaround in favor of an explicit DROP_FTS_INDEX, and flagged that 0.18.0's BM25/FTS bookkeeping changes may move scores. Both are addressed in SearchExtensionsTests. LadybugDB#2 DROP_FTS_INDEX round-trip (new, version-tolerant): the DDL is new in engine 0.18.0/main, so the test Skips gracefully when the loaded native lacks the procedure (catches the Catalog/Binder "function does not exist" error from the first DROP_FTS_INDEX of an existing index) and validates for real when present — which it is against the dev-feed 0.18.0-dev native in CI's Test gate. Pins: (a) clean drop-then-create idempotency — recreate after DROP_FTS_INDEX succeeds and a subsequent QUERY_FTS_INDEX returns rows, the observable proof the aux docs/terms/appears-in tables were cleaned; (b) DROP_FTS_INDEX on a missing index throws LadybugQueryException, so a naive drop-then-create is not idempotent and a guard is still needed. Uses the FTS-specific procedure (generic DROP INDEX is not guaranteed to clean the FTS aux tables, and is not even parseable on some natives). #6 FTS ranking hardened: the existing test now asserts relevance-based, score-tweak-resilient properties — the clearly-most-relevant entity ranks first, scores are strictly descending, an irrelevant entity is absent — over a corpus shaped for unambiguous relevance, instead of any exact BM25 score. Survives the 0.18.0 scoring shift while a genuine ranking regression still fails it. No previously protected assertion was weakened. Verified against the locally staged native (which already carries the DDL): all 4 SearchExtensionsTests pass with 0 skips; full suite 262 passed / 0 failed / 0 skipped; Release build clean on both TFMs (0 warnings). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sergey-v9
added a commit
to sergey-v9/ladybug-dotnet
that referenced
this pull request
Jun 29, 2026
…hiti wishes LadybugDB#3, LadybugDB#5) Wish LadybugDB#5: add a structured `consumer_impact=` one-liner to upstream-engine.pin for the current pin (interop/fts_scoring/new_ddl/fixes/note), and make it a REQUIRED field on every bump in docs/upstream-sync.md — a new numbered pin-advance step plus the field format and per-field guidance, so consumers read the impact off the pin instead of re-deriving it each cycle. Wish LadybugDB#3: add a "D) Engine-feature backlog (needs upstream)" section to docs/upstream-sync.md recording the fixed-size FLOAT[N] parameter-binding ask: the binding cannot do it alone because lbug.h has no fixed-ARRAY value constructor (only lbug_value_create_list) and the header is byte-identical v0.17.1..main, so 0.18.0 adds none either; it needs an upstream lbug_value_create_array-style addition plus a typed binding helper. Until then the List<float> + CAST($v AS FLOAT[N]) path (pinned by Vector_InlineCosineSimilarity) is the supported route. Also append a "Response — 2026-06-29 (binding maintainers)" section to GRAPHITI_SEARCH_EXTENSIONS_FEEDBACK.md addressing all six wishes by number: LadybugDB#1 Linux from-source native build fixed (validated by next dev push), LadybugDB#2 version-tolerant DROP_FTS_INDEX round-trip, LadybugDB#3 engine-gated/backlogged, LadybugDB#4 Connection.ExecuteMany shipped, LadybugDB#5 consumer_impact added+required, #6 FTS ranking assertions hardened to a score-tweak-resilient cross-check. Docs-only; build clean (0 warnings, both TFMs), suite green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sergey-v9
added a commit
to sergey-v9/ladybug-dotnet
that referenced
this pull request
Jun 29, 2026
… + skip rebuilds on doc-only pushes The dev publish run #18 is green on all five RIDs (build-native -> publish -> consume-published), and the .lbug_extension files are verified present in the published LadybugDB.Native.<rid> nupkgs. Mark Graphiti wish LadybugDB#1 resolved at 0.18.0-dev.18.1.eng-d8277a8e5; note LadybugDB#2/#6 are now validated against the real 0.18.0 native (they run in the green Test gate). Also add a paths-ignore (**/*.md, docs/**) to the dev workflow so doc-only pushes don't trigger the ~1h cross-RID build+publish. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
LadybugDB/ladybug-dotnet. This PR removes every remaining personal-repo (sergey-v9/...) reference and retargets the docs/config to the org repo:.agents/notes/DECISIONS.md,HANDOFF.md,ROADMAP.mdrelease.ymltrusted-publishing header comment (owner=LadybugDB)nuget/nuget-package.propsRepositoryUrlci.ymlnative-testmatrix (added in0a8d3d2) and pins the docs toENGINE_VERSION = v0.17.0, matchingrelease.yml.D17recording the org adoption + native CI matrix.Ladybug Contributors.Notes
ENGINE_VERSIONare unchanged.Test plan
build-test(both TFMs + ABI/struct-layout guards + pack smoke) stays green.native-testmatrix (linux-x64 + win-x64) still loads the native engine and runs the suite withLADYBUG_REQUIRE_NATIVE=1.