fix(review): loop-2 findings — login fallback, proof-band confidence, contrast, content hedges

Code review: login no longer strands visitors with zero sign-in methods when
the providers fetch fails (falls back to SMS + error notice); skeleton while
providers load instead of a blank card.

Design re-audit: proof band flipped from apology to flex ('Don't take our
word for it / Every claim links to its proof') and promoted to the primary
heading tier; unverifiable '60 seconds'/'in minutes' speed claims dropped;
fg-subtle body text bumped to fg-muted (AA contrast); marketplace section
differentiated via border-y + elevated bg (adjacent hairlines removed);
preview frame traffic lights on-palette; header h-12 -> h-14 (hero svh calc
adjusted); emerald-400 -> --color-success token.

Content QA: rest-api article description drift between page and registry
resolved; ChatGPT plan-gating table and Atlassian Rovo SSE-cutoff claims now
carry dated hedges.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SXUwmPVRTD8AKQtio6gCN5

apps/web/app/(marketing)/guides/chatgpt-mcp-connector/page.tsx

@@ -38,7 +38,9 @@ export default function Page() {
         <H2>The plan limits, first — because they decide everything</H2>
         <P>
           Before writing a single prompt or line of code, check what your ChatGPT plan allows.
-          OpenAI gates custom MCP connectors by workspace type:
+          As of mid-2026, OpenAI gates custom MCP connectors by workspace type — verify against
+          OpenAI&apos;s current help docs before committing to a plan, since these limits have
+          shifted before:
         </P>
         <Table>
           <thead>

apps/web/app/(marketing)/guides/mcp-transports-explained/page.tsx

@@ -129,7 +129,8 @@ export default function Page() {
           Spec revision <Strong>2025-03-26</Strong> replaced HTTP+SSE with Streamable HTTP. The old
           transport still works where both sides keep supporting it, but the direction is one-way:
           platforms have been announcing removal dates through 2026 — Atlassian's Rovo MCP server,
-          for example, set its HTTP+SSE cutoff for June 30, 2026. New servers should not ship it.
+          for example, announced an HTTP+SSE cutoff of June 30, 2026. New servers should not ship
+          it.
         </P>
 
         <H2>Streamable HTTP: the current standard</H2>