fix(cli): memory health --project matches case-sensitively and fails silently (T-406) #314

Tracking T-406 (LOW).

The defect

memory health --project matches the project name case-sensitively. Against a store that holds the project alpha:

memory health --project ALPHA

returns an empty report — entry_count: 0, scope.projects: [] — while the report's project label still reads ALPHA. Nothing in the output says the filter simply did not match; the report reads like a project that genuinely has no memories.

The same applies to the MCP project argument and the studio's ?project= query parameter, because all three funnel through listForProject() in src/store.ts.

Why this is a defect and not a design choice

Exact matching is defensible; failing silently is not. The report's own contract — stated in scope and in .agents/skills/muse-health/SKILL.md — is that it never guesses. An empty report for a typo'd project name is indistinguishable from an empty project.

Suggested acceptance

Either:

• the match becomes case-insensitive (a strict superset of today's valid matches, so no existing match breaks), or
• the report gains an explicit line when the filter matched nothing.

The second option is the smaller change and keeps the exact-match semantics that list(store, { project }) already uses everywhere else.