Store Health Check

Diagnose issues with knowledge stores: missing paths, schema migrations, model mismatches.

Steps

1. Use the mcp__bluera-knowledge__execute tool with command "stores:health" to check all stores

2. Present results grouped by status:

## Store Health Report

### Errors (require action)
| Store | Type | Issue | Fix |
|-------|------|-------|-----|
| my-repo | repo | Path not found | Re-create store or fix projectRoot |

### Warnings (recommended action)
| Store | Type | Issue | Fix |
|-------|------|-------|-----|
| old-docs | web | Schema v1 | Run: /bluera-knowledge:index old-docs |

### Healthy
- react-docs (web)
- lodash (repo)

**Summary**: 2 healthy, 1 warning, 1 error

Exit Codes

The health check returns an exit code for scripting:

Issue Types

PATH_NOT_FOUND (Error)

The store's source path no longer exists. This happens when:

• A local folder was deleted or moved
• The project was relocated and paths weren't updated
• A cloned repo directory was removed

Fix: Re-create the store or update the projectRoot setting.

SCHEMA_V1 (Warning)

The store was created before model tracking was added. It needs to be re-indexed to be searchable.

Fix: Run /bluera-knowledge:index <store-name>

MODEL_MISMATCH (Warning)

The store was indexed with a different embedding model than the current configuration.

Fix: Run /bluera-knowledge:index <store-name> to re-index with the current model.

Check Single Store

To check a specific store only:

stores:health --store=<store-name>