chore(release): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Minor Changes

• e7fefea: Add superadmin-controlled model allow-lists and bring-your-own-key (BYOK) support. Operators can now restrict which embedding profiles or narrator/guide model configs are usable, server-wide or per-org, via gitsema admin models list|allow|deny|reset --kind <embedding|narrator|guide> [--org <name>]. Independently, narrate/explain/guide (CLI, HTTP, and MCP) accept request-scoped BYOK credentials (--byok-http-url/--byok-api-key/--byok-model/--byok-max-tokens/--byok-temperature and equivalent HTTP/MCP fields) that bypass the allow-list entirely and are never persisted.
• 418779b: Add an identity/authorization audit log: sensitive actions (grant create/revoke, token create/revoke, login success/failure, org membership changes, repo org moves) recorded on the HTTP auth/orgs routes and queryable via gitsema audit log [--org] [--repo] [--limit]. Completes the Multi-Tenant Auth Track (Phases 122-125).
• 83b3de6: Add gitsema index doctor --fix: automatically backfills missing FTS5 content and garbage-collects orphan embeddings when those issues are detected, then re-reports index health — no need to run index backfill-fts/index gc separately.
• d2aa439: Add identity & credentials core for gitsema tools serve: user accounts with password login (gitsema auth login/logout/whoami) and long-lived API keys (gitsema auth token create/list/revoke), backed by new users/sessions/api_keys tables. The server's auth middleware now resolves these alongside the existing GITSEMA_SERVE_KEY/per-repo token mechanisms.
• fff805d: LSP textDocument/hover now enriches its semantic matches with optional Temporal (last touch/change frequency), Risk & quality (debt/hotspot/security), and Structure (caller/callee counts) sections when their data is available. Added textDocument/codeLens with per-symbol "Called N× · debt X.XX" annotations, and an opt-in gitsema tools lsp --diagnostics flag that pushes textDocument/publishDiagnostics notifications for high-debt/high-hotspot-risk files on a background timer (not supported together with --remote).
• fff805d: Added remote delegation for the MCP and LSP servers: gitsema tools mcp --remote <url> and gitsema tools lsp --remote <url> (with --remote-key/--remote-timeout, or GITSEMA_REMOTE/GITSEMA_REMOTE_KEY) now proxy every data-access call to a running gitsema tools serve instance via a new generic POST /api/v1/protocol/:operation route, with a startup health check that fails fast if the remote is unreachable.
• fff805d: Added a WebSocket transport for both protocol servers: gitsema tools mcp --websocket <bind-address> and gitsema tools lsp --websocket <bind-address> (e.g. --websocket 0.0.0.0:4242) listen on fixed /mcp//lsp paths, with --key <token> requiring a matching Authorization: Bearer <token> header. Unlike --remote delegation, WebSocket supports server push, so --diagnostics now works together with --websocket. gitsema does not terminate TLS — put a reverse proxy in front for wss://.
• fff805d: LSP textDocument/definition and textDocument/references now resolve structurally first when the knowledge graph (gitsema graph build) is built, returning exact matches instead of approximate semantic/text results (fallback results are now tagged tags: ['fallback']). Added three new LSP methods backed by the same graph: textDocument/prepareCallHierarchy, callHierarchy/incomingCalls, and callHierarchy/outgoingCalls, advertised via a new callHierarchyProvider: true capability.
• fff805d: Added gitsema tools mcp --http <bind-address> (e.g. --http 0.0.0.0:4242) — a proper MCP Streamable HTTP transport using the SDK's own StreamableHTTPServerTransport, listening on a fixed /mcp path with stateful sessions tracked via the Mcp-Session-Id header. --key <token> requires a matching Authorization: Bearer <token> header, same convention as --websocket. Unlike the non-standard --websocket transport (kept only for forward compatibility), Streamable HTTP is MCP's actual recommended network transport and should be preferred by clients/harnesses that need a network-reachable MCP server.
• 8bb2b62: Add multi-profile embedding serving: a gitsema tools serve deployment can now offer several named embedding profiles (provider/model pairs) at once via GITSEMA_EMBEDDING_PROFILES/the embeddingProfiles config key. Repos are pinned to a profile forever at first index (gitsema remote-index --profile <name>), and gitsema repos info <repo-id> shows the pinned profile. Servers with no profiles configured behave exactly as before.
• 8ff9b51: Adds orgs, personal groups, and repo/branch grants (Phase 123 of the multi-tenant auth track): every user now belongs to one or more orgs (an auto-provisioned personal org, or an explicit team org with org_admin/member roles), and repo access is granted per-user via repo_grants (read/write/owner, optionally scoped to a branch glob). New CLI: gitsema orgs create/list/members add/remove/list, gitsema users create/list, and gitsema repos grant/grants/revoke/move-to-org. New HTTP routes under /api/v1/orgs and /api/v1/repos/:repoId/{grants,move-to-org}.
• c0b059a: Add public repo sharing: persisted repos can now be flagged public (gitsema repos visibility <repo-id> public|private), auto-granting read access to non-owner callers who index an existing public repo, gated by a first-index allow-list (auth.allowPublicAutoIndex/GITSEMA_PUBLIC_AUTO_INDEX) and a per-user re-index throttle (auth.minReindexIntervalSeconds/GITSEMA_MIN_REINDEX_INTERVAL_SECONDS).
• 536fffd: Adds SSO/OIDC identity linking (Phase 124 of the multi-tenant auth track): a user can have an external (provider, externalId) identity linked alongside their password/API keys, all resolving to the same account. Providers must be explicitly allowlisted via GITSEMA_SSO_PROVIDERS. New operator CLI: gitsema auth sso link/unlink/list. New self-service HTTP routes: GET /api/v1/auth/sso and DELETE /api/v1/auth/sso/:provider/:externalId. The live browser-based OIDC login flow is not yet implemented — linking an identity is currently an operator action.
• c3cf147: Add a unified subgraph view (Phase 112) to graph neighbors, graph path, blast-radius, relate, similar, and hotspots: pass --out html:graph.html for an interactive force-directed graph (clicking a node shows its details and suggested follow-up commands), or --out text/--out markdown:graph.md for an ASCII tree / nested bullet list rendering, alongside each command's existing JSON and default text output.

Patch Changes

• 01ce44d: Extracted the duplicated 4000-char LLM-result truncation cap (previously a separate constant in guideTools.ts and llm/narrator.ts) into a single shared core/narrator/resultCap.ts helper. Also refreshed docs/feature-ideas.md — removed LSP/MCP remote-delegation, WebSocket, structural-navigation, and diagnostics/hover ideas that shipped as Phases 113–117, and added the still-undesigned plugin-API idea.
• 37edcbf: Deprecate gitsema index backfill-fts (and its existing top-level alias gitsema backfill-fts) in favor of gitsema index rebuild-fts. No index database predating Phase 11 remains in active use, so the Git-refetch behavior backfill-fts provided is no longer needed; both commands print a deprecation warning but keep working.
• 4d87c08: gitsema tools lsp --tcp is now deprecated in favor of --websocket --key: raw TCP has no request framing to carry a Bearer token in, so the unauthenticated---tcp gap flagged in review10 is closed by steering users to the already-authenticated WebSocket transport instead of inventing a bespoke handshake-auth protocol. --tcp continues to work unchanged but now prints a deprecation notice on every invocation.
• fff805d: Fixed two gaps in gitsema tools mcp --remote: the narrate_repo and explain_issue_or_error tools now delegate to the remote server like every other tool (they previously always ran locally), and --remote now also takes effect when combined with --websocket or --http (previously only the default stdio transport honored it).
• fff805d: gitsema tools mcp --websocket now prints a startup warning that raw WebSocket is not one of MCP's standard transports and is unlikely to work with most MCP clients/harnesses — it's kept for forward compatibility, not removed. A proper MCP Streamable HTTP transport is planned as a follow-up (see docs/PLAN.md Phase 117).
• bbfa34c: Postgres storage backend now probes the connection (SELECT 1) on first use, so a bad or unreachable storage.metadata.url/GITSEMA_STORAGE_METADATA_URL fails with an actionable error instead of an opaque driver error at the first query — mirroring the existing Qdrant connection probe. Also fixed a stale "in progress" roadmap heading and the recurring docs/features.md version-banner drift, now enforced by a test.
• e28d643: Closes out review10's remaining findings: the MCP WebSocket/Streamable HTTP listeners and the LSP TCP/WebSocket listeners now cap payload size and concurrent connections/sessions, and warn at startup when bound to a non-loopback address without a --key (with GITSEMA_WEBSOCKET_KEY/GITSEMA_MCP_HTTP_KEY env-var fallbacks for --key); tools lsp --tcp is documented as unauthenticated. hotspots' topK parameter is now capped at 500 on the HTTP route and MCP tool. regression-gate/code-review's git ref handling moved from shell-interpolated execSync to execFileSync with the same git-ref allowlist used elsewhere. resolveNode() now uses an indexed display_name lookup instead of a full graph scan, the HTML viz's client-side esc() helper now escapes quotes to match the server-side escaper, and gitsema cycles' DFS no longer risks a stack overflow on very long import chains.