feat(web)!: trim app to landing + auth + OAuth consent — CLI/MCP direction lock - #146
Merged
Conversation
…ction lock The web app is retired; CLI + MCP are the product. The Next.js app now serves only the public landing (/), Clerk sign-in/sign-up, and the hosted-MCP OAuth consent page (/oauth/authorize, pointed at by backend/src/strata/config.py). - / always renders the public landing (HomeGate + app home removed) - layout drops AppShell and the react-query Providers (no survivor needs query) - middleware allowlist: / sign-in sign-up oauth robots sitemap opengraph; retired routes 404 via Next not-found, no redirects - sitemap lists only /, no backend fetch; /embed CSP block dropped - deps pruned to @clerk/nextjs, motion, next, react, react-dom, zod (zod via lib/env.ts in the oauth closure); test/storybook/playwright tooling removed; lockfile regenerated with bun - deploy-smoke web probes trimmed to / and /sign-in Full app preserved on branch frontend-archive + tag frontend-archive-2026-06-10. next build green: / /_not-found /oauth/authorize /robots.txt /sign-in /sign-up /sitemap.xml. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The direction lock (root CLAUDE.md): MCP + CLI are the product; the web UI is retired. This PR trims the Next.js app to the only surfaces that still earn their keep, so the Vercel deployment (stratabank.vercel.app) keeps working with a fraction of the code.
The full app is preserved untouched on the
frontend-archivebranch and thefrontend-archive-2026-06-10tag — nothing is lost.What survives
/always renders<NightCanvas><PublicLanding/></NightCanvas>(pixel-identical to the deployed signed-out page; HomeGate + signed-in app home removed)/sign-in,/sign-up,AuthCanvas, Clerk middleware +lib/clerk*— the landing's Sign in / Create account CTAs work exactly as today/oauth/authorize(ConsentView) —backend/src/strata/config.pypoints hosted-MCP OAuth here; its full import closure kept (ui/Button,lib/env→ zod)layout/globals.css/robots/not-found, a sitemap rewritten to list only/(no backend fetch), and config (next.config.tsminus the /embed CSP block)What was deleted
@tanstack/react-query,reactflow,recharts,simple-icons,vis-data,vis-network,zustand,clsx,tailwind-merge(verified against survivor imports — no survivor uses react-query, so the Providers wrapper is gone from layout); all test/storybook devDeps; lockfile regenerated with bunBehavior notes
not-found.tsx, copy updated) — intentional, no redirects/,/sign-in*,/sign-up*,/oauth*, robots/sitemap/opengraphscripts/deploy-smoke.shweb probes trimmed to/+/sign-in/tampermalink repointing is a separate task)Proof
bun run buildgreen — routes://_not-found/oauth/authorize/robots.txt/sign-in/sign-up/sitemap.xml.tsc --noEmit, biome, and eslint all clean.🤖 Generated with Claude Code