@ file picker: file paths not shown in search results, making disambiguation hard

Summary

When using the @ file reference utility to attach a file to a message, the search results show only the filename without the directory path. This makes it impossible to distinguish between files that share the same name across different subdirectories.

Steps to Reproduce

1. Open Claude Code in VSCode
2. In the message input, type @ followed by a filename that exists in multiple locations (e.g. endpoints.md, README.md, index.ts)
3. Observe the search results dropdown

Expected Behavior

Each result in the dropdown should display the full relative path (or at minimum the parent directory) alongside the filename — e.g.:

• plans/api/endpoints.md
• docs/endpoints.md

Actual Behavior

Only the bare filename is shown (e.g. endpoints.md), with no path context. When multiple files share a name, the user cannot tell which one to select.

Workaround

Typing part of the parent directory path (e.g. plans/api/endpoints) in the search query does surface path context in results — but this requires the user to already know the path, defeating the purpose of the search.

Environment

• Claude Code VSCode Extension
• macOS

Request

Show the relative file path in the @ picker results for every entry, not just the filename. A common pattern (used by VS Code's own Quick Open, Telescope in Neovim, etc.) is to show the filename prominently with the path dimmed beneath or to the right.