InterLock 1.0.0-rc.15

Fixed

• After a Redis restart, the gateway and admin could stay unready until
  their pods were restarted. The cache-invalidation and FAISS pub/sub
  listeners caught the dropped connection, then failed in their own cleanup,
  which sent UNSUBSCRIBE to a server that was still down; the listener ended
  and /ready reported it unhealthy for good. On the DigitalOcean rehearsal a
  managed Valkey restart left both services serving 503 for about 41 hours.
  The listeners now close a dropped subscription without that command, never
  let a cleanup error escape, and resubscribe when Redis is back. An
  end-to-end test restarts Redis and requires both services to become ready.

Changed

• Dependency updates: 25 patch releases (among them pydantic 2.13.5,
  cryptography 50.0.2, joserfc 1.7.5, msgpack 1.2.3, snowflake-connector
  4.8.0), OpenTelemetry 1.45 / 0.66b0, authlib 1.8.0 (minimum now 1.7.1, the
  fix for two open-redirect advisories in its OAuth server code, which
  InterLock does not use), and the ml extra's torch 2.14.1, transformers
  5.18.0, faiss-cpu 1.15.1 and spaCy 3.8.16. sentence-transformers stays on
  5.x.

Documentation

• The MCP clients guide covers Codex CLI, the OpenAI Responses API, the
  Gemini Interactions API and google-genai SDK, and the Anthropic API's MCP
  connector, each with a working configuration, and records what was tested
  against a live deployment on 2026-10-04 and how each client shows a refusal.