Rust rewrite: lean multiplexer core with paning system with a basic plugin system.

.github/workflows/ci.yml

@@ -1,113 +1,60 @@
-# Continuous checks on every push and PR. The supported artifact is pure Go, so
-# the main lane is one cgo-free Ubuntu job. Windows gets its own job for one
-# reason: the ConPTY-backed PTY layer (ADR 0006 as amended) is real shipped code
-# on the supported Windows binary, so it is smoke-tested here on every change —
-# a PTY round-trip through go-pty's ConPTY, driven by the same Manager surface an
-# operator's shell tab uses (internal/terminal/pty_windows_test.go).
-name: ci
+name: CI
 
 on:
   push:
-    branches: [main]
   pull_request:
 
 permissions:
   contents: read
 
 jobs:
-  check:
-    name: check + test (linux, cgo-free)
-    runs-on: ubuntu-latest
-    env:
-      CGO_ENABLED: "0"
+  test:
+    name: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [macos-15, ubuntu-24.04]
+    runs-on: ${{ matrix.os }}
+
     steps:
       - uses: actions/checkout@v4
 
-      - uses: actions/setup-go@v5
-        with:
-          go-version: "1.26"
-          cache: true
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: "24"
-          cache: npm
-          cache-dependency-path: web/package-lock.json
-
-      # Build the embedded SPA first: the embed test compiles against web/dist,
-      # and `make check`/`make test` expect a real dist, not just the .gitkeep.
-      - name: Build frontend
-        run: make web
-
-      - name: Frontend unit tests
-        run: cd web && npm test
-
-      - name: Static checks (go vet + svelte-check)
-        run: make check
-
-      - name: Shell script syntax
-        run: bash -n scripts/*.sh
-
-      - name: Go tests
-        run: make test
-
-      # The chrome is monochrome plus --destructive (ADR 0012); the only amber in
-      # the product is the star-map island's `claimed` star, which lives in the
-      # canvas renderer (bundled into JS, never the chrome CSS). So a literal
-      # `amber` in the built CSS is a Tailwind amber-* utility or a raw keyword
-      # leaking into the chrome — fail on it. The built CSS is the ground truth.
-      - name: No amber in built chrome CSS
+      - name: Install Linux dependencies
+        if: runner.os == 'Linux'
         run: |
-          if grep -rniE '\bamber\b' web/dist/assets/*.css; then
-            echo "::error::amber found in built chrome CSS (ADR 0012: the chrome is monochrome + --destructive)"
-            exit 1
-          fi
+          sudo apt-get update
+          sudo apt-get install -y \
+            build-essential clang cmake pkg-config \
+            libasound2-dev libfontconfig-dev libglib2.0-dev libssl-dev \
+            libva-dev libvulkan1 libwayland-dev libx11-xcb-dev \
+            libxkbcommon-x11-dev libzstd-dev libwebkit2gtk-4.1-dev
 
-  # The Linux shell compiles on every change, not only at release time. This is
-  # the cheap half of the release gate and it exists because of how the previous
-  # breakage went unnoticed: webview_go pins `pkg-config: webkit2gtk-4.0`, that
-  # package vanished from the runner image, and because the shell was built only
-  # inside a `continue-on-error` release job, an entire version shipped with no
-  # Linux app and nothing said so. Compiling here means the pin can only rot in
-  # front of a red check. The full AppImage smoke stays in release.yml — it needs
-  # a container and a screenshot, which is too slow to put on every push.
-  linux-shell-build:
-    name: linux webview shell builds (cgo)
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
+      - name: Install the pinned Rust toolchain
+        run: rustup show
 
-      - uses: actions/setup-go@v5
+      - uses: Swatinem/rust-cache@v2
         with:
-          go-version: "1.26"
-          cache: true
-
-      - name: Install WebKitGTK toolchain
-        run: |
-          sudo apt-get update
-          sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev
+          cache-on-failure: true
 
-      # No frontend build: the shell embeds web/dist, and the committed .gitkeep
-      # is enough to compile the embed package. This job is asking whether the
-      # cgo links, not whether the SPA is current.
-      - name: Build the shell
-        run: make webview
+      - name: Install Zig for Herdr
+        uses: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29 # v2
+        with:
+          version: 0.15.2
 
-  windows-smoke:
-    name: windows PTY smoke (ConPTY round-trip)
-    runs-on: windows-latest
-    env:
-      CGO_ENABLED: "0"
-    steps:
-      - uses: actions/checkout@v4
+      - name: Fetch the pinned Herdr sidecar
+        run: ZIG="$(command -v zig)" sh vendor/herdr/fetch.sh
 
-      - uses: actions/setup-go@v5
+      # The workspace's terminal encoder requires a newer Zig than Herdr.
+      - name: Install Zig for the workspace
+        uses: mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29 # v2
         with:
-          go-version: "1.26"
-          cache: true
+          version: 0.16.0
+
+      - name: Check formatting
+        run: cargo fmt --all --check
+
+      - name: Build and test
+        run: cargo test --workspace --locked --no-fail-fast
 
-      # The dist directory needs the committed .gitkeep to compile the embed
-      # package; the terminal test never touches the SPA, so no frontend build is
-      # needed here — just the ConPTY round-trip.
-      - name: ConPTY round-trip smoke test
-        run: go test -v -run TestConPTYRoundTrip ./internal/terminal
+      - name: Build the build-time native module example
+        run: cargo check --manifest-path examples/plugins/hello/Cargo.toml --locked