spike(cli): carry the catalog's recommended field where Claude Code does not warn

[blafourcade]

Problem

claude plugin validate over our marketplace answers plugins[7].recommended: Unknown field 'recommended'. Claude Code ignores it at load time, on the source catalog and on every claude build, and CI now runs that validation on each pull request (#795). The field is ours: aidd setup and aidd plugin search --recommended read it to draw the curated install path. A warning that never goes away trains everyone to ignore the next one.

Scope

• Find where Claude Code's marketplace schema lets a catalog carry its own data (a metadata object, a namespaced key, or nothing).
• Decide: move recommended there, keep it and strip it from the claude build alone, or drop it and express the curated path elsewhere (the CLI's own list, a plugin category).
• Whichever is chosen, claude plugin validate over the source catalog and over the claude build passes with no warning of ours, and aidd setup still proposes the same plugins.

Acceptance criteria

• scripts/check-claude-accepts-build.cjs output carries no recommended warning
• claude plugin validate . at the repository root carries none either
• aidd setup and plugin search --recommended propose the same three plugins as before, golden snapshots updated only where the catalog's bytes moved

Prior art in this repo

• cli/src/contexts/tools/domain/marketplace-catalog.ts:94 copies recommended into every build; cli/src/contexts/framework/application/plugin/plugin-search-use-case.ts:50 reads it.
• scripts/check-claude-accepts-build.cjs and its test, added by feat(cli): one shared framework source per machine, user scope and session telemetry #795.

Out of scope

• strict, an official field since feat(cli): one shared framework source per machine, user scope and session telemetry #795.
• Codex, copilot and cursor catalogs: none of them warned on the field.