index_status returns project-not-found for project returned by list_projects

[edecarvalhoreis]

Summary

codebase-memory-mcp cli index_status can return project not found or not indexed for a project name that is returned by list_projects in the same environment.

Version

• codebase-memory-mcp 0.6.1

Reproduction

1. codebase-memory-mcp cli list_projects
2. Pick the returned project name, for example sample-project.
3. codebase-memory-mcp cli index_status '{"project":"sample-project"}'

Actual

index_status fails with:

{"error":"project not found or not indexed","hint":"Use list_projects to see all indexed projects, then pass the project name.","available_projects":["sample-project"],"count":1}

Expected

index_status should accept the same project id/name returned by list_projects and return status metadata.

Additional signal

index_repository may fail with pipeline.err phase=dump and a generic pipeline hint, which makes diagnosis difficult.

Impact

Breaks automation paths that depend on index_status for health/selector checks.

Suggested fix direction

• Align selector parsing for index_status with list_projects output.
• Surface concrete dump-phase failure reason (DB path/permission/state) instead of a generic hint.

[DeusData]

Thanks — and the giveaway was your own log: the error lists available_projects:["sample-project"] while claiming the same name isn't found. That happens because the two code paths disagree:

• list_projects (and the error helper) enumerate by opening the .db files directly.
• index_status/search_graph/etc. go through resolve_store, which first runs the name through cbm_validate_project_name (a security gate that allows only [A-Za-z0-9._-]).

The project name is derived from the repo path by cbm_project_name_from_path, which only replaced / and : with - — leaving spaces, @, +, unicode, parentheses, etc. intact. So a repo like /home/u/my project became the name home-u-my project: indexing created home-u-my project.db and list_projects showed it, but resolve_store rejected the space and returned project not found.

Fixed in commit 5595ce4: cbm_project_name_from_path now maps every character the validator would reject to - (plus collapses .. and strips leading dots), so a derived name always round-trips through resolve_store. Regression test project_name_always_validator_safe_issue349 asserts the invariant for paths with spaces, @, +, .., leading dots, and non-ASCII bytes.

One migration note: a project that was already indexed under an unsafe name still has a .db file with the old name, which will keep showing this mismatch. After updating, run index_repository once on that repo — it'll create the correctly-named DB. (You can delete the stale file from ~/.cache/codebase-memory-mcp/ if you like.)

Ships in the next release. Thanks for the precise repro!