Skip to content

feat(frontend): path-first connected Operate shell - #2

Closed
Warexpor wants to merge 4 commits into
masterfrom
feat/connected-bench-v2
Closed

feat(frontend): path-first connected Operate shell#2
Warexpor wants to merge 4 commits into
masterfrom
feat/connected-bench-v2

Conversation

@Warexpor

Copy link
Copy Markdown
Owner

Why

The connected shell on master was half-finished next to the intro, and the earlier signal-bench PR overcooked the instrument look. This restarts from master with a calmer path-first Operate UI.

Scope

Connected shell only. Adds DESIGN.md / PRODUCT.md, connected.css, ConnectedHeader, pathAggregate, Vite sim.js (?connected=1), and restyles Sidebar / PeerList / Chat / Settings / StatusBar. One Settings control in the header (sidebar duplicate removed). Restrained motion. Intro ConnectView and space.css stay frozen.

Tradeoffs

Kept master view routing (network / chat / settings) instead of a Discord chat column. Dropped the prior LED/graticule costume for readable density.

Blast Radius

Windows Wails frontend connected mode and Vite DEV preview. No vpncore or signaling changes.

Verification

  • cd client/frontend && npm run build
  • Vite http://127.0.0.1:5173/?connected=1 (room, VIP, path, disconnect, peers)

These files pin path-first B&W chrome so the rebuild can follow a contract instead of the old CRT costume.
Derive one pathAggregate in App, scope tokens to html[data-app], and put disconnect in the header so connected mode can leave the server. Vite sim supports ?connected=1.
@Warexpor Warexpor closed this Aug 28, 2026
@Warexpor
Warexpor deleted the feat/connected-bench-v2 branch August 28, 2026 15:45
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