MCP v1.4.0

Added

• 5 AI observability tools for AI components running on the connected
  instance and traces ingested via OpenTelemetry (#330):
  • ai_list_instances — superset discovery view of all AI component
    instances (semantic caches, agent caches, agent-memory stores, retrieval
    pipelines) with liveness and the latest stored metrics sample.
  • ai_instance_history — stored metrics time-series for one AI component
    instance (hits, misses, hit rate, cost saved, evictions, item count, index
    size, threshold) for spotting hit-rate degradation, growth, or drift.
  • list_ai_traces — list recent AI application traces (LLM calls, cache
    lookups, memory recalls, retrieval spans).
  • get_ai_trace — full span waterfall for one trace with timing, parent
    relationships, and attributes (model, cache hit/miss, similarity scores).
  • correlate_ai_trace — join a trace's cache/memory spans with live Valkey
    state (key existence, TTL, active threshold, index state) to explain
    unexpected cache misses or stale memory recalls.
• 3 analytics tools over the persisted metrics and anomaly stores (#331):
  • get_forecast — capacity forecast for a metric (opsPerSec,
    usedMemory, cpuTotal, memFragmentation) with projected time to
    ceiling.
  • get_latency_regressions — sustained p99 latency regressions vs baseline
    from the anomaly event store; companion to get_anomalies.
  • get_largest_keys — largest keys by measured memory usage from key
    analytics snapshots; companion to get_hot_keys. Requires BetterDB Pro
    (keyAnalytics).
• 2 vector-search tools for the Search module (valkey-search / RediSearch)
  (#332):
  • get_vector_indexes — per-index health: document count, memory usage,
    indexing failures, and percent indexed.
  • get_inference_latency — FT.SEARCH p50/p95/p99 per vector index plus SLA
    breach status. SLA fields require BetterDB Pro inference SLA monitoring.

Changed

• get_health / instance health now surfaces config-hazard advisories,
  including the default-user-enabled + AOF silent data-loss hazard
  (valkey#3983), with a distinct "could not verify" state (#337).
• README "Available Tools" updated with the new AI Observability, Analytics,
  and Vector Search sections.
• server.json registry version synced to 1.4.0 (it had drifted at 1.2.0
  through the 1.3.x line).

Pro tier

get_largest_keys requires BetterDB Pro (keyAnalytics) and the SLA fields of
get_inference_latency require Pro inference SLA monitoring. On community-tier
deployments the underlying endpoints degrade gracefully — sla is reported as
null and Pro-only endpoints surface the tier error to the agent.