[AdirAmsalem]

Summary

The server now resolves lucy-latest to lucy-2.6 instead of lucy-2.5 (DecartAI/api companion PR). The fast-mode warning in models.py, the docstring in realtime/types.py and README.md listed lucy-2.5 / lucy-latest as a pair. They now pair lucy-latest with 2.6. No behavior change.

An earlier CI run failed Test Python 3.14 in test_verify_rejects_tampered_signature, and it passes on the latest push. That test is flaky on its own, independent of this PR: it picks the replacement character based on signature[-1] but overwrites signature[0]. When the signature already starts with that character, the token comes out unchanged.

Link to Devin session: https://app.devin.ai/sessions/e0721d006eec47b3a020d92511e1194b
Open in Devin Desktop: https://app.devin.ai/desktop/session/e0721d006eec47b3a020d92511e1194b?variant=devin
Requested by: @AdirAmsalem

---

Note

Low Risk
Documentation and warning string updates only; no runtime or API logic changes.

Overview
Updates documentation and warning text to reflect that lucy-latest now maps to lucy-2.6 (not lucy-2.5) on the platform. The fast-mode model list in README.md, the RealtimeConnectOptions.speed docstring in decart/realtime/types.py, and the unsupported-speed warning in decart/models.py now group lucy-2.6 / lucy-latest together and list lucy-2.5 separately. No SDK behavior changes—aliases are still sent as-is; only user-facing wording is aligned with the server.

^{Reviewed by Cursor Bugbot for commit 22320d1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[decartdev]

LGTM (approved at Adir's request).