[CodexManvik]

Phase 3: a Next.js web app in web/ that replaces the Streamlit stopgap as the showcase. The spec is in docs/superpowers/specs/2026-11-09-phase3-web-app-design.md.

What's in it

• Landing page:
  • an asymmetric hero with a question box and a live, draggable canvas globe of all 660 floats, coloured by surface temperature (cmocean thermal)
  • live dataset numbers and sample questions
  • a scroll-driven "How an answer is made", where the real run-log component fills in as the story reaches each stage
  • the latest benchmark score, read from eval/latest.json on GitHub
  • the stack
• Chat (/chat, streams /query/stream):
  • a live run log while the answer is worked out: what the router understood (AI router or keyword fallback, filters as chips), each SQL attempt with rows and timing, the search with its match count, and who wrote the text; when done it collapses to a one-line summary
  • the streaming answer, then Chart / Data / SQL tabs, or the matching profiles on a map
  • Stop, Retry, copy, suggested follow-ups, and history for follow-ups
• Float pages (/floats/[id]): trajectory map, latest profile, a depth-time section (temperature, salinity or oxygen, square-root depth axis) and a T-S diagram. Plus /floats (search, region and BGC filters) and /compare (two floats overlaid).
• Design: graphite neutrals with one accent, marine safety orange, kept to actions and live state. Data uses the oceanographers' cmocean scales. Geist and Geist Mono type, light and dark themes, mobile menu, reduced-motion support, and AA contrast checked numerically.
• Agent UI follows current agent-UX guidance: visible tool calls with their inputs and outputs, a chronological step log, calibrated signals ("keyword fallback", "SQL repaired", "widened search") instead of reasoning prose, and stop/retry controls.

Checks

• web/: 16 Vitest unit tests (SSE parser, run reducer, cmocean sampling, profile shaping), ESLint and tsc clean, next build passes. A new web CI job runs all of these.
• Lighthouse, mobile, production build of the landing page: performance 92, accessibility 100, best practices 100, SEO 100.
• Verified in the browser against the live API, on desktop and at 375 px, in both themes:
  • analytical and search questions
  • follow-up chips
  • float page, index and compare
• While building this I found a streaming mojibake bug, fixed and merged separately in Decode the LLM event stream as UTF-8 #11.

Needs you (accounts)

Import the repo on Vercel with root directory web and set NEXT_PUBLIC_API_URL, then add the Vercel URL to ALLOWED_ORIGINS on Render. The steps are in DEPLOY.md, section 5.

🤖 Generated with Claude Code

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: ff47aeff-abb9-4892-ba99-631ab709ee81

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.