test: QA integration tests + fix FTS5 query escaping

[EtanHey]

Summary

• 19 integration tests for Think/Recall/Sessions with real production DB
• Fix: FTS5 syntax error when query contains special chars (dots, dashes)
  • Wrapped terms in double quotes, joined with OR for lenient matching
  • Without this fix, queries like "implementing authentication" crash with apsw.SQLError

Test breakdown

• 5 session tests (no embedding, fast ~1s)
• 2 file-recall tests (no embedding)
• 6 think tests (with bge-large embedding, ~40s total)
• 3 topic-recall tests (with embedding)
• 3 MCP wiring verification tests

Test plan

• All 19 new integration tests pass
• All 48 existing tests still pass (no regressions)
• FTS5 fix verified — special characters no longer crash

🤖 Generated with Claude Code

---

Note

Medium Risk
Touches query construction for FTS5 MATCH, which can affect search correctness and recall; the new tests also depend on a large “production” DB and embeddings, increasing CI/runtime fragility even though logic changes are small.

Overview
Fixes hybrid keyword search crashes by escaping user query_text before passing it to FTS5 MATCH (quotes each term, strips embedded quotes, joins with OR, and falls back to * for empty input).

Adds a new test_think_recall_integration.py suite that runs against the production SQLite DB to validate sessions(), think(), and recall() behavior end-to-end (including embedding-backed paths) and verifies MCP tool registration/annotations.

^{Written by Cursor Bugbot for commit 5e7aa23. This will update automatically on new commits. Configure here.}

[coderabbitai]

Warning

Rate limit exceeded

@EtanHey has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 7 minutes and 31 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between a297f7e and 5e7aa23.

📒 Files selected for processing (2)

• src/brainlayer/vector_store.py
• tests/test_think_recall_integration.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch test/qa-think-recall

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Invalid FTS5 fallback * causes syntax error

Medium Severity

_escape_fts5_query returns a bare "*" for empty/whitespace queries and for inputs consisting entirely of double-quote characters. A standalone * is not valid FTS5 MATCH syntax — it's only valid as a suffix on a term (e.g. prefix*). Using it in WHERE chunks_fts MATCH '*' raises apsw.SQLError: fts5: syntax error, which is the same class of crash this PR aims to fix.

Additional Locations (1)

• src/brainlayer/vector_store.py#L63-L64