Unit tests and lint
tests/fixtures/. They never read the real vault and never call Notion or Google.
Trying changes against real data
Use a copy, never the live vault.- Use a different port from the live app.
- Do not set
NOTION_TOKENin the test shell, and do not runbrain sync notionin a copy. - Add
BRAIN_READONLY=1to test the read-only behaviour.
What the agent layer was tested against
On a copy of a 1,600-note vault, 36 checks passed across the three entry points:- CLI: current-state and topic briefings, budgets of 200, 600 and 3,000 tokens, topics with no page, JSON output, and every command in the skill file.
- MCP: start-up, tool listing,
brain_context,brain_skill,brain_get,brain_ask. - HTTP: requests without a token are refused;
/api/context,/api/skill,/api/askand/api/searchreturn the same content as the CLI.
What the Google Drive connector was tested against
A local server that imitates Google’s token and Drive endpoints. 14 checks passed: both credential types, paged listings, a retry after a503, nested folders, Markdown and plain-text export, skipped file types, unchanged documents, changed and renamed documents, and a failure partway through followed by a clean retry.
It has not been run against Google itself.