[ENHANCEMENT] Codebase_Search should trim project paths

[jeepshop]

Problem (one or two sentences)

Some models seem to think they need to pass the absolute workspace path to the codebase search. However if they do that, the codebase search won't return any results. However if I instruct the LLM to try again with a relative path, then the search works.

Context (who is affected and when)

This happens often with Qwen 3.5, but I've seen other model decide to use the full workspace path when trying to search the code base.

Desired behavior (conceptual, not technical)

It would be great if the codebase_search tool could detect the use of an absolute workspace path and auto-convert in into a relative path that it really needs.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Problem: When an LLM passes an absolute workspace path (e.g., /home/user/project/src/components) as the path parameter to codebase_search, the vector store filtering fails because stored path segments are relative. The absolute path gets split into segments like ["home", "user", "project", "src", "components"] which don't match the stored relative segments ["src", "components"].

Proposed fix -- modify CodebaseSearchTool.ts to normalize the path parameter:

1. In CodebaseSearchTool.execute() (around line 23), after extracting directoryPrefix from params, check if it is an absolute path using path.isAbsolute()
2. If it is absolute and starts with the workspace path (task.cwd), convert it to a relative path using path.relative(task.cwd, directoryPrefix)
3. This follows the same pattern already used by SearchReplaceTool and EditFileTool for their file_path parameter
4. Apply the same normalization in handlePartial() for consistent UI display
5. Add unit tests for the new path normalization behavior

This is a minimal, targeted change that handles the most common case (LLM passes the full workspace path) without affecting any other code paths. The existing downstream normalization in search-service.ts and qdrant-client.ts (handling ./, ., trailing slashes, etc.) remains untouched.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.