[codex] Fix vNext keyword memory retrieval

[samrusani]

Summary

This fixes the vNext context-pack retrieval path for committed memories that match the user query by keywords but not as one contiguous phrase. The Postgres store now searches memories and sources with an exact phrase first, then keyword fallback patterns, while preserving the existing domain and sensitivity filters.

Root Cause

search_memories() and search_sources() previously built a single ILIKE %query% predicate. Agent queries such as agent-first /vnext audit correction cockpit could exclude the intended memory before the Python ranker saw it, even though the memory had strong token overlap and domain=unknown was allowed by policy.

Validation

• ./.venv/bin/pytest tests/unit/test_vnext_store.py tests/integration/test_vnext_agentic_memory_commit_api.py -q
• ./.venv/bin/python -m py_compile apps/api/src/alicebot_api/vnext_store.py
• git diff --check
• Manual CLI context-pack check selected memory 138a27e2-4eec-48e7-b71d-ca10ef57caae with no retrieval warnings.

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.