Chunk -> embed -> upsert agent pages into the store (§9.3/§11).

Full geometry-safe re-index (reset + rebuild, §10.4/§11).

Embed query -> vector search -> ranked, attributed hits (§11).

Store stats. In-handler read-only init guard (§11/§6b.3).

Count-only by design: a status read reuses the warm memoized bundle when one exists, and on a cold process it never constructs the embedder (a full model load for sentence-transformers) — the count comes from a store-only client and the geometry metadata from the prior vectorstore-index artifact.

Diagnose vectorstore reachability + dimension (read-only; never writes).

This tool is inherently a dry-run diagnostic: it NEVER constructs the store client and NEVER writes to disk. It runs the §6.5 conflict matrix with two bounded, fail-closed live probes wired in:

• C3 (ollama unreachable): a GET to the configured ollama base_url within embed_timeout_seconds; any error/timeout warns + disables.

• C4 (Pinecone dimension): a describe_index lookup compared against the effective embedding dimension; a mismatch or any probe failure warns + disables (no index is ever created).

reachable reflects whether the vectorstore survives the conflict matrix (with the above probes folded in): chromadb-local is always reachable; remote/probe-gated backends are reachable only when no disabling conflict fired. dimension is the embedder's effective dimension when it can be built, else None.