[codex] Allow project selectors by unique basename

[ScriptedAlchemy]

Summary

• allow registered-project selectors to resolve a unique bare project basename after exact project_id and alias lookup fail
• keep ambiguous or missing selectors fail-closed, with a more actionable error pointing to tracedecay_project_search
• add regression coverage for cross-project graph dispatch using project_selector.path = "target"

Root Cause

Agents naturally used short project names such as react-router, but MCP selector resolution only accepted registered project ids or exact registered path aliases. That caused registered project not found for selector even when a single registered project basename matched.

Validation

• cargo fmt --check
• git diff --check
• cargo test graph_reader_selector_dispatch
• manually verified installed MCP lookup for project_selector.path = "react-router" returns React Router symbols after daemon restart

[changeset-bot]

⚠️ No Changeset found

Latest commit: 764c309

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8533bd1d9a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".