Release v0.11.3 · GlitterKill/sdl-mcp

[0.11.3] - 2026-05-14

Added a dependency-free /ui/config visual configuration admin console with loopback-only write APIs, schema/semantic validation, redacted raw/effective snapshots, atomic save/backup/rollback, high-risk diff confirmation, and reusable JSON Pointer profiles.
Added opt-in phase timing diagnostics for sdl.context, sdl.workflow, sdl.runtime.execute, and sdl.file, plus observability aggregation for per-tool phase p95/max latency and LadybugDB query latency sampling.
Added sdl.context quality benchmark gates for lexical, confidence-gated default, and forced semantic retrieval recall, noise, and latency targets.
Added direct CLI metadata proxies for action.search and manual (including sdl. aliases) without graph DB initialization; sdl.context, sdl.workflow, and sdl.file remain MCP-only.

sdl.context now uses confidence-gated hybrid retrieval for unscoped natural-language requests; options.semantic: true forces hybrid, options.semantic: false preserves lexical-only behavior, and exact symbol or explicit scope lookups stay on the fast path.
Tool responses are now human-first across the MCP and CLI surfaces: visible content/terminal output is concise text, projected task data lives in structuredContent, and JSON-first consumers should switch to structuredContent or explicit JSON output modes.
Stdio server startup now defers file watcher initialization until after tool serving begins, avoiding watcher/DB contention on the first tool call.
LadybugDB stored-procedure row reads now materialize and close result handles under the per-connection mutex via a shared helper, improving latency accounting and avoiding leaked live query results.
Operator docs now distinguish foreground tool dispatch queue timeouts from background derived-refresh timeouts and document SDL_DERIVED_REFRESH_TIMEOUT_MS.

Bounded LadybugDB FTS retrieval by passing TOP separately from BM25 K in QUERY_FTS_INDEX calls.
SDL-MCP tool responses now include visible MCP content blocks for human-readable tool output, edit diff previews, and per-call token-savings meters instead of relying only on optional client logging notifications.
MCP content now defaults to model-facing projections that omit internal task IDs, cache/debug diagnostics, precondition snapshots, backup paths, live-index details, packed-wire stats, and duplicate sdl.context summaries unless the caller explicitly requests diagnostic surfaces; ETags remain visible for conditional follow-up calls.
file.write and search.edit apply responses now surface bounded before/after diff previews in visible tool output, matching search.edit preview behavior.