feat(plugin): 0.2.0 - connect to the hosted Aeon MCP server - #1181

Draft: hold until OpenAI finishes reviewing plugin 0.1.0. Only one review can be active per plugin, and a new package version is reviewed again.

What changes

• MCP server: plugin/.mcp.json (Codex and Claude Code, type: http) points at https://www.aeon.fun/connect/mcp, the hosted server in Aeon Connect (aaronjmars/aeon-connect#66, live and tested in ChatGPT). It has 17 tools: list_instances, switch_instance, list_skills, run_skill, list_runs, get_run, read_output, update_skill, read_memory, search_memory, read_strategy, update_strategy, read_soul, update_soul, setup_status (key names only), list_packs, install_pack (opens a PR through the install-skill run). In ChatGPT it also has a settings page (one switch per skill plus the harness), @ mentions of skills, and a live runs view on run_skill, list_runs and install_pack.
• Drops the orphaned portable plugin/mcp.json. chore(plugin): drop the agent-plugins manifest #1187 removed the portable plugin/plugin.json, so nothing read it anymore, and the Claude directory scanner has flagged that kind of file before.
• Onboarding: new skills/get-started skill, set as extensions.com.openai.onboardingSkill. It checks the connection with list_skills (and mentions list_instances / switch_instance only if switching was allowed), summarizes what is on, calls setup_status and names missing keys without asking for values, then runs heartbeat with the user: follows the run (live view or get_run), reads the result with read_output, or explains a failure. It confirms before any change: update_skill, update_strategy, update_soul, install_pack, switch_instance and the settings switches.
• Review info in extensions.com.openai.review, in OpenAI's format:
  • eight positive test cases: list skills, run and follow a skill, explain failures, schedule a skill, read a run's output (list_runs, read_output), check setup (setup_status), search memory (search_memory, read_memory), edit the north star (read_strategy, update_strategy)
  • three negative ones: secrets, deleting the repo, a repo the user did not allow
  • commerce: false
  • publication.release_notes covering the new abilities and switching
• Listing: version 0.2.0 in both manifests (.codex-plugin/plugin.json, .claude-plugin/plugin.json). New description, long description (887 chars), default prompts (adds "What does my Aeon agent still need to be fully set up?"), and capabilities Interactive, Read, Write. The long description says the connection reaches only the repo you pick, plus your other Aeon repos if you allow switching, and never reads or changes secrets.
• Marketplaces: the plugin description in .claude-plugin/marketplace.json and .agents/plugins/marketplace.json now reads "Run your Aeon agent from your coding agent: connect to it, run and schedule skills, and set it up with the operator console."
• README: "Connect your agent" section maps example asks to each tool, lists the ChatGPT extras, and states the scope and secrets rule.
• SECURITY.md: the plugin bundles no credentials and no telemetry; from 0.2.0 it points at the hosted server (OAuth with GitHub sign-in), which reaches only the repos you allow and can list missing key names but never read or write secret values.

Checked

• claude plugin validate plugin and claude plugin validate . pass.
• All touched JSON parses with jq.
• scripts/check-aeon-skill-sync.sh is OK; the operator skill is untouched (its references/mcp.md gets its own PR on main).
• .mcp.json uses type: http because Claude Code drops a URL server without a type. Codex accepts it: its own plugin fixtures use the same shape.

Before submitting (not in this PR)

1. Merge aaronjmars/aeon-website#585: the privacy policy covering Connect and connected apps, plus the /.well-known/openai-apps-challenge route.
2. In the portal, connect the MCP server, then set OPENAI_APPS_CHALLENGE in Vercel to the token it shows.
3. Give reviewers a test account that signs in without MFA or email codes. This is still an open question.
4. Record the demo video, then add review.demo_recording_url.
5. Upload the ZIP of plugin/.