…faces

Every place this package gets discovered led with framing instead of with the
words people type. The GitHub About opened "YouTube for AI agents as one Agent
Plugin", the README h1 opened with the brand, and the manifest description —
the text plugin browsers show in search results — opened the same way. Someone
searching "youtube mcp" matched none of them early.

Reordered so the searched terms come first, without inventing claims:

- README h1: "TranscriptAPI — YouTube for AI Agents"
  -> "YouTube MCP + YouTube Skill for AI Agents", with the brand moved to the
  line directly beneath so attribution is not lost
- manifest description in plugin.json and all four per-client manifests, plus
  both marketplace indexes
- .codex-plugin interface displayName and shortDescription
- keywords: youtube-mcp and youtube-skill hoisted to positions 1 and 2

The GitHub About and repo topics are repo metadata, not files, so those were
set through the API rather than in this commit. The old About still advertised
"13 skills" — stale since the consolidation, and the more damaging half of the
problem, since it was the single most-read sentence in the repo.

Deliberately did NOT touch skills/youtube/SKILL.md's `description`. That field
is the agent's trigger-matching surface, not marketing copy — it is the only
thing loaded at startup when deciding whether to activate the skill. Stuffing
"YouTube MCP" into it would bias activation toward the literal phrase and away
from the natural-language phrasings it is tuned for. SEO and trigger vocabulary
are different jobs and should not share a field.

Also fixed a real defect while in the file. Step 3 asserted `format="text"` is
the default, unqualified. That holds on the MCP path only — the REST default is
`json`, and REST also defaults `send_metadata` to `false`. references/rest-api.md
already warned about exactly this, but references load on demand, so an agent
reading only SKILL.md and taking the REST path would omit the parameter and get
JSON with no metadata. Now states both defaults and says to pass them explicitly
on REST.

Bumped to 1.2.0 — new discovery copy plus a behavioural correction in the skill.

Verified: ajv `valid` for both manifests; skills-ref 1/1; check_conformance.py
11/11; all JSON and YAML parse; skill description unchanged at 732/1024;
SKILL.md 131/500 lines; all eight manifests agree on 1.2.0.

Co-Authored-By: CRHQ <noreply@crhq.ai>