chore(deps): bump dakera-client from 0.11.98 to 0.11.101

[dependabot]

Bumps dakera-client from 0.11.98 to 0.11.101.

Release notes

Sourced from dakera-client's releases.

v0.11.101

dakera-rs v0.11.101

Sync with server v0.11.97.

Version Bump

• Bump to v0.11.101, server v0.11.97 sync (#156, 8b08b35)

Server Compatibility

Compatible with dakera server v0.11.97. No breaking API changes. Metadata-only sync (CHANGELOG + version bump).

v0.11.100

Bug Fixes

• RecalledMemory.score now returns server-rank ordering — .score previously exposed the raw score field, which did not match the server's actual ranking key. The server ranks by smart_score (when present) → weighted_score → raw score, but the Rust SDK always returned raw score. Consumers sorting by .score saw incorrect ordering vs the server's returned rank. This was the root cause of invalid bench artifact score-gap analytics in dakera-bench (Core Engine finding, bench run 28550966828 showed 1251 adjacent score inversions in top-20). .score now resolves smart_score ?? weighted_score ?? score. (#154)

New Fields

• RecalledMemory.smart_score — optional f32, the server's primary ranking component. Present when the server includes it; consumers that need the raw component can read it directly. (#154)
• RecalledMemory.weighted_score — optional f32, the server's secondary ranking component. Exposed for parity with the server response schema. (#154)

⚠️ Behavior Change

.score values will change for existing consumers after upgrading to 0.11.100. If your code sorts or filters by .score, it will now correctly reflect the server's ranking order. This is a fix, not a breaking change, but validate downstream consumers (especially bench analytics) after updating.

Maintenance

• chore: bump version to 0.11.100, update CHANGELOG (6efeb200)

Full Changelog: Dakera-AI/dakera-rs@v0.11.99...v0.11.100

dakera-client v0.11.99

What's Changed

Server sync v0.11.96 — no SDK API surface changes; bundled with server v0.11.96 engine and routes-handler improvements (DAK-7243).

Full Changelog: https://github.com/Dakera-AI/dakera-rs/blob/main/CHANGELOG.md

Changelog

Sourced from dakera-client's changelog.

[0.11.101] - 2026-07-05

Changed

• Server sync v0.11.97 — no SDK API surface changes; bundled with server v0.11.97 security dep pins (quick-xml/memmap2), CI improvements (DAK-7362).

[0.11.100] - 2026-07-03

Fixed

• RecalledMemory.score now returns server-rank ordering — .score previously exposed the raw score field, which did not match the server's actual ranking key (smart_score → weighted_score → score fallback). Bench analytics and consumers sorting by .score saw incorrect ordering vs the server's returned rank. .score now resolves smart_score when present, then weighted_score, then raw score, matching the server. Callers relying on .score for ordering will see correct results after updating. New optional fields smart_score and weighted_score are exposed on RecalledMemory for consumers that need the raw components. (#154)

[0.11.99] - 2026-07-02

Changed

• Server sync v0.11.96 — no SDK API surface changes; bundled with server v0.11.96 engine and routes-handler improvements (DAK-7243).

Commits

• 8b08b35 bump: release v0.11.101 — server v0.11.97 sync (DAK-7362) (#156)
• 6efeb20 chore: bump dakera-client to v0.11.100 (smart_score fix, DAK-7328)
• cb97149 fix(recall): prefer smart_score as ranking key in RecalledMemory (#154)
• dbd3880 bump: release v0.11.99 — server v0.11.96 sync (DAK-7243) (#153)
• f44a0cb ci: add version gate to publish workflow (DAK-7231) (#152)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)