jif-oai be12a80ad1 feat: add normalized matching to memory search (#21205) ...

## Why

Memory search currently treats separators literally, so callers need to
know whether a stored term uses spaces, hyphens, or no separators at
all. That makes recall brittle for terms such as `MultiAgentV2` vs.
`multi agent v2` and `cold-resume` vs. `cold resume`.

## What changed

- Add an opt-in `normalized` mode to memory search that removes
non-alphanumeric separators after any requested case folding.
- Thread the new flag through the MCP `search` tool into the local
backend while keeping existing literal matching as the default.
- Reject queries that normalize to an empty string, and add regression
coverage for both normalized matching and that validation path.

## Testing

- `cargo test -p codex-memories-mcp`

2026-05-05 17:33:07 +02:00

..

src

feat: add normalized matching to memory search (#21205)

2026-05-05 17:33:07 +02:00

BUILD.bazel

feat: memories mcp v1 (#20622)

2026-05-04 13:51:03 +02:00

Cargo.toml

memories/mcp: generate tool schemas with schemars (#21012)

2026-05-04 18:40:17 +02:00