feat!: align hot-path session memory with context-mode

[vicary]

Summary

• re-center the branch on an MCP-first session_* runtime, with in-process bounded execution, file processing, local indexing/search, and per-root-session corpus storage on Redis/FalkorDB
• keep session continuity and long-term memory split correctly: plugin hooks own canonical root-session resolution, event capture, <session_memory> injection, and native-tool enforcement, while Graphiti stays asynchronous and off the hot path
• harden runtime lifecycle and session-state behavior with shared teardown, temporary-root to canonical-root migration, bounded artifact/corpus overflow handling, and follow-up docs/config cleanup

Key Changes

• register an in-process session_* MCP surface from the plugin runtime: session_execute, session_execute_file, session_batch_execute, session_index, session_search, session_fetch_and_index, session_stats, and session_doctor
• add the local session corpus layer for normalized indexing, bounded search/snippet retrieval, fetched-content ingestion, artifact storage, and per-root-session stats in Redis/FalkorDB
• route large or risky work toward the MCP-first path via tool.execute.before / tool.execute.after, including native-tool guidance, argument rewriting, denial paths, and routing outcome metadata
• preserve shared session state across parent/child and temporary/canonical root transitions by wiring runtime-state migration through SessionManager, the session MCP runtime, and corpus storage
• retain the Redis-backed short-term memory + async Graphiti model: hot-path injection remains local/cache-backed, while Graphiti drain and cache refresh stay background-only
• refresh README/plans/tests to describe the MCP-first architecture, local-first injection semantics, Graphiti-optional behavior, and current validation surface
• update release workflow behavior in .github/workflows/publish.yml and .github/scripts/version.ts so publish gating, skip behavior, and tag/release creation stay consistent and idempotent even when npm publish is skipped

Testing

• add and expand focused Deno coverage for the MCP runtime, corpus, routing, runtime teardown, session migration, and hook integration paths
• covered suites now include src/services/session-mcp-runtime.test.ts, src/services/session-corpus.test.ts, src/services/tool-routing.test.ts, src/services/tool-guidance-cache.test.ts, src/services/tool-routing-outcome-cache.test.ts, src/handlers/tool-before.test.ts, src/handlers/tool-after.test.ts, src/session.test.ts, and related index/handler/service tests
• release/versioning coverage includes .github/scripts/version.test.ts

Notes

• this PR is no longer just the original Redis hot-tier rewrite; it now reflects the follow-up MCP-first replacement work and the later hardening passes on runtime lifecycle, corpus behavior, root-session migration, and release workflow handling
• current docs intentionally describe hooks as enforcement/continuity plumbing, not the primary execution surface; the primary path is the in-process session_* MCP runtime

[Copilot]

Pull request overview

Copilot reviewed 47 out of 101 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/config.ts:1

• coerceConfiguredUrl returns url.toString(), which normalizes URLs by adding a trailing / path when none is present (e.g. redis://host:6379 becomes redis://host:6379/). This is an observable behavior change that can break downstream parsing if any caller expects the original URL string format. Consider preserving the original candidate when it already has an explicit scheme (and is valid), or stripping the default / path when the input did not include one.

import os from "node:os";

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.