Skip to content

Redesign Lumos platform surfaces#620

Draft
candasoz01-cmd wants to merge 1 commit into
mainfrom
codex/lumos-platform-redesign
Draft

Redesign Lumos platform surfaces#620
candasoz01-cmd wants to merge 1 commit into
mainfrom
codex/lumos-platform-redesign

Conversation

@candasoz01-cmd

Copy link
Copy Markdown
Owner

Summary

  • Reframes the home page from a chat-product landing into a Lumos platform/control-layer surface.
  • Reorganizes /panel as a real workspace: modules, central chat, identity/system/task context.
  • Adds desktop/mobile evidence, before/after comparisons, and two explored visual variants.

Scope

  • Selected variant B: stronger ecosystem and orchestration signal while keeping the dark Lumos language, turquoise/gold accents, and restrained motion.
  • Adds clear Lumos ID, security, AI orchestration, integrations, automation, developer, and device ecosystem messaging.
  • Labels unavailable capabilities as roadmap/preparing instead of presenting them as live.
  • Preserves existing routes, panel behavior, redirects, and release configuration.

Out of scope

  • No production deployment.
  • No OAuth secrets, environment values, or private OAuth implementation copied into this public branch.
  • No backend/provider behavior changes.

Validation

  • npm run build — 15 static routes built.
  • targeted UI/i18n tests — 148 passed.
  • full suite — 1320 passed, 3 skipped.
  • npm run e2e:smoke --prefix ui — passed.
  • merge simulation with cursor/oauth-callback-live-02d4 — clean, no conflicts.
  • local mobile checks: home 375/375 and panel 390/390 client/scroll width; no horizontal overflow.

Visual review

See docs/visual-review/README.md and the committed images under docs/visual-review/:

  • variant-a-desktop.png
  • variant-b-desktop.png
  • compare-home.png
  • compare-panel.png
  • after-home-mobile.png
  • after-panel-mobile.png

Known risks

  • Public main does not contain the production OAuth routes; this branch intentionally leaves that private integration boundary untouched.
  • Some long legacy landing content remains in source and is visually de-emphasized; a later content-debt pass may remove it after product approval.
  • npm install reports 5 existing audit findings (1 low, 1 moderate, 3 high); this PR does not broaden scope into dependency upgrades.

@vercel

vercel Bot commented Jul 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
lumos-core Ready Ready Preview, Comment Jul 16, 2026 10:45am
n Ready Ready Preview, Comment Jul 16, 2026 10:45am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant