Files
Chris CoutinhoandClaude Opus 4.8 d883052fb8 feat: add opt-in MCP decomposition hook points (design §10)
Adds the seven §10.2 hook-point modules + five env vars so Astrolabe Cloud can
offload document processing to the external document-processor / embedding
gateway. Purely additive: with every setting unset the server behaves exactly
as today, so self-hosters are unaffected (Deck #92).

Hook points (all default to current monolith behavior):
- config: EMBEDDING_PROVIDER, INGEST_MODE, STATUS_BACKEND,
  COLLECTION_METADATA_SOURCE, FACT_EVENT_EMITTER (+ supporting settings),
  validated in Settings.__post_init__ (fail-fast STATUS_BACKEND=local with
  INGEST_MODE=external); shared canonical.py.
- vector/payload_keys.py + acl_hash.py: cross-impl NAMESPACE/point_id (§2.2)
  and BLAKE2b-128 ACL hash (§11), pinned by fixtures shared with the
  document-processor repo.
- embedding/gateway_client.py: OpenAI-compatible GatewayProvider authenticating
  via M2M OIDC client-credentials (separate realm); manual-only registry entry.
- vector/collection_metadata.py: sentinel-point / API metadata source with env
  fallback.
- vector/queue/: hexagonal ingest producer ports + memory/NATS adapters
  (Postgres seam); INGEST_MODE=external publishes mcp.ingest.requested.{tenant}
  instead of the in-memory stream and skips the in-process processor pool. The
  lifespan becomes a composition root across both deployment branches.
- vector/queue/status.py: STATUS_BACKEND=bus subscriber feeding a StatusStore
  the vector-sync status endpoint reads.
- admin/payload_backfill.py: POST /api/v1/admin/payload-backfill (admin scope);
  processor writes the new payload keys; query-side ACL pre-filter gated behind
  ACL_PREFILTER_ENABLED (default off).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 13:13:25 +02:00

45 lines
1.5 KiB
Python

"""Drift guard for the cross-implementation point-ID namespace (design §2.2).
The MCP server and the external document-processor must compute identical chunk
point IDs. This test pins the NAMESPACE against a fixture checked into both
repos; the processor repo runs a mirror of this test against the same fixture.
"""
import uuid
from pathlib import Path
from nextcloud_mcp_server.vector import payload_keys
FIXTURE = Path(__file__).parents[2] / "fixtures" / "namespace_uuid.txt"
def test_namespace_matches_fixture():
assert str(payload_keys.NAMESPACE) == FIXTURE.read_text().strip()
def test_point_id_deterministic():
a = payload_keys.point_id("t", "d", 0)
assert a == payload_keys.point_id("t", "d", 0)
assert a != payload_keys.point_id("t", "d", 1)
assert a != payload_keys.point_id("t2", "d", 0)
def test_point_id_exact_value():
# Pins the canonical-JSON name + uuid5 formula so a refactor that changes
# key ordering or encoding is caught (would silently break idempotency).
expected = str(
uuid.uuid5(
payload_keys.NAMESPACE,
'{"chunk_index":0,"doc_id":"d","tenant_id":"t"}',
)
)
assert payload_keys.point_id("t", "d", 0) == expected
def test_payload_key_constants():
assert payload_keys.EMBEDDING_IDENTITY == "embedding_identity"
assert payload_keys.ACL_HASH == "acl_hash"
assert payload_keys.PROCESSOR_VERSION == "processor_version"
assert payload_keys.PARSED_AT == "parsed_at"
assert payload_keys.PIPELINE_TIER == "pipeline_tier"