Basic Memory status

Report the plugin's current state for this project, then present a concise summary. This is a quick diagnostic, gather the facts and lay them out; don't over-investigate.

When no project is pinned, discover projects with bm_project(command="list") and pass the selected project's external ID as project on note/search calls. With several addressable projects, these calls require an explicit scope even when a default is configured.

Gather

1. CLI reachable? Run basic-memory --version, then bm --version, then uvx --prerelease=allow basic-memory --version. If no launcher resolves, report the CLI status as unavailable and continue with MCP/config checks. The plugin hooks can still use their uv-managed environment.

2. Configuration. Read the basicMemory block with the hooks' precedence. For the user-level base, append settings.json to the literal value of CLAUDE_CONFIG_DIR when that environment variable is present; do not trim it, expand ~, or treat an empty value as unset. Use ~/.claude/settings.json only when the variable is absent. Then the project's .claude/settings.json and .claude/settings.local.json override per key. Report the result, noting when a value comes from the user-level block versus the project:

   • From the basicMemory block: primaryProject (or note none is pinned, the listed default or sole project is selected explicitly), secondaryProjects (team/shared read sources), teamProjects (share targets for /basic-memory:bm-share), captureFolder (default sessions), rememberFolder (default bm-remember), preCompactCapture mode (default extractive), sessionProfile (default general), repository (coding profile only), captureEvents (default true).
   • From the root settings object (not basicMemory): whether outputStyle is basic-memory, i.e. whether the capture reflexes are on.