Prepare to publish.

Author: nedtwigg

.gitattributes

@@ -0,0 +1,3 @@
+*.png binary
+*.webp binary
+*.mp4 binary

.github/workflows/chromatic.yml

@@ -0,0 +1,44 @@
+name: Chromatic
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'lib/**'
+  pull_request:
+    paths:
+      - 'lib/**'
+
+jobs:
+  chromatic:
+    name: Visual Regression Tests
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Install dependencies
+        run: pnpm install
+        working-directory: lib
+
+      - name: Run Chromatic
+        uses: chromaui/action@latest
+        with:
+          projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
+          workingDir: lib
+          buildScriptName: build-storybook
+          exitZeroOnChanges: true
+          onlyChanged: true

.github/workflows/ci.yml

@@ -0,0 +1,63 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  build-and-test:
+    name: Build & Test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Test
+        run: pnpm test
+
+      - name: Build
+        run: pnpm build
+
+  standalone-smoketest:
+    name: Standalone Smoketest
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - uses: dtolnay/rust-toolchain@stable
+
+      - name: Install system dependencies
+        run: |
+          sudo apt-get update -qq
+          sudo apt-get install -y -qq libgtk-3-dev libwebkit2gtk-4.1-dev libappindicator3-dev librsvg2-dev
+
+      - name: Install npm dependencies
+        run: pnpm install
+        working-directory: standalone
+
+      - name: TypeScript check
+        run: npx tsc --noEmit
+        working-directory: standalone
+
+      - name: Cargo check
+        run: cargo check
+        working-directory: standalone/src-tauri

.github/workflows/publish-vscode.yml

@@ -0,0 +1,57 @@
+name: Publish VSCode Extension
+
+on:
+  push:
+    tags:
+      - 'vscode-ext/v*'
+
+jobs:
+  publish:
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: pnpm
+          cache-dependency-path: |
+            lib/pnpm-lock.yaml
+            vscode-ext/pnpm-lock.yaml
+
+      # Install and build frontend for VSCode
+      - name: Install frontend dependencies
+        run: cd lib && pnpm install
+
+      - name: Run tests
+        run: cd lib && pnpm test
+
+      - name: Build frontend for VSCode
+        run: cd vscode-ext && pnpm build:frontend
+
+      # Install and build extension
+      - name: Install extension dependencies
+        run: cd vscode-ext && pnpm install
+
+      - name: Build extension
+        run: cd vscode-ext && pnpm build
+
+      # Package
+      - name: Package extension
+        run: cd vscode-ext && npx vsce package --no-dependencies
+
+      # Publish to VS Code Marketplace
+      - name: Publish to VS Code Marketplace
+        run: cd vscode-ext && npx vsce publish --no-dependencies
+        env:
+          VSCE_PAT: ${{ secrets.VSCE_PAT }}
+
+      # Publish to OpenVSX
+      - name: Publish to OpenVSX
+        run: cd vscode-ext && npx ovsx publish --no-dependencies
+        env:
+          OVSX_PAT: ${{ secrets.OVSX_PAT }}

.gitignore

@@ -0,0 +1,49 @@
+# Dependencies
+node_modules/
+
+# Build output
+dist/
+lib/dist/
+*.tsbuildinfo
+
+# Vite cache
+lib/.vite/
+
+# VSCode extension
+vscode-ext/dist/
+vscode-ext/media/
+vscode-ext/node_modules/
+vscode-ext/*.vsix
+
+# Tauri / Standalone
+standalone/src-tauri/target/
+standalone/src-tauri/binaries/
+standalone/dist/
+standalone/sidecar/node_modules/
+standalone/node_modules/
+
+# Website
+website/dist/
+website/node_modules/
+
+# OS
+.DS_Store
+
+# Editor
+.vscode/*
+!.vscode/launch.json
+!.vscode/tasks.json
+.idea/
+
+# Environment
+.env.local
+
+# Storybook / Chromatic
+storybook-static/
+build-storybook.log
+chromatic.log
+chromatic-build-*.xml
+chromatic-diagnostics.json
+
+# symlinked skill files
+.agents/skills/

.impeccable.md

@@ -0,0 +1,41 @@
+## Design Context
+
+### Users
+Developers ranging from terminal beginners (non-developers using Claude Code for the first time) to tmux power users. They're multitasking across multiple terminal sessions and need to know when background tasks finish without watching idle screens. Context: working inside VSCode (primary) or a standalone terminal app (secondary).
+
+### Brand Personality
+**Focused. Approachable. Capable.**
+
+MouseTerm should feel like focused efficiency that cares about beginners and onboarding, without sacrificing anything that even the most extreme power user might want eventually. The interface should communicate: "everything is under control" — no clutter, no distraction, just the information you need when you need it.
+
+### Aesthetic Direction
+
+**Primary constraint: Feel native inside VSCode.** The current Catppuccin Mocha design is throwaway — built to get things running. The first design priority is making MouseTerm feel completely native within VSCode, respecting whatever theme the user has chosen. This means:
+- Use VSCode's CSS variables and theme tokens, not hardcoded colors
+- Match VSCode's spacing, typography, and interaction patterns
+- Light mode and dark mode support from the start (inherited from user's VSCode theme)
+- The webview should feel like a built-in VSCode feature, not a third-party panel
+
+**After VSCode-native is achieved**, figure out the standalone terminal's visual identity separately.
+
+**References:**
+- VSCode itself — the gold standard for how MouseTerm should feel as an extension
+- The tool should feel like a natural part of the editor, not a foreign embed
+
+**Anti-references:**
+- Generic SaaS (rounded cards, gradients, startup illustrations)
+- Hacker aesthetic (green-on-black, Matrix vibes, intimidating to beginners)
+- Electron bloat (Slack — heavy, slow-feeling, too much chrome)
+- Overly playful (too many animations, emojis, mascots)
+
+### Design Principles
+
+1. **Native first** — Inside VSCode, MouseTerm should be indistinguishable from a built-in feature. Use the host's theme tokens, spacing, and conventions. Never fight the environment.
+
+2. **Information density without intimidation** — Power users want dense layouts with many terminals visible. Beginners need to not feel overwhelmed. Solve this with progressive disclosure: simple by default, powerful when you explore.
+
+3. **Status at a glance** — The core UX promise is "glance and know what's done." Status indicators must be scannable in under a second across many terminals. No reading required — use shape, color, and position.
+
+4. **No chrome, all content** — Minimize UI chrome. Terminals are the content. Headers, tabs, and controls should be minimal and recede. Every pixel of chrome competes with terminal output.
+
+5. **Theme-adaptive** — Never hardcode colors. Always derive from the host theme (VSCode variables, or a standalone theme system later). Support light and dark from day one.

.vscode/launch.json

@@ -0,0 +1,13 @@
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "name": "MouseTerm Extension",
+      "type": "extensionHost",
+      "request": "launch",
+      "args": ["--extensionDevelopmentPath=${workspaceFolder}/vscode-ext"],
+      "outFiles": ["${workspaceFolder}/vscode-ext/dist/**/*.js"],
+      "preLaunchTask": "build-mouseterm-vscode"
+    }
+  ]
+}

.vscode/tasks.json

@@ -0,0 +1,12 @@
+{
+  "version": "2.0.0",
+  "tasks": [
+    {
+      "label": "build-mouseterm-vscode",
+      "type": "shell",
+      "command": "pnpm build:vscode",
+      "group": "build",
+      "problemMatcher": []
+    }
+  ]
+}

AGENTS.md

@@ -0,0 +1,48 @@
+# MouseTerm
+
+A mouse-friendly multitasking terminal built with pnpm, react, typescript, vite, tailwind, storybook, and xterm.js.
+
+## Setup
+
+```
+pnpm install     # install deps
+pnpm build       # build lib, vscode extension, and website
+```
+
+## Architecture
+
+- **lib/** — Shared React + TailwindCSS frontend library (components, platform abstraction, tests, Storybook)
+- **standalone/** — Tauri desktop app with Node.js sidecar for native PTY via node-pty
+- **vscode-ext/** — VS Code extension wrapping the lib in a webview with native PTY backend
+- **website/** — Marketing website bundling part of the lib as an interactive demo
+
+## Project Structure
+
+- `lib/` — Core UI library (pnpm) — Storybook, tests, shared components
+- `lib/src/lib/platform/` — Platform abstraction layer (`PlatformAdapter` interface, fake + VSCode adapters)
+- `standalone/` — Tauri app (Rust + Vite frontend)
+- `standalone/sidecar/` — Node.js PTY manager, bundled as Tauri sidecar
+- `standalone/src-tauri/` — Rust backend that bridges webview ↔ Node.js sidecar
+- `vscode-ext/` — VS Code extension (esbuild, node-pty via forked child process)
+- `website/` — Marketing site (Vite, uses FakePtyAdapter for demo)
+
+## Specs
+
+The primary job of a spec is to be an accurate reference for the current state of the code. Read the relevant spec before modifying a feature it covers — the spec describes invariants, edge cases, and design decisions that are not obvious from the code alone.
+
+- **`docs/specs/layout.md`** — Tiling layout, pane/door containers, dockview configuration, modes (passthrough/command), keyboard shortcuts, selection overlay, spatial navigation, detach/reattach, inline rename, session lifecycle, session persistence, and theming. Read this when touching: `Pond.tsx`, `Baseboard.tsx`, `Door.tsx`, `TerminalPane.tsx`, `spatial-nav.ts`, `layout-snapshot.ts`, `terminal-registry.ts`, `session-save.ts`, `session-restore.ts`, `reconnect.ts`, `index.css`, `theme.css`, or any keyboard/navigation/mode behavior.
+- **`docs/specs/alarm.md`** — Activity monitoring state machine, alarm trigger/clearing rules, attention model, TODO lifecycle (soft/hard), bell button visual states and interaction, door alarm indicators, and hardening (a11y, motion, i18n, overflow). Read this when touching: `activity-monitor.ts`, `alarm-manager.ts`, the alarm bell or TODO pill in `Pond.tsx` (TerminalPaneHeader), alarm indicators in `Door.tsx`, or the `a`/`t` keyboard shortcuts. Layout.md defers to this spec for all alarm/TODO behavior.
+- **`docs/specs/vscode.md`** — VS Code extension architecture: hosting modes (WebviewView + WebviewPanel), PTY lifecycle and buffering, message protocol between webview and extension host, session persistence flow, reconnection protocol, theme integration, CSP, build pipeline, and invariants (save-before-kill ordering, PTY ownership, alarm state merging). Read this when touching: `extension.ts`, `webview-view-provider.ts`, `message-router.ts`, `message-types.ts`, `pty-manager.ts`, `pty-host.js`, `session-state.ts`, `webview-html.ts`, `vscode-adapter.ts`, or `pty-core.js`.
+- **`docs/specs/tutorial.md`** — Playground tutorial on the website: 3-pane initial layout, `tut` command and TutorialShell, 6-step progressive tutorial with detection logic, theme picker, FakePtyAdapter extensions, and Pond event hooks. Read this when touching: `website/src/pages/Playground.tsx`, `website/src/lib/tutorial-shell.ts`, `website/src/lib/tutorial-detection.ts`, `website/src/components/ThemePicker.tsx`, `website/src/lib/playground-themes.ts`, `lib/src/lib/platform/fake-scenarios.ts` (tutorial scenarios), or the `onApiReady`/`onEvent`/`initialPaneIds` props on Pond.
+
+When updating code covered by a spec, update the spec to match. When the two specs overlap (e.g. pane header elements appear in both), layout.md documents placement and sizing while alarm.md documents behavior and visual states.
+
+## Design
+
+See [.impeccable.md](.impeccable.md) for full design context. Key principles:
+
+1. **Native first** — Inside VSCode, feel indistinguishable from a built-in feature. Use the host's theme tokens.
+2. **Information density without intimidation** — Dense for power users, approachable for beginners. Progressive disclosure.
+3. **Status at a glance** — Scannable in under a second across many terminals.
+4. **No chrome, all content** — Minimize UI chrome. Terminals are the content.
+5. **Theme-adaptive** — Never hardcode colors. Support light and dark from day one.