feat(landing): lead with MCP, not Claude, on the public pages

[jfrench9]

Summary

The public pages stop leading with Claude. RoboInvestor works from any MCP client, and the in-app AI no longer runs on Claude alone, but the hero said RoboInvestor "combines Claude AI" with the graph, the trust row carried a "Claude AI" badge, and the MCP lines named only Claude Desktop and Cursor. This matches what robosystems-app and roboledger-app (RoboFinSystems/roboledger-app#383) already did.

Changes

• Hero (HeroSection): the body pairs RoboSystems' knowledge graph with "Claude, ChatGPT, or any MCP client". The Agent-Managed Portfolio card names the same clients. The trust badge is the Model Context Protocol mark with "Works with any MCP client".
• AI analysis section (AIAnalysisSection): steps 1 and 4 say "the AI" instead of "Claude AI". The footer credits the Analyst Operator, which step 2 already names, and the MCP note names Claude, ChatGPT, or any MCP client.
• Features, research, schema, final CTA (FeaturesSection, ResearchSection, InvestorSchemaSection, FinalCTA): "AI-powered" research console, "your AI assistant reads and writes your graph", "Built for MCP clients from the ground up", and "from the AI assistant you already use, built on RoboSystems".
• Research pages (CompareYourCompany): "ask your AI how your margins and growth compare".
• Home ((app)/home): the getting-started card is "Connect your AI via MCP", and it and the checklist name Claude, ChatGPT, Cursor, or any MCP client.
• src/components/mcp/McpLogo.tsx is new, the same component the other two apps use. public/images/claude.svg is removed, since nothing references it now.
• README follows.
• The repository getting-started page keeps its per-client recipes (Claude connectors, claude mcp add, Cursor), which are instructions for those clients.

Deploy Notes

None.

Testing

• The pre-commit gate passed on the commit: vitest (28 files, 189 tests passed), plus format, lint, and typecheck.
• Rendered / on next dev: the hero, trust badge, analysis footer, features, and final CTA show the new copy. "Claude AI", "Claude Desktop" and claude.svg no longer appear.
• npm run build: not run.

🤖 Generated with Claude Code

[github-actions]

Change classification: normal — platform or application code changed.

A normal change carries a documented automated review on this pull request before merge, in place of a second human approver. The change-classification job requests that review and passes once it has been posted. Recorded by the change-classification job.

[jfrench9]

@claude please review this PR

[claude]

Claude finished @jfrench9's task in 1m 18s —— View job

---

Reviewing PR #331

• Gather context (diff, changed files)
• Read changed files in full
• Review copy/content changes
• Review new McpLogo component
• Check for stale references (e.g. claude.svg, "Claude AI" leftovers)
• Post review feedback

Review

Clean, well-scoped copy change that matches the approach already taken in robosystems-app and roboledger-app. No functional risk here — purely presentational text/asset changes.

What looks good:

• grep -rn "claude.svg\|Claude AI\|Claude Desktop" across src/ and public/ comes back empty — no stale references left behind.
• New McpLogo component (src/components/mcp/McpLogo.tsx) is a simple stroked SVG using currentColor, marked aria-hidden, and paired with a visible text label everywhere it's used (HeroSection.tsx:146-147) — good, avoids an a11y gap now that the descriptive alt="Claude AI" on the old <Image> is gone.
• Messaging is consistent across the funnel: hero → AI analysis section → features → schema → final CTA → home dashboard all now say "Claude, ChatGPT, or any MCP client" / "the AI" rather than singling out Claude, and step 2 in AIAnalysisSection.tsx already named "Analyst Operator" so the footer change (AIAnalysisSection.tsx:159-161) ties back to an existing term rather than introducing a new one.
• Repository getting-started page correctly keeps its per-client instructions (Claude connectors, claude mcp add, Cursor) since those are literal client-specific setup steps, not marketing copy — good call to scope the change to public-facing pages only.
• README.md updates are consistent with the component changes.

Minor/non-blocking observations:

• HeroSection.tsx:24-31: "RoboInvestor pairs RoboSystems' knowledge graph with Claude, ChatGPT, or any MCP client" — grammatically the "or" reads slightly oddly listing two proper nouns then a generic catch-all; something like "Claude, ChatGPT, or your MCP client of choice" reads a touch smoother, but this is a stylistic nit, not a defect.
• No new tests were added for McpLogo, but it's a static, prop-less (aside from className) presentational SVG, so that's reasonable to skip.
• Per the PR description, npm run build wasn't run — worth confirming in CI before merge, though the change is text/SVG only so build risk is low.

I wasn't able to execute npm run test:all/prettier/typecheck myself in this sandbox (no node_modules installed here and command execution requires interactive approval unavailable in this context), so I relied on manual reading of the diff. The PR description states the pre-commit gate (vitest, format, lint, typecheck) already passed locally, and the diff's formatting is consistent with the rest of the codebase's Prettier style.

Verdict: Looks good to merge — copy-only change, consistent terminology, no stale asset/text references, reasonable a11y handling on the new logo.