## Description of changes

Raise CPU resource limits and requests from 100m to 300m for all
services in both values.dev.yaml and values2.dev.yaml. The previous
100m limits were too restrictive for dev workloads, causing CPU
throttling.

Affected services: sysdb, rustFrontendService, queryService,
compactionService, rustLogService, garbageCollector, rustSysdbService,
and rustSysdbMigration.

## Test plan

CI

## Migration plan

N/A

## Observability plan

CI goes green

## Documentation Changes

N/A

Co-authored-by: AI

## Description of changes

Rename all test_live_cloud_* tests to test_k8s_integration_* so they run
under the existing k8s integration nextest profile instead of requiring
a
separate live cloud profile and credentials.

- Rename 29 test functions across chroma_http_client.rs and
collection.rs
- Remove the live_cloud nextest profile from nextest.toml
- Replace cloud API client config (dotenvy, CHROMA_ENDPOINT,
  CHROMA_CLOUD_API_KEY) with localhost:8000 default tenant/database
- Remove test_live_cloud_ from the default nextest exclusion filter
- Remove test-live-cloud GitHub action.

## Test plan

I ran `cargo test -p chroma` locally.

CI for the rest.

## Migration plan

N/A

## Observability plan

N/A

## Documentation Changes

N/A

Co-authored-by: AI

## Description of changes

I'd like this metric to track total dirty collections. I got 30k dirty
and it didn't move.

## Test plan

Eyeballs.

## Migration plan

N/A

## Observability plan

Watch on staging.

## Documentation Changes

N/A

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - Updated a few structs for `QuantizedSpannIndexWriter` to facilitate segment writer
  - Separated scrub and rebuild centroid logic from `commit` to a separate `finish`
  - Introduces the new `QuantizedSpannSegmentWriter`, under the feature flag
  - Updated the `VectorSegmentWriter` to use the new writer impl

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - Updated spann provider to spawn quantized writer with feature flag
  - Wire up the quantized writer spawning in compactor
- New functionality
  - N/A

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - Extended existing `test_persist` to use the reader impl
- New functionality
  - Introducing quantized spann segment reader

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - N/A
- New functionality
  - Wire up the quantized reader in a new quantized spann orchestrator. 

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

s## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - N/A
- New functionality
  - Wire up GC to clean up usearch binary files

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - N/A
- New functionality
  - Adds instrumentation and tracing for the index writer and segment reader

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

- Improvements & Bug fixes
- `DataChunk.len()` used to count the number of `visibility[i] = True`
values to compute the length(). This is inefficient to compute on every
invocation. The metadata log reader has a loop that invokes that invokes
this `len()` function for every fetched log record. This appears to
continue to take up > 40% of CPU on stack traces during gets on a high
number of log records. This change precomputes this length value to fix
this perf issue.
- New functionality
    - ...

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility
changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the_ [_docs
section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

A few fields in the CollectionInfo part of version files were not correctly filled in during MCMR compaction flush. This diff fixes that.

- Improvements & Bug fixes
  - ...
- New functionality
  - ...

## Test plan

Tests have been edited to test for the corrected fields.

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - Fixed broken links in README.md

## Test plan

_How are these changes tested?_

- No need

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility
changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - Fixed broken docs.rs link in getting-started.mdx (missing https://)

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Migration plan

_Are there any migrations, or any forwards/backwards compatibility
changes needed in order to make sure this change deploys reliably?_

## Observability plan

_What is the plan to instrument and monitor this change?_

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
- Apply materialized logs skips fts indexing if disabled in schema. Note
that it would still flush one empty block and a sparse index with one
entry (init state) and write this file path to sysdb. Chose this
approach for simplicity and due to less changes. Ideally the file path
should be absent in sysdb for fts, the writer/reader should not create
fts, etc.
- Query/Get/Search throws an error if user tries FTS/Regex in such a
case
- Rust client, Python client and JS client now allow setting this.
Previously the user would get an error if they try to disable FTS
- New functionality
  - ...

## Test plan

_How are these changes tested?_
Added unit tests and e2e tests
- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Migration plan
None

## Observability plan
None

## Documentation Changes
None