git:20260714.9fcb8df to git:20260716.aa80694

2 added, 2 removed. Audit A to A.

React SPA connecting to the server via WebSocket (`useChat` hook).

Before editing host-app UI, read `../DESIGN.md` and the relevant rules in `../.agents/rules/`. `../DESIGN.md` owns visual direction and semantic choices; topic rules own syntax, component source owns APIs and dimensions, and the theme CSS owns token values. Generic design and shadcn skills may help with craft and component mechanics, but project guidance wins on aesthetics, installed-component policy, and approval requirements.

`../DESIGN.md` applies to host chrome and product surfaces. It does not apply to workspace widget/view internals or generated applets; use their workspace-local design guidance.

## Entities

- - **Space** — Top-level container. Has a name and contains widgets and a chat. One space is active at a time.

- - **Widget** — A configurable card inside the space's main area. Displayed in a grid. When there are no widgets, the chat fills the whole panel.

+ - **Workspace** — Top-level container. Has a name and contains widgets and a chat. One workspace is active at a time.

+ - **Widget** — A configurable card inside the workspace's main area. Displayed in a grid. When there are no widgets, the chat fills the whole panel.

- **Chat** — The agent conversation. Contains a scrollable message list and an input. Always lives in the panel. Two modes: sidebar (a bounded pane beside the widgets, or the full panel when there are no widgets) and floating (popover). Floating only applies when there are widgets and they need the room.

## Conventions

- UI components in `components/ui/` are shadcn built on Base UI React.

- `lib/cn.ts` is `clsx` + `tailwind-merge`.

## Frontend boundaries

- `app/` owns routes and the app shell. Route files load data and compose features; keep feature UI out of them.

- `features/<name>/` owns that feature's components, hooks, state, API hooks, and nearby tests.

- `components/ui/` contains installed shadcn primitives. `components/shared/` contains reusable app components with no feature knowledge.

- `api/` contains shared request helpers, query keys, and query policies. Feature endpoints stay in the feature's `api.ts`.

- `runtime/` contains browser-wide lifecycle code such as HMR and shared workspace events.

- `lib/` contains small feature-neutral utilities. Do not use it as a catch-all for components or feature state.

- App code may compose features. Shared components and primitives must not import from `features/` or `app/`.

- Keep tests next to the code they cover. Extract a component, hook, or pure helper when a file starts mixing multiple responsibilities.