Bleeding Edge: Mosh, Sixel, TUI improvements

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: wavetermdev

.github/copilot-instructions.md

@@ -2,22 +2,45 @@
 
 ## Project Rules
 
-Read and follow all guidelines in [`.roo/rules/rules.md`](./.roo/rules/rules.md).
+- See the overview of the project in `.kilocode/rules/overview.md`
+- Read and follow all guidelines in `.kilocode/rules/rules.md`
 
 ---
 
 ## Skill Guides
 
 This project uses a set of "skill" guides — focused how-to documents for common implementation tasks. When your task matches one of the descriptions below, **read the linked SKILL.md file before proceeding** and follow its instructions precisely.
 
-| Skill | Description |
-|-------|-------------|
-| [add-config](./.kilocode/skills/add-config/SKILL.md) | Guide for adding new configuration settings to Wave Terminal. Use when adding a new setting to the configuration system, implementing a new config key, or adding user-customizable settings. |
-| [add-rpc](./.kilocode/skills/add-rpc/SKILL.md) | Guide for adding new RPC calls to Wave Terminal. Use when implementing new RPC commands, adding server-client communication methods, or extending the RPC interface with new functionality. |
-| [add-wshcmd](./.kilocode/skills/add-wshcmd/SKILL.md) | Guide for adding new wsh commands to Wave Terminal. Use when implementing new CLI commands, adding command-line functionality, or extending the wsh command interface. |
-| [context-menu](./.kilocode/skills/context-menu/SKILL.md) | Guide for creating and displaying context menus in Wave Terminal. Use when implementing right-click menus, adding context menu items, creating submenus, or handling menu interactions with checkboxes and separators. |
-| [create-view](./.kilocode/skills/create-view/SKILL.md) | Guide for implementing a new view type in Wave Terminal. Use when creating a new view component, implementing the ViewModel interface, registering a new view type in BlockRegistry, or adding a new content type to display within blocks. |
-| [electron-api](./.kilocode/skills/electron-api/SKILL.md) | Guide for adding new Electron APIs to Wave Terminal. Use when implementing new frontend-to-electron communications via preload/IPC. |
-| [wps-events](./.kilocode/skills/wps-events/SKILL.md) | Guide for working with Wave Terminal's WPS (Wave PubSub) event system. Use when implementing new event types, publishing events, subscribing to events, or adding asynchronous communication between components. |
+| Skill        | File                                     | Description                                                                                                                                                                                                                                 |
+| ------------ | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| add-config   | `.kilocode/skills/add-config/SKILL.md`   | Guide for adding new configuration settings to Wave Terminal. Use when adding a new setting to the configuration system, implementing a new config key, or adding user-customizable settings.                                               |
+| add-rpc      | `.kilocode/skills/add-rpc/SKILL.md`      | Guide for adding new RPC calls to Wave Terminal. Use when implementing new RPC commands, adding server-client communication methods, or extending the RPC interface with new functionality.                                                 |
+| add-wshcmd   | `.kilocode/skills/add-wshcmd/SKILL.md`   | Guide for adding new wsh commands to Wave Terminal. Use when implementing new CLI commands, adding command-line functionality, or extending the wsh command interface.                                                                      |
+| context-menu | `.kilocode/skills/context-menu/SKILL.md` | Guide for creating and displaying context menus in Wave Terminal. Use when implementing right-click menus, adding context menu items, creating submenus, or handling menu interactions with checkboxes and separators.                      |
+| create-view  | `.kilocode/skills/create-view/SKILL.md`  | Guide for implementing a new view type in Wave Terminal. Use when creating a new view component, implementing the ViewModel interface, registering a new view type in BlockRegistry, or adding a new content type to display within blocks. |
+| electron-api | `.kilocode/skills/electron-api/SKILL.md` | Guide for adding new Electron APIs to Wave Terminal. Use when implementing new frontend-to-electron communications via preload/IPC.                                                                                                         |
+| waveenv      | `.kilocode/skills/waveenv/SKILL.md`      | Guide for creating WaveEnv narrowings in Wave Terminal. Use when writing a named subset type of WaveEnv for a component tree, documenting environmental dependencies, or enabling mock environments for preview/test server usage.          |
+| wps-events   | `.kilocode/skills/wps-events/SKILL.md`   | Guide for working with Wave Terminal's WPS (Wave PubSub) event system. Use when implementing new event types, publishing events, subscribing to events, or adding asynchronous communication between components.                            |
 
 > **How skills work:** Each skill is a self-contained guide covering the exact files to edit, patterns to follow, and steps to take for a specific type of task in this codebase. If your task matches a skill's description, open that SKILL.md and treat it as your primary reference for the implementation.
+
+---
+
+## Preview Server
+
+To run the standalone component preview (no Electron, no backend required):
+
+```
+task preview
+```
+
+This runs `cd frontend/preview && npx vite` and serves at **http://localhost:7007** (port configured in `frontend/preview/vite.config.ts`).
+
+To build a static preview: `task build:preview`
+
+**Do NOT use any of the following to start the preview — they all launch the full Electron app or serve the wrong content:**
+
+- `npm run dev` — runs `electron-vite dev`, launches Electron
+- `npm run start` — also launches Electron
+- `npx vite` from the repo root — uses the Electron-Vite config, not the preview app
+- Serving the `dist/` directory — the preview app is never built there; it has its own build output

.gitignore

@@ -16,6 +16,7 @@ out/
 make/
 artifacts/
 mikework/
+aiplans/
 manifests/
 .env
 out
@@ -38,3 +39,4 @@ test-results.xml
 docsite/
 
 .kilo-format-temp-*
+.ruvector/

.kilocode/skills/add-rpc/SKILL.md

@@ -26,7 +26,7 @@ RPC commands in Wave Terminal follow these conventions:
 
 - **Method names** must end with `Command`
 - **First parameter** must be `context.Context`
-- **Second parameter** (optional) is the command data structure
+- **Remaining parameters** are a regular Go parameter list (zero or more typed args)
 - **Return values** can be either just an error, or one return value plus an error
 - **Streaming commands** return a channel instead of a direct value
 
@@ -49,7 +49,7 @@ type WshRpcInterface interface {
 
 - Method name must end with `Command`
 - First parameter must be `ctx context.Context`
-- Optional second parameter for input data
+- Remaining parameters are a regular Go parameter list (zero or more)
 - Return either `error` or `(ReturnType, error)`
 - For streaming, return `chan RespOrErrorUnion[T]`
 

.kilocode/skills/electron-api/SKILL.md

@@ -7,11 +7,12 @@ description: Guide for adding new Electron APIs to Wave Terminal. Use when imple
 
 Electron APIs allow the frontend to call Electron main process functionality directly via IPC.
 
-## Three Files to Edit
+## Four Files to Edit
 
 1. [`frontend/types/custom.d.ts`](frontend/types/custom.d.ts) - TypeScript [`ElectronApi`](frontend/types/custom.d.ts:82) type
 2. [`emain/preload.ts`](emain/preload.ts) - Expose method via `contextBridge`
 3. [`emain/emain-ipc.ts`](emain/emain-ipc.ts) - Implement IPC handler
+4. [`frontend/preview/preview-electron-api.ts`](frontend/preview/preview-electron-api.ts) - Add a no-op stub to keep the `previewElectronApi` object in sync with the `ElectronApi` type
 
 ## Three Communication Patterns
 
@@ -54,7 +55,15 @@ electron.ipcMain.handle("capture-screenshot", async (event, rect) => {
 });
 ```
 
-### 4. Call from Frontend
+### 4. Add Preview Stub
+
+In [`frontend/preview/preview-electron-api.ts`](frontend/preview/preview-electron-api.ts):
+
+```typescript
+captureScreenshot: (_rect: Electron.Rectangle) => Promise.resolve(""),
+```
+
+### 5. Call from Frontend
 
 ```typescript
 import { getApi } from "@/store/global";
@@ -167,6 +176,7 @@ webContents.send("zoom-factor-change", newZoomFactor);
 - [ ] Include IPC channel name in comment
 - [ ] Expose in [`preload.ts`](emain/preload.ts)
 - [ ] Implement in [`emain-ipc.ts`](emain/emain-ipc.ts)
+- [ ] Add no-op stub to [`preview-electron-api.ts`](frontend/preview/preview-electron-api.ts)
 - [ ] IPC channel names match exactly
 - [ ] **For sync**: Set `event.returnValue` (or browser hangs!)
 - [ ] Test end-to-end

.kilocode/skills/waveenv/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: waveenv
+description: Guide for creating WaveEnv narrowings in Wave Terminal. Use when writing a named subset type of WaveEnv for a component tree, documenting environmental dependencies, or enabling mock environments for preview/test server usage.
+---
+
+# WaveEnv Narrowing Skill
+
+## Purpose
+
+A WaveEnv narrowing creates a _named subset type_ of `WaveEnv` that:
+
+1. Documents exactly which parts of the environment a component tree actually uses.
+2. Forms a type contract so callers and tests know what to provide.
+3. Enables mocking in the preview/test server — you only need to implement what's listed.
+
+## When To Create One
+
+Create a narrowing whenever you are writing a component (or group of components) that you want to test in the preview server, or when you want to make the environmental dependencies of a component tree explicit.
+
+## Core Principle: Only Include What You Use
+
+**Only list the fields, methods, atoms, and keys that the component tree actually accesses.** If you don't call `wos`, don't include `wos`. If you only call one RPC command, only list that one command. The narrowing is a precise dependency declaration — not a copy of `WaveEnv`.
+
+## File Location
+
+- **Separate file** (preferred for shared/complex envs): name it `<feature>env.ts` next to the component, e.g. `frontend/app/block/blockenv.ts`.
+- **Inline** (acceptable for small, single-file components): export the type directly from the component file, e.g. `WidgetsEnv` in `frontend/app/workspace/widgets.tsx`.
+
+## Imports Required
+
+```ts
+import {
+  BlockMetaKeyAtomFnType, // only if you use getBlockMetaKeyAtom
+  ConnConfigKeyAtomFnType, // only if you use getConnConfigKeyAtom
+  SettingsKeyAtomFnType, // only if you use getSettingsKeyAtom
+  WaveEnv,
+  WaveEnvSubset,
+} from "@/app/waveenv/waveenv";
+```
+
+## The Shape
+
+```ts
+export type MyEnv = WaveEnvSubset<{
+  // --- Simple WaveEnv properties ---
+  // Copy the type verbatim from WaveEnv with WaveEnv["key"] syntax.
+  isDev: WaveEnv["isDev"];
+  createBlock: WaveEnv["createBlock"];
+  showContextMenu: WaveEnv["showContextMenu"];
+  platform: WaveEnv["platform"];
+
+  // --- electron: list only the methods you call ---
+  electron: {
+    openExternal: WaveEnv["electron"]["openExternal"];
+  };
+
+  // --- rpc: list only the commands you call ---
+  rpc: {
+    ActivityCommand: WaveEnv["rpc"]["ActivityCommand"];
+    ConnEnsureCommand: WaveEnv["rpc"]["ConnEnsureCommand"];
+  };
+
+  // --- atoms: list only the atoms you read ---
+  atoms: {
+    modalOpen: WaveEnv["atoms"]["modalOpen"];
+    fullConfigAtom: WaveEnv["atoms"]["fullConfigAtom"];
+  };
+
+  // --- wos: always take the whole thing, no sub-typing needed ---
+  wos: WaveEnv["wos"];
+
+  // --- services: list only the services you call; no method-level narrowing ---
+  services: {
+    block: WaveEnv["services"]["block"];
+    workspace: WaveEnv["services"]["workspace"];
+  };
+
+  // --- key-parameterized atom factories: enumerate the keys you use ---
+  getSettingsKeyAtom: SettingsKeyAtomFnType<"app:focusfollowscursor" | "window:magnifiedblockopacity">;
+  getBlockMetaKeyAtom: BlockMetaKeyAtomFnType<"view" | "frame:title" | "connection">;
+  getConnConfigKeyAtom: ConnConfigKeyAtomFnType<"conn:wshenabled">;
+
+  // --- other atom helpers: copy verbatim ---
+  getConnStatusAtom: WaveEnv["getConnStatusAtom"];
+  getLocalHostDisplayNameAtom: WaveEnv["getLocalHostDisplayNameAtom"];
+}>;
+```
+
+### Automatically Included Fields
+
+Every `WaveEnvSubset<T>` automatically includes the mock fields — you never need to declare them:
+
+- `isMock: boolean`
+- `mockSetWaveObj: <T extends WaveObj>(oref: string, obj: T) => void`
+- `mockModels?: Map<any, any>`
+
+### Rules for Each Section
+
+| Section                    | Pattern                                                | Notes                                                                                              |
+| -------------------------- | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------- |
+| `electron`                 | `electron: { method: WaveEnv["electron"]["method"]; }` | List every method called; omit the rest.                                                           |
+| `rpc`                      | `rpc: { Cmd: WaveEnv["rpc"]["Cmd"]; }`                 | List every RPC command called; omit the rest.                                                      |
+| `atoms`                    | `atoms: { atom: WaveEnv["atoms"]["atom"]; }`           | List every atom read; omit the rest.                                                               |
+| `wos`                      | `wos: WaveEnv["wos"]`                                  | Take the whole `wos` object (no sub-typing needed), but **only add it if `wos` is actually used**. |
+| `services`                 | `services: { svc: WaveEnv["services"]["svc"]; }`       | List each service used; take the whole service object (no method-level narrowing).                 |
+| `getSettingsKeyAtom`       | `SettingsKeyAtomFnType<"key1" \| "key2">`              | Union all settings keys accessed.                                                                  |
+| `getBlockMetaKeyAtom`      | `BlockMetaKeyAtomFnType<"key1" \| "key2">`             | Union all block meta keys accessed.                                                                |
+| `getConnConfigKeyAtom`     | `ConnConfigKeyAtomFnType<"key1">`                      | Union all conn config keys accessed.                                                               |
+| All other `WaveEnv` fields | `WaveEnv["fieldName"]`                                 | Copy type verbatim.                                                                                |
+
+## Using the Narrowed Type in Components
+
+```ts
+import { useWaveEnv } from "@/app/waveenv/waveenv";
+import { MyEnv } from "./myenv";
+
+const MyComponent = memo(() => {
+    const env = useWaveEnv<MyEnv>();
+    // TypeScript now enforces you only access what's in MyEnv.
+    const val = useAtomValue(env.getSettingsKeyAtom("app:focusfollowscursor"));
+    ...
+});
+```
+
+The generic parameter on `useWaveEnv<MyEnv>()` casts the context to your narrowed type. The real production `WaveEnv` satisfies every narrowing; mock envs only need to implement the listed subset.
+
+## Real Examples
+
+- `BlockEnv` in `frontend/app/block/blockenv.ts` — complex narrowing with all section types, in a separate file.
+- `WidgetsEnv` in `frontend/app/workspace/widgets.tsx` — smaller narrowing defined inline in the component file.

.roo/rules/rules.md

@@ -84,8 +84,7 @@ The full API is defined in custom.d.ts as type ElectronApi.
 
 - **CRITICAL: Completion format MUST be: "Done: [one-line description]"**
 - **Keep your Task Completed summaries VERY short**
-- **No lengthy pre-completion summaries** - Do not provide detailed explanations of implementation before using attempt_completion
-- **No recaps of changes** - Skip explaining what was done before completion
+- **No double-summarization** - Put your summary ONLY inside attempt_completion. Do not write a summary in the message body AND then repeat it in attempt_completion. One summary, one place.
 - **Go directly to completion** - After making changes, proceed directly to attempt_completion without summarizing
 - The project is currently an un-released POC / MVP. Do not worry about backward compatibility when making changes
 - With React hooks, always complete all hook calls at the top level before any conditional returns (including jotai hook calls useAtom and useAtomValue); when a user explicitly tells you a function handles null inputs, trust them and stop trying to "protect" it with unnecessary checks or workarounds.

README.md

@@ -104,6 +104,14 @@ Find more information in our [Contributions Guide](CONTRIBUTING.md), which inclu
 - [Ways to contribute](CONTRIBUTING.md#contributing-to-wave-terminal)
 - [Contribution guidelines](CONTRIBUTING.md#before-you-start)
 
+### Sponsoring Wave ❤️
+
+If Wave Terminal is useful to you or your company, consider sponsoring development.
+
+Sponsorship helps support the time spent building and maintaining the project.
+
+- https://github.com/sponsors/wavetermdev
+
 ## License
 
 Wave Terminal is licensed under the Apache-2.0 License. For more information on our dependencies, see [here](./ACKNOWLEDGEMENTS.md).