Polish responsive UI and skip docs-only builds

Author: bproject07

.github/workflows/ci.yml

@@ -15,8 +15,82 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
+  changes:
+    name: Classify changes
+    runs-on: ubuntu-24.04
+    outputs:
+      docs_only: ${{ steps.classify.outputs.docs_only }}
+
+    steps:
+      - name: Check out source
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+
+      - name: Classify documentation-only changes
+        id: classify
+        shell: bash
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          BEFORE_SHA: ${{ github.event.before }}
+          BASE_SHA: ${{ github.event.pull_request.base.sha }}
+          HEAD_SHA: ${{ github.sha }}
+        run: |
+          set -euo pipefail
+
+          if [[ "$EVENT_NAME" == "workflow_dispatch" ]]; then
+            echo "docs_only=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          if [[ "$EVENT_NAME" == "pull_request" ]]; then
+            base="$BASE_SHA"
+          else
+            base="$BEFORE_SHA"
+          fi
+
+          if [[ -z "$base" || "$base" =~ ^0+$ ]] ||
+             ! git cat-file -e "$base^{commit}" 2>/dev/null; then
+            echo "docs_only=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          mapfile -d '' changed_files < <(
+            git diff --name-only -z "$base" "$HEAD_SHA"
+          )
+          if [[ "${#changed_files[@]}" -eq 0 ]]; then
+            echo "docs_only=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          docs_only=true
+          for path in "${changed_files[@]}"; do
+            lowercase_path="${path,,}"
+            case "$lowercase_path" in
+              *.md | docs/*)
+                ;;
+              *)
+                docs_only=false
+                break
+                ;;
+            esac
+          done
+
+          echo "docs_only=$docs_only" >> "$GITHUB_OUTPUT"
+
+  documentation:
+    name: Documentation only
+    needs: changes
+    if: needs.changes.outputs.docs_only == 'true'
+    runs-on: ubuntu-24.04
+    steps:
+      - name: Confirm documentation-only change
+        run: echo "Only Markdown or docs/ files changed; build jobs are skipped."
+
   validate:
     name: ${{ matrix.name }}
+    needs: changes
+    if: needs.changes.outputs.docs_only != 'true'
     runs-on: ${{ matrix.runner }}
     timeout-minutes: 30
     strategy:
@@ -208,6 +282,8 @@ jobs:
 
   minimum-rust:
     name: Minimum Rust 1.88
+    needs: changes
+    if: needs.changes.outputs.docs_only != 'true'
     runs-on: ubuntu-24.04
     timeout-minutes: 15
 

BUILDING.md

@@ -109,6 +109,13 @@ If the local machine cannot run Linux, use GitHub Actions, a Linux VM, or a
 Linux host you control. Do not mark the change complete or describe it as
 Linux-supported until that validation has actually passed.
 
+The CI workflow classifies every push and pull request before starting the
+build matrix. When every changed path is either a Markdown file or is under
+`docs/`, CI records a successful documentation-only job and skips the Node,
+Rust, Windows, and Linux build jobs. Any source, script, workflow,
+configuration, lockfile, or other non-documentation change runs the complete
+matrix. A manual `workflow_dispatch` always runs the complete matrix.
+
 Documentation must describe the current source and verified behavior. Check
 CLI flags, environment variables, dependency versions, build commands,
 package contents, UI labels, platform support, and known limitations instead
@@ -933,13 +940,13 @@ For a disposable manual peer smoke:
 1. start a package on an unused port and with an isolated `--state-dir`;
 2. open **@cwt** from a running source tab;
 3. choose a different ready agent and a disposable reviewer directory that is
-   not the source directory, then use **Source ready — Prepare handoff** at an
+   not the source directory, then use **Prepare summary** at an
    empty source prompt;
-4. verify the preview, then use **Reviewer ready — Send** at an empty reviewer
+4. verify the preview, then use **Send to reviewer** at an empty reviewer
    prompt;
 5. verify a new linked reviewer tab was created in the selected reviewer
    directory and the source directory did not change;
-6. use **Source ready — Return**, then issue **Recheck** and confirm the same
+6. use **Return to source**, then issue **Recheck** and confirm the same
    reviewer `terminalId` and `sessionId` remain;
 7. close the reviewer and confirm the source is still running;
 8. stop the disposable server.

OPERATIONS.md

@@ -610,14 +610,14 @@ normal tab, even when a matching agent appears idle.
 
 The operational sequence is:
 
-1. choose the reviewer agent, working folder, and action, then use **Source
-   ready — Prepare handoff** while the source is at an empty agent prompt;
+1. choose the reviewer agent, working folder, and action, then use **Prepare
+   summary** while the source is at an empty agent prompt;
 2. wait for the source agent to submit a bounded handoff;
-3. inspect or edit **Preview handoff**;
-4. use **Reviewer ready — Send** while the reviewer is at an empty agent
+3. inspect or edit **Preview summary**;
+4. use **Send to reviewer** while the reviewer is at an empty agent
    prompt;
 5. wait for **Response ready**;
-6. use **Source ready — Return** while the source is at an empty agent prompt;
+6. use **Return to source** while the source is at an empty agent prompt;
 7. use a follow-up or **Recheck** to retain that same reviewer context.
 
 Concrete example: from a Codex source tab, choose **Verify** with Claude and
@@ -627,8 +627,8 @@ missing Windows/Linux tests.` Inspect the generated handoff before dispatch.
 The dedicated reviewer starts in the selected directory without changing any
 ordinary tab. Return Claude's response to the same Codex source, then use
 **Recheck** for another pass that retains Claude's reviewer context and
-working directory. Use **+ New peer** only when a clean reviewer conversation
-is intentional.
+working directory. Use **+ New reviewer** only when a clean reviewer
+conversation is intentional.
 It is disabled when session capacity is full, while follow-ups on an existing
 reviewer remain available. One reviewer thread retains at most 32 turns; close
 it and start a clean peer after reaching that boundary. The broker permits at
@@ -660,8 +660,10 @@ shutdown disables new capabilities and revokes existing ones before releasing
 the private listener; an unexpected private-listener exit also stops the
 public service.
 
-The readiness-labelled buttons are an explicit operator acknowledgement, not
-an inferred state. The corresponding API requests require `sourceReady: true`
+**Prepare summary**, **Send to reviewer**, and **Return to source** are an
+explicit operator acknowledgement that the named terminal is at an empty
+prompt, not an inferred state. The corresponding API requests require
+`sourceReady: true`
 or `reviewerReady: true`, and delivery is rejected if the PTY generation has
 changed. Do not confirm readiness while the CLI is showing a permission,
 login, trust, or first-run prompt, or while text is partially entered.
@@ -777,8 +779,9 @@ left to the browser or operating system.
 ### Mobile keys
 
 Shows or hides the mobile toolbar. Its order begins with Enter and the arrow
-keys, followed by Page Up/Down, Ctrl mode, Esc, Tab, Ctrl+C, Ctrl+L, Top, Live,
-and Hide.
+keys, followed by Esc, Ctrl+C, Tab, Ctrl mode, Page Up/Down, Ctrl+L, Top, Live,
+and Hide, so the interrupt keys stay inside the first screenful on a narrow
+phone.
 
 - **PgUp/PgDn** moves through xterm's client-side scrollback.
 - **Top** moves to the oldest retained client-side line.

README.md

@@ -402,8 +402,8 @@ does not intercept text typed into xterm, so raw terminal input and Android
 IME handling remain unchanged.
 
 1. Select **Review**, **Verify**, **Ask**, or **Handoff**, choose an installed
-   agent kind and reviewer folder, describe the scope, and use **Source ready
-   — Prepare handoff** only while the source is at an empty agent prompt. The
+   agent kind and reviewer folder, describe the scope, and use **Prepare
+   summary** only while the source is at an empty agent prompt. The
    reviewer folder defaults to the source tab's folder; **Change folder**
    reuses the normal Favorites, Recent, Browse, and absolute-path picker.
 2. The server revalidates that selected directory and creates a fresh
@@ -414,14 +414,14 @@ IME handling remain unchanged.
    reviewer tab yourself.
 3. The source agent prepares a bounded Markdown handoff through a private
    local bridge. The browser shows it for review and optional editing.
-4. **Reviewer ready — Send** releases the approved handoff after the dedicated
+4. **Send to reviewer** releases the approved handoff after the dedicated
    reviewer is at an empty agent prompt.
-5. When the response is ready, **Source ready — Return** asks the source agent
+5. When the response is ready, **Return to source** asks the source agent
    to retrieve it and present the useful conclusion in its existing context.
 6. A later **Recheck** or follow-up uses the same live reviewer PTY. **+ New
-   peer** always creates a clean reviewer context.
+   reviewer** always creates a clean reviewer context.
 
-A new reviewer also consumes one session slot, so **+ New peer** is disabled
+A new reviewer also consumes one session slot, so **+ New reviewer** is disabled
 when the configured capacity is full. Existing follow-ups remain enabled
 because they reuse their reviewer. The broker retains at most 32 turns in one
 reviewer thread; after that, close it and start a clean peer conversation.
@@ -434,10 +434,10 @@ then enter: `Review the current implementation for correctness, security
 regressions, and missing Windows/Linux tests.` The source prepares the
 handoff; you inspect it before sending. Claude's fresh reviewer runs in the
 selected project B directory without modifying an ordinary project B tab.
-After Claude submits its bounded response, **Source ready — Return** brings
+After Claude submits its bounded response, **Return to source** brings
 the result back to that exact Codex conversation. A later **Recheck** keeps
-Claude's reviewer context and working directory; **+ New peer** deliberately
-starts without that conversation.
+Claude's reviewer context and working directory; **+ New reviewer**
+deliberately starts without that conversation.
 
 Peer and ordinary non-primary tabs have an accessible `×`. Closing a peer tab
 terminates only its dedicated PTY and purges its in-memory thread. A reviewer
@@ -460,8 +460,9 @@ writes an artifact.
 
 This is supervised coordination, not an autonomous scheduler. Generic CLI
 TUIs expose no reliable cross-provider "idle" signal, so Preview, Send, Return,
-and retry decisions stay explicit. The readiness-labelled buttons are the
-operator's acknowledgement; the matching API requests require
+and retry decisions stay explicit. **Prepare summary**, **Send to reviewer**,
+and **Return to source** are the operator's acknowledgement that the named
+terminal is at an empty prompt; the matching API requests require
 `sourceReady: true` or `reviewerReady: true`. Delivery is bound to the exact
 PTY `sessionId` generation, but the server intentionally does not guess
 whether a CLI is showing its normal prompt, a confirmation, or first-run
@@ -1001,7 +1002,8 @@ terminal byte stream.
 xterm.js is configured with:
 
 - ANSI/VT parsing and original Codex colors
-- Cascadia Mono/Cascadia Code/Consolas font fallback
+- Cascadia Mono/Cascadia Code/Consolas font fallback, then Roboto Mono, Noto
+  Sans Mono, and Droid Sans Mono before generic monospace
 - 10,000 lines of client scrollback by default
 - FitAddon resize using `ResizeObserver`
 - debounced PTY resize messages
@@ -1018,8 +1020,9 @@ so Firefox Quick Find does not replace terminal input. Form fields, dialogs,
 mobile/coarse-pointer input, IME composition, and modified shortcuts keep their
 normal behavior.
 
-The mobile toolbar begins with Enter and the arrow keys, followed by Page
-Up/Down, Ctrl mode, Esc, Tab, Ctrl+C, Ctrl+L, Top, Live, and Hide. Its Ctrl mode
+The mobile toolbar begins with Enter and the arrow keys, followed by Esc,
+Ctrl+C, Tab, Ctrl mode, Page Up/Down, Ctrl+L, Top, Live, and Hide, keeping the
+interrupt keys inside the first screenful on a narrow phone. Its Ctrl mode
 converts the next typed ASCII letter to the matching control character, then
 automatically turns off.