fengming 0.3.9 → 0.3.11

package/docs/platforms/mac/permissions.md

@@ -1,73 +0,0 @@
----
-summary: "macOS permission persistence (TCC) and signing requirements"
-read_when:
-  - Debugging missing or stuck macOS permission prompts
-  - Deciding whether to grant Accessibility to node or a CLI runtime
-  - Packaging or signing the macOS app
-  - Changing bundle IDs or app install paths
-title: "macOS permissions"
----
-
-macOS permission grants are fragile. TCC associates a permission grant with the
-app's code signature, bundle identifier, and on-disk path. If any of those change,
-macOS treats the app as new and may drop or hide prompts.
-
-## Requirements for stable permissions
-
-- Same path: run the app from a fixed location (for FengMing, `dist/FengMing.app`).
-- Same bundle identifier: changing the bundle ID creates a new permission identity.
-- Signed app: unsigned or ad-hoc signed builds do not persist permissions.
-- Consistent signature: use a real Apple Development or Developer ID certificate
-  so the signature stays stable across rebuilds.
-
-Ad-hoc signatures generate a new identity every build. macOS will forget previous
-grants, and prompts can disappear entirely until the stale entries are cleared.
-
-## Accessibility grants for Node and CLI runtimes
-
-Prefer granting Accessibility to FengMing.app, Peekaboo.app, or another signed
-helper with its own bundle identifier instead of a generic `node` binary.
-
-macOS TCC grants Accessibility to the code identity of the process it sees. If a
-Homebrew, nvm, pnpm, or npm workflow causes a shared `node` executable to
-receive Accessibility, any JavaScript package launched through that same
-executable may inherit GUI automation privileges.
-
-Treat a `node` entry in System Settings as broad permission for that Node
-runtime, not as permission for one npm package. Avoid granting Accessibility to
-`node` unless you trust every script and package launched through that exact
-Node install.
-
-If you accidentally granted Accessibility to `node`, remove that entry from
-System Settings -> Privacy & Security -> Accessibility. Then grant the signed
-app or helper that should own UI automation.
-
-## Recovery checklist when prompts disappear
-
-1. Quit the app.
-2. Remove the app entry in System Settings -> Privacy & Security.
-3. Relaunch the app from the same path and re-grant permissions.
-4. If the prompt still does not appear, reset TCC entries with `tccutil` and try again.
-5. Some permissions only reappear after a full macOS restart.
-
-Example resets (replace bundle ID as needed):
-
-```bash
-sudo tccutil reset Accessibility ai.fengming.mac
-sudo tccutil reset ScreenCapture ai.fengming.mac
-sudo tccutil reset AppleEvents
-```
-
-## Files and folders permissions (Desktop/Documents/Downloads)
-
-macOS may also gate Desktop, Documents, and Downloads for terminal/background processes. If file reads or directory listings hang, grant access to the same process context that performs file operations (for example Terminal/iTerm, LaunchAgent-launched app, or SSH process).
-
-Workaround: move files into the FengMing workspace (`~/.fengming/workspace`) if you want to avoid per-folder grants.
-
-If you are testing permissions, always sign with a real certificate. Ad-hoc
-builds are only acceptable for quick local runs where permissions do not matter.
-
-## Related
-
-- [macOS app](/platforms/macos)
-- [macOS signing](/platforms/mac/signing)

package/docs/platforms/mac/remote.md

@@ -1,123 +0,0 @@
----
-summary: "macOS app flow for controlling a remote FengMing gateway"
-read_when:
-  - Setting up or debugging remote mac control
-title: "Remote control"
----
-
-This flow lets the macOS app act as a full remote control for an FengMing gateway running on another host (desktop/server). The app can connect directly to trusted LAN/Tailnet gateway URLs or manage an SSH tunnel when the remote gateway is loopback-only. Health checks, Voice Wake forwarding, and Web Chat reuse the same remote configuration from _Settings → General_.
-
-## Modes
-
-- **Local (this Mac)**: Everything runs on the laptop. No SSH involved.
-- **Remote over SSH (default)**: FengMing commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key and a local port-forward.
-- **Remote direct (ws/wss)**: No SSH tunnel. The mac app connects to the gateway URL directly (for example, via LAN, Tailscale, Tailscale Serve, or a public HTTPS reverse proxy).
-
-## Remote transports
-
-Remote mode supports two transports:
-
-- **SSH tunnel** (default): Uses `ssh -N -L ...` to forward the gateway port to localhost. The gateway will see the node's IP as `127.0.0.1` because the tunnel is loopback.
-- **Direct (ws/wss)**: Connects straight to the gateway URL. The gateway sees the real client IP.
-
-In SSH tunnel mode, discovered LAN/tailnet hostnames are saved as
-`gateway.remote.sshTarget`. The app keeps `gateway.remote.url` on the local
-tunnel endpoint, for example `ws://127.0.0.1:18789`, so CLI, Web Chat, and
-the local node-host service all use the same safe loopback transport.
-If the local tunnel port differs from the remote gateway port, set
-`gateway.remote.remotePort` to the port on the remote host.
-
-Browser automation in remote mode is owned by the CLI node host, not by the
-native macOS app node. The app starts the installed node host service when
-possible; if you need browser control from that Mac, install/start it with
-`fengming node install ...` and `fengming node start` (or run
-`fengming node run ...` in the foreground), then target that browser-capable
-node.
-
-## Prereqs on the remote host
-
-1. Install Node + pnpm and build/install the FengMing CLI (`pnpm install && pnpm build && pnpm link --global`).
-2. Ensure `fengming` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed).
-3. For SSH transport only: open SSH with key auth. We recommend **Tailscale** IPs for stable reachability off-LAN.
-
-## macOS app setup
-
-To preconfigure the app without the welcome flow:
-
-```bash
-fengming-mac configure-remote \
-  --ssh-target user@gateway.local \
-  --local-port 18789 \
-  --remote-port 18789 \
-  --token "$FENGMING_GATEWAY_TOKEN"
-```
-
-For a gateway already reachable on a trusted LAN or Tailnet, skip SSH entirely:
-
-```bash
-fengming-mac configure-remote \
-  --direct-url ws://192.168.0.202:18789 \
-  --token "$FENGMING_GATEWAY_TOKEN"
-```
-
-This writes the remote config, marks onboarding complete, and lets the app own
-the selected transport when it starts.
-
-1. Open _Settings → General_.
-2. Under **FengMing runs**, pick **Remote** and set:
-   - **Transport**: **SSH tunnel** or **Direct (ws/wss)**.
-   - **SSH target**: `user@host` (optional `:port`).
-     - If the gateway is on the same LAN and advertises Bonjour, pick it from the discovered list to auto-fill this field.
-   - **Gateway URL** (Direct only): `wss://gateway.example.ts.net` (or `ws://...` for local/LAN).
-   - **Identity file** (advanced): path to your key.
-   - **Project root** (advanced): remote checkout path used for commands.
-   - **CLI path** (advanced): optional path to a runnable `fengming` entrypoint/binary (auto-filled when advertised).
-3. Hit **Test remote**. Success indicates the remote `fengming status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn't found remotely.
-4. Health checks and Web Chat will now run through the selected transport automatically.
-
-## Web Chat
-
-- **SSH tunnel**: Web Chat connects to the gateway over the forwarded WebSocket control port (default 18789).
-- **Direct (ws/wss)**: Web Chat connects straight to the configured gateway URL.
-- There is no separate WebChat HTTP server anymore.
-
-## Permissions
-
-- The remote host needs the same TCC approvals as local (Automation, Accessibility, Screen Recording, Microphone, Speech Recognition, Notifications). Run onboarding on that machine to grant them once.
-- Nodes advertise their permission state via `node.list` / `node.describe` so agents know what's available.
-
-## Security notes
-
-- Prefer loopback binds on the remote host and connect via SSH, Tailscale Serve, or a trusted Tailnet/LAN direct URL.
-- SSH tunneling uses strict host-key checking; trust the host key first so it exists in `~/.ssh/known_hosts`.
-- If you bind the Gateway to a non-loopback interface, require valid Gateway auth: token, password, or an identity-aware reverse proxy with `gateway.auth.mode: "trusted-proxy"`.
-- See [Security](/gateway/security) and [Tailscale](/gateway/tailscale).
-
-## WhatsApp login flow (remote)
-
-- Run `fengming channels login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone.
-- Re-run login on that host if auth expires. Health check will surface link problems.
-
-## Troubleshooting
-
-- **exit 127 / not found**: `fengming` isn't on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`.
-- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`fengming status --json`).
-- **Web Chat stuck**: confirm the gateway is running on the remote host and the forwarded port matches the gateway WS port; the UI requires a healthy WS connection.
-- **Node IP shows 127.0.0.1**: expected with the SSH tunnel. Switch **Transport** to **Direct (ws/wss)** if you want the gateway to see the real client IP.
-- **Dashboard works but Mac capabilities are offline**: this means the app's operator/control connection is healthy, but the companion node connection is not connected or is missing its command surface. Open the menu bar device section and check whether the Mac is `paired · disconnected`. For `wss://*.ts.net` Tailscale Serve endpoints, the app detects stale legacy TLS leaf pins after certificate rotation, clears the stale pin when macOS trusts the new certificate, and retries automatically. If the certificate is not system-trusted or the host is not a Tailscale Serve name, set `gateway.remote.tlsFingerprint` to the expected certificate fingerprint, review the certificate, or switch to **Remote over SSH**.
-- **Voice Wake**: trigger phrases are forwarded automatically in remote mode; no separate forwarder is needed.
-
-## Notification sounds
-
-Pick sounds per notification from scripts with `fengming` and `node.invoke`, e.g.:
-
-```bash
-fengming nodes notify --node <id> --title "Ping" --body "Remote gateway ready" --sound Glass
-```
-
-There is no global "default sound" toggle in the app anymore; callers choose a sound (or none) per request.
-
-## Related
-
-- [macOS app](/platforms/macos)
-- [Remote access](/gateway/remote)

package/docs/platforms/mac/signing.md

@@ -1,52 +0,0 @@
----
-summary: "Signing steps for macOS debug builds generated by packaging scripts"
-read_when:
-  - Building or signing mac debug builds
-title: "macOS signing"
----
-
-# mac signing (debug builds)
-
-This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/fengming/fengming/blob/main/scripts/package-mac-app.sh), which now:
-
-- sets a stable debug bundle identifier: `ai.fengming.mac.debug`
-- writes the Info.plist with that bundle id (override via `BUNDLE_ID=...`)
-- calls [`scripts/codesign-mac-app.sh`](https://github.com/fengming/fengming/blob/main/scripts/codesign-mac-app.sh) to sign the main binary and app bundle so macOS treats each rebuild as the same signed bundle and keeps TCC permissions (notifications, accessibility, screen recording, mic, speech). For stable permissions, use a real signing identity; ad-hoc is opt-in and fragile (see [macOS permissions](/platforms/mac/permissions)).
-- uses `CODESIGN_TIMESTAMP=auto` by default; it enables trusted timestamps for Developer ID signatures. Set `CODESIGN_TIMESTAMP=off` to skip timestamping (offline debug builds).
-- inject build metadata into Info.plist: `FengMingBuildTimestamp` (UTC) and `FengMingGitCommit` (short hash) so the About pane can show build, git, and debug/release channel.
-- **Packaging defaults to Node 24**: the script runs TS builds and the Control UI build. Node 22 LTS, currently `22.19+`, remains supported for compatibility.
-- reads `SIGN_IDENTITY` from the environment. Add `export SIGN_IDENTITY="Apple Development: Your Name (TEAMID)"` (or your Developer ID Application cert) to your shell rc to always sign with your cert. Ad-hoc signing requires explicit opt-in via `ALLOW_ADHOC_SIGNING=1` or `SIGN_IDENTITY="-"` (not recommended for permission testing).
-- runs a Team ID audit after signing and fails if any Mach-O inside the app bundle is signed by a different Team ID. Set `SKIP_TEAM_ID_CHECK=1` to bypass.
-
-## Usage
-
-```bash
-# from repo root
-scripts/package-mac-app.sh               # auto-selects identity; errors if none found
-SIGN_IDENTITY="Developer ID Application: Your Name" scripts/package-mac-app.sh   # real cert
-ALLOW_ADHOC_SIGNING=1 scripts/package-mac-app.sh    # ad-hoc (permissions will not stick)
-SIGN_IDENTITY="-" scripts/package-mac-app.sh        # explicit ad-hoc (same caveat)
-DISABLE_LIBRARY_VALIDATION=1 scripts/package-mac-app.sh   # dev-only Sparkle Team ID mismatch workaround
-```
-
-### Ad-hoc Signing Note
-
-When signing with `SIGN_IDENTITY="-"` (ad-hoc), the script automatically disables the **Hardened Runtime** (`--options runtime`). This is necessary to prevent crashes when the app attempts to load embedded frameworks (like Sparkle) that do not share the same Team ID. Ad-hoc signatures also break TCC permission persistence; see [macOS permissions](/platforms/mac/permissions) for recovery steps.
-
-## Build metadata for About
-
-`package-mac-app.sh` stamps the bundle with:
-
-- `FengMingBuildTimestamp`: ISO8601 UTC at package time
-- `FengMingGitCommit`: short git hash (or `unknown` if unavailable)
-
-The About tab reads these keys to show version, build date, git commit, and whether it's a debug build (via `#if DEBUG`). Run the packager to refresh these values after code changes.
-
-## Why
-
-TCC permissions are tied to the bundle identifier _and_ code signature. Unsigned debug builds with changing UUIDs were causing macOS to forget grants after each rebuild. Signing the binaries (ad-hoc by default) and keeping a fixed bundle id/path (`dist/FengMing.app`) preserves the grants between builds, matching the VibeTunnel approach.
-
-## Related
-
-- [macOS app](/platforms/macos)
-- [macOS permissions](/platforms/mac/permissions)

package/docs/platforms/mac/skills.md

@@ -1,43 +0,0 @@
----
-summary: "macOS Skills settings UI and gateway-backed status"
-read_when:
-  - Updating the macOS Skills settings UI
-  - Changing skills gating or install behavior
-title: "Skills (macOS)"
----
-
-The macOS app surfaces FengMing skills via the gateway; it does not parse skills locally.
-
-## Data source
-
-- `skills.status` (gateway) returns all skills plus eligibility and missing requirements
-  (including allowlist blocks for bundled skills).
-- Requirements are derived from `metadata.fengming.requires` in each `SKILL.md`.
-
-## Install actions
-
-- `metadata.fengming.install` defines install options (brew/node/go/uv).
-- The app calls `skills.install` to run installers on the gateway host.
-- Built-in dangerous-code `critical` findings block `skills.install` by default; suspicious findings still warn only. The dangerous override exists on the gateway request, but the default app flow stays fail-closed.
-- If every install option is `download`, the gateway surfaces all download
-  choices.
-- Otherwise, the gateway picks one preferred installer using the current
-  install preferences and host binaries: Homebrew first when
-  `skills.install.preferBrew` is enabled and `brew` exists, then `uv`, then the
-  configured node manager from `skills.install.nodeManager`, then later
-  fallbacks like `go` or `download`.
-- Node install labels reflect the configured node manager, including `yarn`.
-
-## Env/API keys
-
-- The app stores keys in `~/.fengming/fengming.json` under `skills.entries.<skillKey>`.
-- `skills.update` patches `enabled`, `apiKey`, and `env`.
-
-## Remote mode
-
-- Install + config updates happen on the gateway host (not the local Mac).
-
-## Related
-
-- [Skills](/tools/skills)
-- [macOS app](/platforms/macos)

package/docs/platforms/mac/voice-overlay.md

@@ -1,66 +0,0 @@
----
-summary: "Voice overlay lifecycle when wake-word and push-to-talk overlap"
-read_when:
-  - Adjusting voice overlay behavior
-title: "Voice overlay"
----
-
-# Voice Overlay Lifecycle (macOS)
-
-Audience: macOS app contributors. Goal: keep the voice overlay predictable when wake-word and push-to-talk overlap.
-
-## Current intent
-
-- If the overlay is already visible from wake-word and the user presses the hotkey, the hotkey session _adopts_ the existing text instead of resetting it. The overlay stays up while the hotkey is held. When the user releases: send if there is trimmed text, otherwise dismiss.
-- Wake-word alone still auto-sends on silence; push-to-talk sends immediately on release.
-
-## Implemented (Dec 9, 2025)
-
-- Overlay sessions now carry a token per capture (wake-word or push-to-talk). Partial/final/send/dismiss/level updates are dropped when the token doesn't match, avoiding stale callbacks.
-- Push-to-talk adopts any visible overlay text as a prefix (so pressing the hotkey while the wake overlay is up keeps the text and appends new speech). It waits up to 1.5s for a final transcript before falling back to the current text.
-- Chime/overlay logging is emitted at `info` in categories `voicewake.overlay`, `voicewake.ptt`, and `voicewake.chime` (session start, partial, final, send, dismiss, chime reason).
-
-## Next steps
-
-1. **VoiceSessionCoordinator (actor)**
-   - Owns exactly one `VoiceSession` at a time.
-   - API (token-based): `beginWakeCapture`, `beginPushToTalk`, `updatePartial`, `endCapture`, `cancel`, `applyCooldown`.
-   - Drops callbacks that carry stale tokens (prevents old recognizers from reopening the overlay).
-2. **VoiceSession (model)**
-   - Fields: `token`, `source` (wakeWord|pushToTalk), committed/volatile text, chime flags, timers (auto-send, idle), `overlayMode` (display|editing|sending), cooldown deadline.
-3. **Overlay binding**
-   - `VoiceSessionPublisher` (`ObservableObject`) mirrors the active session into SwiftUI.
-   - `VoiceWakeOverlayView` renders only via the publisher; it never mutates global singletons directly.
-   - Overlay user actions (`sendNow`, `dismiss`, `edit`) call back into the coordinator with the session token.
-4. **Unified send path**
-   - On `endCapture`: if trimmed text is empty → dismiss; else `performSend(session:)` (plays send chime once, forwards, dismisses).
-   - Push-to-talk: no delay; wake-word: optional delay for auto-send.
-   - Apply a short cooldown to the wake runtime after push-to-talk finishes so wake-word doesn't immediately retrigger.
-5. **Logging**
-   - Coordinator emits `.info` logs in subsystem `ai.fengming`, categories `voicewake.overlay` and `voicewake.chime`.
-   - Key events: `session_started`, `adopted_by_push_to_talk`, `partial`, `finalized`, `send`, `dismiss`, `cancel`, `cooldown`.
-
-## Debugging checklist
-
-- Stream logs while reproducing a sticky overlay:
-
-  ```bash
-  sudo log stream --predicate 'subsystem == "ai.fengming" AND category CONTAINS "voicewake"' --level info --style compact
-  ```
-
-- Verify only one active session token; stale callbacks should be dropped by the coordinator.
-- Ensure push-to-talk release always calls `endCapture` with the active token; if text is empty, expect `dismiss` without chime or send.
-
-## Migration steps (suggested)
-
-1. Add `VoiceSessionCoordinator`, `VoiceSession`, and `VoiceSessionPublisher`.
-2. Refactor `VoiceWakeRuntime` to create/update/end sessions instead of touching `VoiceWakeOverlayController` directly.
-3. Refactor `VoicePushToTalk` to adopt existing sessions and call `endCapture` on release; apply runtime cooldown.
-4. Wire `VoiceWakeOverlayController` to the publisher; remove direct calls from runtime/PTT.
-5. Add integration tests for session adoption, cooldown, and empty-text dismissal.
-
-## Related
-
-- [macOS app](/platforms/macos)
-- [Voice wake (macOS)](/platforms/mac/voicewake)
-- [Talk mode](/nodes/talk)

package/docs/platforms/mac/voicewake.md

@@ -1,73 +0,0 @@
----
-summary: "Voice wake and push-to-talk modes plus routing details in the mac app"
-read_when:
-  - Working on voice wake or PTT pathways
-title: "Voice wake (macOS)"
----
-
-# Voice Wake & Push-to-Talk
-
-## Modes
-
-- **Wake-word mode** (default): always-on Speech recognizer waits for trigger tokens (`swabbleTriggerWords`). On match it starts capture, shows the overlay with partial text, and auto-sends after silence.
-- **Push-to-talk (Right Option hold)**: hold the right Option key to capture immediately—no trigger needed. The overlay appears while held; releasing finalizes and forwards after a short delay so you can tweak text.
-
-## Runtime behavior (wake-word)
-
-- Speech recognizer lives in `VoiceWakeRuntime`.
-- Trigger only fires when there's a **meaningful pause** between the wake word and the next word (~0.55s gap). The overlay/chime can start on the pause even before the command begins.
-- Silence windows: 2.0s when speech is flowing, 5.0s if only the trigger was heard.
-- Hard stop: 120s to prevent runaway sessions.
-- Debounce between sessions: 350ms.
-- Overlay is driven via `VoiceWakeOverlayController` with committed/volatile coloring.
-- After send, recognizer restarts cleanly to listen for the next trigger.
-
-## Lifecycle invariants
-
-- If Voice Wake is enabled and permissions are granted, the wake-word recognizer should be listening (except during an explicit push-to-talk capture).
-- Overlay visibility (including manual dismiss via the X button) must never prevent the recognizer from resuming.
-
-## Sticky overlay failure mode (previous)
-
-Previously, if the overlay got stuck visible and you manually closed it, Voice Wake could appear "dead" because the runtime's restart attempt could be blocked by overlay visibility and no subsequent restart was scheduled.
-
-Hardening:
-
-- Wake runtime restart is no longer blocked by overlay visibility.
-- Overlay dismiss completion triggers a `VoiceWakeRuntime.refresh(...)` via `VoiceSessionCoordinator`, so manual X-dismiss always resumes listening.
-
-## Push-to-talk specifics
-
-- Hotkey detection uses a global `.flagsChanged` monitor for **right Option** (`keyCode 61` + `.option`). We only observe events (no swallowing).
-- Capture pipeline lives in `VoicePushToTalk`: starts Speech immediately, streams partials to the overlay, and calls `VoiceWakeForwarder` on release.
-- When push-to-talk starts we pause the wake-word runtime to avoid dueling audio taps; it restarts automatically after release.
-- Permissions: requires Microphone + Speech; seeing events needs Accessibility/Input Monitoring approval.
-- External keyboards: some may not expose right Option as expected—offer a fallback shortcut if users report misses.
-
-## User-facing settings
-
-- **Voice Wake** toggle: enables wake-word runtime.
-- **Hold Cmd+Fn to talk**: enables the push-to-talk monitor. Disabled on macOS < 26.
-- Language & mic pickers, live level meter, trigger-word table, tester (local-only; does not forward).
-- Mic picker preserves the last selection if a device disconnects, shows a disconnected hint, and temporarily falls back to the system default until it returns.
-- **Sounds**: chimes on trigger detect and on send; defaults to the macOS "Glass" system sound. You can pick any `NSSound`-loadable file (e.g. MP3/WAV/AIFF) for each event or choose **No Sound**.
-
-## Forwarding behavior
-
-- When Voice Wake is enabled, transcripts are forwarded to the active gateway/agent (the same local vs remote mode used by the rest of the mac app).
-- Replies are delivered to the **last-used main provider** (WhatsApp/Telegram/Discord/WebChat). If delivery fails, the error is logged and the run is still visible via WebChat/session logs.
-
-## Forwarding payload
-
-- `VoiceWakeForwarder.prefixedTranscript(_:)` prepends the machine hint before sending. Shared between wake-word and push-to-talk paths.
-
-## Quick verification
-
-- Toggle push-to-talk on, hold Cmd+Fn, speak, release: overlay should show partials then send.
-- While holding, menu-bar ears should stay enlarged (uses `triggerVoiceEars(ttl:nil)`); they drop after release.
-
-## Related
-
-- [Voice wake](/nodes/voicewake)
-- [Voice overlay](/platforms/mac/voice-overlay)
-- [macOS app](/platforms/macos)

package/docs/platforms/mac/webchat.md

@@ -1,54 +0,0 @@
----
-summary: "How the mac app embeds the gateway WebChat and how to debug it"
-read_when:
-  - Debugging mac WebChat view or loopback port
-title: "WebChat (macOS)"
----
-
-The macOS menu bar app embeds the WebChat UI as a native SwiftUI view. It
-connects to the Gateway and defaults to the **main session** for the selected
-agent (with a session switcher for other sessions).
-
-- **Local mode**: connects directly to the local Gateway WebSocket.
-- **Remote mode**: forwards the Gateway control port over SSH and uses that
-  tunnel as the data plane.
-
-## Launch and debugging
-
-- Manual: Lobster menu → "Open Chat".
-- Auto-open for testing:
-
-  ```bash
-  dist/FengMing.app/Contents/MacOS/FengMing --webchat
-  ```
-
-- Logs: `./scripts/clawlog.sh` (subsystem `ai.fengming`, category `WebChatSwiftUI`).
-
-## How it is wired
-
-- Data plane: Gateway WS methods `chat.history`, `chat.send`, `chat.abort`,
-  `chat.inject` and events `chat`, `agent`, `presence`, `tick`, `health`.
-- `chat.history` returns display-normalized transcript rows: inline directive
-  tags are stripped from visible text, plain-text tool-call XML payloads
-  (including `<tool_call>...</tool_call>`,
-  `<function_call>...</function_call>`, `<tool_calls>...</tool_calls>`,
-  `<function_calls>...</function_calls>`, and truncated tool-call blocks) and
-  leaked ASCII/full-width model control tokens are stripped, pure
-  silent-token assistant rows such as exact `NO_REPLY` / `no_reply` are
-  omitted, and oversized rows can be replaced with placeholders.
-- Session: defaults to the primary session (`main`, or `global` when scope is
-  global). The UI can switch between sessions.
-- Onboarding uses a dedicated session to keep first-run setup separate.
-
-## Security surface
-
-- Remote mode forwards only the Gateway WebSocket control port over SSH.
-
-## Known limitations
-
-- The UI is optimized for chat sessions (not a full browser sandbox).
-
-## Related
-
-- [WebChat](/web/webchat)
-- [macOS app](/platforms/macos)

package/docs/platforms/mac/xpc.md

@@ -1,66 +0,0 @@
----
-summary: "macOS IPC architecture for FengMing app, gateway node transport, and PeekabooBridge"
-read_when:
-  - Editing IPC contracts or menu bar app IPC
-title: "macOS IPC"
----
-
-# FengMing macOS IPC architecture
-
-**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `fengming-mac` debug CLI exists for discovery/connect checks; agent actions still flow through the Gateway WebSocket and `node.invoke`. UI automation uses PeekabooBridge.
-
-## Goals
-
-- Single GUI app instance that owns all TCC-facing work (notifications, screen recording, mic, speech, AppleScript).
-- A small surface for automation: Gateway + node commands, plus PeekabooBridge for UI automation.
-- Predictable permissions: always the same signed bundle ID, launched by launchd, so TCC grants stick.
-
-## How it works
-
-### Gateway + node transport
-
-- The app runs the Gateway (local mode) and connects to it as a node.
-- Agent actions are performed via `node.invoke` (e.g. `system.run`, `system.notify`, `canvas.*`).
-
-### Node service + app IPC
-
-- A headless node host service connects to the Gateway WebSocket.
-- `system.run` requests are forwarded to the macOS app over a local Unix socket.
-- The app performs the exec in UI context, prompts if needed, and returns output.
-
-Diagram (SCI):
-
-```
-Agent -> Gateway -> Node Service (WS)
-                      |  IPC (UDS + token + HMAC + TTL)
-                      v
-                  Mac App (UI + TCC + system.run)
-```
-
-### PeekabooBridge (UI automation)
-
-- UI automation uses a separate UNIX socket named `bridge.sock` and the PeekabooBridge JSON protocol.
-- Host preference order (client-side): Peekaboo.app → Claude.app → FengMing.app → local execution.
-- Security: bridge hosts require an allowed TeamID; DEBUG-only same-UID escape hatch is guarded by `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1` (Peekaboo convention).
-- See: [PeekabooBridge usage](/platforms/mac/peekaboo) for details.
-
-## Operational flows
-
-- Restart/rebuild: `SIGN_IDENTITY="Apple Development: <Developer Name> (<TEAMID>)" scripts/restart-mac.sh`
-  - Kills existing instances
-  - Swift build + package
-  - Writes/bootstraps/kickstarts the LaunchAgent
-- Single instance: app exits early if another instance with the same bundle ID is running.
-
-## Hardening notes
-
-- Prefer requiring a TeamID match for all privileged surfaces.
-- PeekabooBridge: `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1` (DEBUG-only) may allow same-UID callers for local development.
-- All communication remains local-only; no network sockets are exposed.
-- TCC prompts originate only from the GUI app bundle; keep the signed bundle ID stable across rebuilds.
-- IPC hardening: socket mode `0600`, token, peer-UID checks, HMAC challenge/response, short TTL.
-
-## Related
-
-- [macOS app](/platforms/macos)
-- [macOS IPC flow (Exec approvals)](/tools/exec-approvals-advanced#macos-ipc-flow)

package/docs/platforms/oracle.md

@@ -1,12 +0,0 @@
----
-summary: "Redirect to /install/oracle"
-title: "Oracle Cloud (platform)"
-redirect: /install/oracle
----
-
-This page has moved to [Oracle Cloud](/install/oracle).
-
-## Related
-
-- [Install overview](/install)
-- [VPS hosting](/vps)

package/docs/platforms/raspberry-pi.md

@@ -1,13 +0,0 @@
----
-summary: "Redirect to /install/raspberry-pi"
-title: "Raspberry Pi (platform)"
-redirect: /install/raspberry-pi
----
-
-This page has moved to [Raspberry Pi](/install/raspberry-pi).
-
-## Related
-
-- [Install overview](/install)
-- [Linux server](/vps)
-- [Platforms](/platforms)