This PR adds an optional `all_projects` boolean to `mem_search` so callers can request cross-project lookup, while keeping default behavior unchanged when the flag is omitted or set to false.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Introduced a concrete cross-project search path in the MCP layer by extending `mem_search` schema with `all_projects` and updating `handleSearch` to bypass project resolution when global search is requested.
Developers and operators can now retrieve memory search hits across multiple projects with a single `mem_search` call, so cross-project workflows no longer require repeated per-project queries or manual project switching; this is especially useful for debugging and agent operations that span project boundaries. The change is implemented in MCP request parsing and handler logic, which now routes `all_projects: true` to project-agnostic lookup while preserving existing scoped behavior for `false`/unset, so the next signal to watch is whether global results stay bounded by intended access controls and whether large multi-project queries introduce response latency or result-volume surprises.
Developers and operators can now retrieve memory search hits across multiple projects with a single `mem_search` call, so cross-project workflows no longer require repeated per-project queries or manual project switching; this is especially useful for debugging and agent operations that span project boundaries. The change is implemented in MCP request parsing and handler logic, which now routes `all_projects: true` to project-agnostic lookup while preserving existing scoped behavior for `false`/unset, so the next signal to watch is whether global results stay bounded by intended access controls and whether large multi-project queries introduce response latency or result-volume surprises.