feat(registry): generate client-specific install profiles

[JSONbored]

Summary

Install guidance is currently assembled from entry-level fields and category-specific metadata. Client-specific install profiles would make HeyClaude more useful for Claude Desktop, Claude Code, Codex, Cursor, Windsurf, Raycast, and other consuming tools.

Current state

• Entries expose installCommand, configSnippet, usageSnippet, copyable assets, and skill platform compatibility.
• MCP has get_client_setup, get_install_guidance, and get_platform_adapter.
• Raycast exposes copy/install/config actions but does not consume normalized client profiles.

Desired behavior

• Generate normalized install profiles per entry/client where enough metadata exists.
• Include command/config/snippet/source/trust/safety fields in a consistent shape.
• Expose profiles through registry artifacts, MCP install guidance, and Raycast detail/action surfaces.

Implementation notes

• Start with a small supported client set and explicit unsupported/manual statuses.
• Avoid inventing install commands where metadata is missing.
• Keep profiles deterministic and generated from content source fields.

Acceptance criteria

• Generated artifacts include client-specific install profiles.
• MCP install guidance can select a client profile.
• Raycast can display/copy profile-specific setup where available.
• Tests cover supported, manual, and missing-profile cases.

Validation

• pnpm test:registry-artifacts
• pnpm test:mcp
• pnpm validate:raycast-feed
• Add or update focused unit tests for the touched API/helper surface.
• Run the narrow relevant validation command for the changed package or route.
• Run git diff --check before opening a PR.