[Laurianti]

Fixes GetAsync with a limit of 0 on a collection client made by name, when the collection does not exist.

• Before: a collection client made by name returned an empty list for GetAsync(limit: 0) without any request, also when the collection did not exist.
• Now: it reads its collection first, as the other reads do, so a collection that does not exist throws the same ChromaException. A limit of 0 still sends no get, since Chroma 0.6.3 would take it as no limit.
• Compared with the Python client: it sends the get with limit: 0 as it is, and on Chroma 0.6.3 gets every record back; this client sends no get, and throws when the collection does not exist.
• Tests: CollectionClientGetTests.GetWithALimitOf0ByNameOnACollectionThatDoesNotExist, which fails on main, on Chroma 1.5.9 and on Chroma Cloud; the get tests pass on Chroma 0.6.3 too.
• Docs: docs/queries-and-filters.md, and the column of the client in the KD-13 row of docs/COMPATIBILITY.md, which said "without a request".

[Copilot]

🟢 Approval recommended

The behavior, regression coverage, and documentation are aligned; only a non-blocking async-test cleanup remains.

1 open finding

• Remove unnecessary async from synchronous NUnit test · New

What changed in this PR

Fixes zero-limit reads for collection clients created by name by resolving the collection before returning an empty result.

Changes:

• Moves the zero-limit shortcut inside the collection operation wrapper.
• Adds regression coverage for nonexistent named collections.
• Updates query and compatibility documentation.

File	Description
ChromaDB.Client/​ChromaCollectionClient.cs	Resolves named collections before zero-limit returns.
ChromaDB.Client.Tests/​CollectionClientGetTests.cs	Tests the missing-collection behavior.
docs/​queries-and-filters.md	Documents zero-limit named-client semantics.
docs/​COMPATIBILITY.md	Updates the KD-13 workaround description.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.