v2.27.0

Add Codex and Gemini CLI install targets, MCP progress for long lookups,
display titles, a Claude Code marketplace, and MCP Registry metadata.

Tool Surface Changes

Tool surface changes: no CLI command or flag changes. recon mcp install --client
and recon doctor --client accept codex and gemini.

Added

• Publish MCP Registry metadata for io.github.blisspixel/recon. server.json
  is generated from the project version, and the README carries the PyPI
  mcp-name marker. The declared launch is uvx --from recon-tool recon mcp.
  The release job publishes that pointer with GitHub OIDC after PyPI parity.
  The artifact remains the attested wheel. (#321)
• Install recon for Codex and Gemini CLI. recon mcp install --client=codex
  writes [mcp_servers.recon] in ~/.codex/config.toml or .codex/config.toml,
  preserving sibling tables and comments. --force replaces only that table's
  span. The install does not write tool_timeout_sec or
  default_tools_approval_mode. recon mcp install --client=gemini merges
  mcpServers.recon into ~/.gemini/settings.json or .gemini/settings.json
  and omits autoApprove. recon doctor --client reads both files. (#323)
• Publish a repository Claude Code marketplace named blisspixel-recon.
  claude plugin marketplace add blisspixel/recon and
  claude plugin install recon@blisspixel-recon install the existing plugin,
  including its skills. The plugin still launches recon from PATH, so
  recon-tool remains a separate install. The marketplace file is generated
  from the plugin manifest and the project version. (#322)
• Advertise MCP display metadata. On mcp 2.0.0 and newer, server/discover
  and initialize serverInfo carry title recon, the package description,
  and websiteUrl https://github.com/blisspixel/recon. Every tool, catalog
  resource, and the domain_report prompt has a verb-first title. Names are
  unchanged, and recon publishes no icon. The v1.28.1 rollback pin forwards
  websiteUrl and those component titles. (#320)
• Send MCP notifications/progress from chain_lookup, a cache-miss
  lookup_tenant, build_review_bundle, cluster_verification_tokens, and
  compare_postures. Messages are stage names and counts. A client that
  resets its tool timeout on progress, or raises that timeout, can keep a
  depth 2 or 3 chain lookup alive. (#317)

Fixed

• Ignore a RECON_CONFIG_DIR that is relative or still contains an unexpanded
  ${...} placeholder. Cursor and VS Code leave ${PLUGIN_DATA} literal, and
  recon was writing cache and limiter state into that directory in the working
  directory. recon doctor and recon doctor --mcp warn and name the
  placeholder. An absolute path is unchanged. (#318)
• Advertise only MCP change notifications recon sends. On mcp 2.3.0 and newer,
  server/discover leaves listChanged and resources.subscribe false, and
  recon mcp doctor fails if a later SDK default turns them back on. Older v2
  SDKs still advertise the flags, so the same check warns and the 2.0.0
  compatibility floor stays in place. (#319)