Naragate v0.9.0 — naragate-mcp --local (embedded engine)

Naragate v0.9.0 — naragate-mcp --local (embedded engine)

The MCP server can now run the engine in its own process, so it needs no
backend process and no NARAGATE_BACKEND_URL:

pip install "naragate-mcp[local]"        # Python 3.12+
SECTORS_API_KEY=... naragate-mcp --local

LocalEngine starts the same FastAPI engine (uvicorn on a loopback port in a
daemon thread) and every tool routes through the existing REST client at that
in-process base URL — one engine, one Evidence Graph cache, one credit ledger.
Select it with --local, --embedded, or NARAGATE_ENGINE=embedded.

• The optional [local] extra pulls naragate-engine (with a
  python_version >= "3.12" marker so 3.10/3.11 installs stay resolvable and
  can still use a remote backend).
• Missing engine → a clear, actionable error.
• Embedded config comes from the environment (SECTORS_API_KEY,
  OLLAMA_BASE_URL, OLLAMA_MODEL); per-user tokens and bind_sectors_key
  don't apply to a single local user.
• Still prefer a shared engine? Run naragate-engine (or the
  ghcr.io/masdevid/naragate-engine image) and set NARAGATE_BACKEND_URL —
  unchanged.

naragate-mcp 0.6.0. Tests: mode detection, base-URL routing, missing-engine
error, and an in-process integration test that boots the real engine and calls
list_templates / get_setup_status (0 Sectors credits).