🔀 chore: Merge latest main into PR branch

Author: Kendrick-Song

.github/workflows/ci.yml

@@ -126,6 +126,75 @@ jobs:
       - name: Integration tests
         run: make integration
 
+  integration-milvus:
+    name: integration tests (Milvus 2.6)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v8.2.0
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - name: Set up Python
+        run: uv python install 3.12
+
+      - name: Install dependencies (frozen)
+        run: make install-deps
+
+      - name: Start Milvus 2.6.22
+        run: |
+          curl --fail --location --retry 3 \
+            --output /tmp/milvus-compose.yml \
+            https://github.com/milvus-io/milvus/releases/download/v2.6.22/milvus-standalone-docker-compose.yml
+          docker compose -f /tmp/milvus-compose.yml up -d
+          for attempt in {1..60}; do
+            if curl --fail --silent http://127.0.0.1:9091/healthz >/dev/null; then
+              exit 0
+            fi
+            sleep 2
+          done
+          docker compose -f /tmp/milvus-compose.yml logs
+          exit 1
+
+      - name: Milvus repository contract
+        env:
+          EVEROS_TEST_MILVUS_URI: http://127.0.0.1:19530
+          EVEROS_TEST_MILVUS_FULL_STARTUP: "1"
+        run: uv run --frozen pytest tests/integration/test_milvus_remote.py -v
+
+      - name: Milvus /get truncation telemetry
+        env:
+          EVEROS_TEST_MILVUS_URI: http://127.0.0.1:19530
+        run: >-
+          uv run --frozen pytest
+          tests/e2e/test_get_endpoint_e2e.py::test_get_truncates_above_max_fetch
+          -v -k milvus
+
+      # The contract tests above exercise the repository port directly. This
+      # drives the same request path the application does -- /add, /flush,
+      # cascade, every search method, /get -- against the remote backend, so a
+      # break anywhere between the API and Milvus surfaces here rather than in
+      # production. Deselecting the LanceDB half keeps the job to its subject.
+      - name: Milvus end-to-end (tiered API suites)
+        env:
+          EVEROS_TEST_MILVUS_URI: http://127.0.0.1:19530
+        run: uv run --frozen pytest tests/integration/test_tiers -v -k milvus
+
+      # The structural half of the port contract runs in the ordinary unit job
+      # for both adapters. The behavioural half needs a server, so it only has
+      # a backend to compare against here.
+      - name: Derived-index port contract (both backends)
+        env:
+          EVEROS_TEST_MILVUS_URI: http://127.0.0.1:19530
+        run: uv run --frozen pytest tests/unit/test_infra/test_index_contract.py -v
+
+      - name: Stop Milvus
+        if: always()
+        run: docker compose -f /tmp/milvus-compose.yml down -v
+
   package:
     name: package build
     runs-on: ubuntu-latest

CHANGELOG.md

@@ -7,6 +7,93 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.3.0] - 2026-09-07
+
+**Milvus as an optional index backend, behind a port that hides which one you
+run.** The rebuildable BM25/vector index can now live in a remote Milvus Server
+or Zilliz Cloud instead of the embedded LanceDB, selected by one setting and
+verified at startup. Nothing about the default installation changes: LanceDB
+stays the backend, `pymilvus` stays an optional extra, and markdown stays the
+source of truth — the index is derived either way, so switching backends is a
+rebuild, not a migration. Both backends implement the same typed ports, so
+cascade, search and `/get` never branch on physical storage; a filter is a
+backend-neutral predicate tree rather than a rendered SQL string, which is what
+lets one set of contract tests hold both adapters to the same behaviour. The
+vector metric is now cosine everywhere, which corrects an inconsistency
+described under Changed.
+
+### Added
+
+- **Optional Milvus derived-index backend.** Install with
+  `pip install everos[milvus]` and select it with:
+
+  ```toml
+  [index]
+  backend = "milvus"
+
+  [milvus]
+  uri = "http://127.0.0.1:19530"   # or a Zilliz Cloud endpoint
+  token = ""                        # Zilliz Cloud API key
+  db_name = ""
+  consistency_level = "Session"     # Strong | Bounded | Session | Eventually
+  collection_prefix = "everos"
+  ```
+
+  Every field binds to an environment variable
+  (`EVEROS_INDEX__BACKEND`, `EVEROS_MILVUS__URI`, ...). The seven business
+  tables are created as `<collection_prefix>_<kind>`.
+
+  **Remote Milvus Server or Zilliz Cloud only.** A local database path is
+  rejected at startup rather than silently accepted: embedded Milvus Lite is
+  not supported, because its pure-Python rewrite degrades a single query to a
+  full scan and drops search-time parameters.
+
+  Startup verifies the physical collection field by field — datatype, primary
+  key, nullability, vector dimension, and the index metric (dense `COSINE`,
+  BM25 output fields) — so a collection that disagrees with the declared schema
+  fails immediately instead of at the first write or search.
+
+### Changed
+
+- **Vector search now uses cosine distance on LanceDB too.** The generic
+  vector path called `nearest_to()` without a distance type, so it ran on
+  LanceDB's L2 default while `agent_skill` recall and every Milvus query
+  already used cosine. All of them are cosine now. **Ranking can shift for
+  existing deployments** — the same vectors are scored by a different metric.
+  No action is required and no rebuild is involved; the index is unchanged.
+- **everalgo's transitive layer is pinned.** `everalgo-boundary`,
+  `everalgo-core` and `everalgo-clustering` are now direct `==` dependencies
+  matching the versions the test suite resolves. The consumer packages declare
+  them as `>=0.2.0,<2.0.0`, which treats a 0.x line as if only a major bump
+  could break compatibility, so a fresh resolution could pick releases the
+  suite had never run against. Raise them deliberately, together with a smoke
+  run against a PyPI-resolved install — `make package` installs the built
+  wheel with `--no-deps`, so it cannot catch a resolution break on its own.
+
+### Fixed
+
+- **`POST /api/v1/memory/add` no longer fails on a freshly resolved install.**
+  `everalgo-boundary` 0.3.0 added a third required field to the public
+  `DetectionResult` NamedTuple while `everalgo-agent-memory` 0.4.0 still built
+  it with two, so a default (`memorize.mode = "agent"`) install answered
+  `500 TypeError: DetectionResult.__new__() missing 1 required positional
+  argument: 'should_wait'`. Chat mode was unaffected. The pin above resolves
+  the compatible pair.
+- **Milvus datetime round-trips are exact below the millisecond threshold.**
+  Timestamps were written in milliseconds but read back through a
+  seconds-or-milliseconds heuristic, so any instant before 2001-09-09 either
+  landed in the year 30000 or raised `ValueError`. Physical column reads now
+  use an exact inverse.
+- **Concurrent `update()` on the Milvus backend no longer loses writes.** The
+  read half of the read-modify-write cycle sat outside the write lock, so a
+  backfill writing `vector` and a reflection writing `deprecated_by` could
+  overwrite each other on the same row. Both halves share one lock, and the
+  silent 10,000-row truncation on that path is gone.
+- **Milvus queries stay inside the engine's result window.** Row scans and
+  search `topK` are bounded by the 16,384-row ceiling instead of requesting
+  more and failing.
+
+
 ## [1.2.3] - 2026-08-07
 
 **Background maintenance that fails loudly instead of quietly.** A soak run on
@@ -946,7 +1033,7 @@ for AI agents.
 - **Decoupled algorithms** — memory extraction algorithms live in the standalone
   `everalgo-*` libraries published on PyPI.
 
-[Unreleased]: https://github.com/EverMind-AI/everos/compare/v1.1.4...HEAD
+[Unreleased]: https://github.com/EverMind-AI/everos/compare/v1.3.0...HEAD
 [1.1.4]: https://github.com/EverMind-AI/everos/compare/v1.1.3...v1.1.4
 [1.1.3]: https://github.com/EverMind-AI/everos/compare/v1.1.2...v1.1.3
 [1.1.2]: https://github.com/EverMind-AI/everos/compare/v1.1.1...v1.1.2