Release 0.2.7: accept MCP release details without names

[MainSequenceDev]

Valid FastAPI release details omit the discovery-only name, causing MCP add, tool listing, and calls to fail before initialization. Treat the release UID as the connection identity and keep name as optional display metadata, including in saved connections. Existing endpoint, metadata UID, credential-target, and access checks remain in place.

Prepare @dev-mainsequence/devtools@0.2.7 and the matching plugin manifest. The marketplace pin will advance after npm publication is verified. This hotfix is based on current main and excludes the separate OpenCode development work.

Validation:

• npm run release:check: 110 tests passed, with package and standalone-plugin archives built and the isolated npm consumer verified.
• The exact packed 0.2.7 npm archive discovered and added the deployed crm release whose detail has no name; a fresh client loaded its saved connection and listed all 70 tools.
• Regression fixtures now match nameless release details and cover nameless saved records, UID/metadata validation, removed capability, endpoint changes, and access denial.

Addresses #6.