skykoi 2026.3.11 → 2026.3.13

package/docs/gateway/discovery.md

@@ -9,12 +9,12 @@ title: "Discovery and Transports"
 
 # Discovery & transports
 
-SkyKoi has two distinct problems that look similar on the surface:
+SKYKOI has two distinct problems that look similar on the surface:
 
 1. **Operator remote control**: the macOS menu bar app controlling a gateway running elsewhere.
 2. **Node pairing**: iOS/Android (and future nodes) finding a gateway and pairing securely.
 
-The design goal is to keep all network discovery/advertising in the **Node Gateway** (`SkyKoi gateway`) and keep clients (mac app, iOS) as consumers.
+The design goal is to keep all network discovery/advertising in the **Node Gateway** (`SKYKOI gateway`) and keep clients (mac app, iOS) as consumers.
 
 ## Terms
 
@@ -56,7 +56,7 @@ Troubleshooting and beacon details: [Bonjour](/gateway/bonjour).
 #### Service beacon details
 
 - Service types:
-  - `_SkyKoi-gw._tcp` (gateway transport beacon)
+  - `_SKYKOI-gw._tcp` (gateway transport beacon)
 - TXT keys (non-secret):
   - `role=gateway`
   - `lanHost=<hostname>.local`
@@ -65,13 +65,13 @@ Troubleshooting and beacon details: [Bonjour](/gateway/bonjour).
   - `gatewayTls=1` (only when TLS is enabled)
   - `gatewayTlsSha256=<sha256>` (only when TLS is enabled and fingerprint is available)
   - `canvasPort=18793` (default canvas host port; serves `/__SKYKOI__/canvas/`)
-  - `cliPath=<path>` (optional; absolute path to a runnable `SkyKoi` entrypoint or binary)
+  - `cliPath=<path>` (optional; absolute path to a runnable `SKYKOI` entrypoint or binary)
   - `tailnetDns=<magicdns>` (optional hint; auto-detected when Tailscale is available)
 
 Disable/override:
 
 - `SKYKOI_DISABLE_BONJOUR=1` disables advertising.
-- `gateway.bind` in `~/.skykoi/skykoi.json` controls the Gateway bind mode.
+- `gateway.bind` in `~/.SKYKOI/SKYKOI.json` controls the Gateway bind mode.
 - `SKYKOI_SSH_PORT` overrides the SSH port advertised in TXT (defaults to 22).
 - `SKYKOI_TAILNET_DNS` publishes a `tailnetDns` hint (MagicDNS).
 - `SKYKOI_CLI_PATH` overrides the advertised CLI path.

package/docs/gateway/doctor.md

@@ -8,44 +8,44 @@ title: "Doctor"
 
 # Doctor
 
-`SkyKoi doctor` is the repair + migration tool for SkyKoi. It fixes stale
+`SKYKOI doctor` is the repair + migration tool for SKYKOI. It fixes stale
 config/state, checks health, and provides actionable repair steps.
 
 ## Quick start
 
 ```bash
-SkyKoi doctor
+SKYKOI doctor
 ```
 
 ### Headless / automation
 
 ```bash
-SkyKoi doctor --yes
+SKYKOI doctor --yes
 ```
 
 Accept defaults without prompting (including restart/service/sandbox repair steps when applicable).
 
 ```bash
-SkyKoi doctor --repair
+SKYKOI doctor --repair
 ```
 
 Apply recommended repairs without prompting (repairs + restarts where safe).
 
 ```bash
-SkyKoi doctor --repair --force
+SKYKOI doctor --repair --force
 ```
 
 Apply aggressive repairs too (overwrites custom supervisor configs).
 
 ```bash
-SkyKoi doctor --non-interactive
+SKYKOI doctor --non-interactive
 ```
 
 Run without prompts and only apply safe migrations (config normalization + on-disk state moves). Skips restart/service/sandbox actions that require human confirmation.
 Legacy state migrations run automatically when detected.
 
 ```bash
-SkyKoi doctor --deep
+SKYKOI doctor --deep
 ```
 
 Scan system services for extra gateway installs (launchd/systemd/schtasks).
@@ -53,7 +53,7 @@ Scan system services for extra gateway installs (launchd/systemd/schtasks).
 If you want to review changes before writing, open the config file first:
 
 ```bash
-cat ~/.skykoi/skykoi.json
+cat ~/.SKYKOI/SKYKOI.json
 ```
 
 ## What it does (summary)
@@ -68,7 +68,7 @@ cat ~/.skykoi/skykoi.json
 - State integrity and permissions checks (sessions, transcripts, state dir).
 - Config file permission checks (chmod 600) when running locally.
 - Model auth health: checks OAuth expiry, can refresh expiring tokens, and reports auth-profile cooldown/disabled states.
-- Extra workspace dir detection (`~/SkyKoi`).
+- Extra workspace dir detection (`~/SKYKOI`).
 - Sandbox image repair when sandboxing is enabled.
 - Legacy service migration and extra gateway detection.
 - Gateway runtime checks (service installed but not running; cached launchd label).
@@ -98,13 +98,13 @@ schema.
 ### 2) Legacy config key migrations
 
 When the config contains deprecated keys, other commands refuse to run and ask
-you to run `SkyKoi doctor`.
+you to run `SKYKOI doctor`.
 
 Doctor will:
 
 - Explain which legacy keys were found.
 - Show the migration it applied.
-- Rewrite `~/.skykoi/skykoi.json` with the updated schema.
+- Rewrite `~/.SKYKOI/SKYKOI.json` with the updated schema.
 
 The Gateway also auto-runs doctor migrations on startup when it detects a
 legacy config format, so stale configs are repaired without manual intervention.
@@ -138,18 +138,18 @@ remove the override and restore per-model API routing + costs.
 Doctor can migrate older on-disk layouts into the current structure:
 
 - Sessions store + transcripts:
-  - from `~/.skykoi/sessions/` to `~/.skykoi/agents/<agentId>/sessions/`
+  - from `~/.SKYKOI/sessions/` to `~/.SKYKOI/agents/<agentId>/sessions/`
 - Agent dir:
-  - from `~/.skykoi/agent/` to `~/.skykoi/agents/<agentId>/agent/`
+  - from `~/.SKYKOI/agent/` to `~/.SKYKOI/agents/<agentId>/agent/`
 - WhatsApp auth state (Baileys):
-  - from legacy `~/.skykoi/credentials/*.json` (except `oauth.json`)
-  - to `~/.skykoi/credentials/whatsapp/<accountId>/...` (default account id: `default`)
+  - from legacy `~/.SKYKOI/credentials/*.json` (except `oauth.json`)
+  - to `~/.SKYKOI/credentials/whatsapp/<accountId>/...` (default account id: `default`)
 
 These migrations are best-effort and idempotent; doctor will emit warnings when
 it leaves any legacy folders behind as backups. The Gateway/CLI also auto-migrates
 the legacy sessions + agent dir on startup so history/auth/models land in the
 per-agent path without a manual doctor run. WhatsApp auth is intentionally only
-migrated via `SkyKoi doctor`.
+migrated via `SKYKOI doctor`.
 
 ### 4) State integrity checks (session persistence, routing, and safety)
 
@@ -168,12 +168,12 @@ Doctor checks:
   transcript files.
 - **Main session “1-line JSONL”**: flags when the main transcript has only one
   line (history is not accumulating).
-- **Multiple state dirs**: warns when multiple `~/.skykoi` folders exist across
+- **Multiple state dirs**: warns when multiple `~/.SKYKOI` folders exist across
   home directories or when `SKYKOI_STATE_DIR` points elsewhere (history can
   split between installs).
 - **Remote mode reminder**: if `gateway.mode=remote`, doctor reminds you to run
   it on the remote host (the state lives there).
-- **Config file permissions**: warns if `~/.skykoi/skykoi.json` is
+- **Config file permissions**: warns if `~/.SKYKOI/SKYKOI.json` is
   group/world readable and offers to tighten to `600`.
 
 ### 5) Model auth health (OAuth expiry)
@@ -202,9 +202,9 @@ switch to legacy names if the current image is missing.
 ### 8) Gateway service migrations and cleanup hints
 
 Doctor detects legacy gateway services (launchd/systemd/schtasks) and
-offers to remove them and install the SkyKoi service using the current gateway
+offers to remove them and install the SKYKOI service using the current gateway
 port. It can also scan for extra gateway-like services and print cleanup hints.
-Profile-named SkyKoi gateway services are considered first-class and are not
+Profile-named SKYKOI gateway services are considered first-class and are not
 flagged as "extra."
 
 ### 9) Security warnings
@@ -225,7 +225,7 @@ workspace.
 ### 12) Gateway auth checks (local token)
 
 Doctor warns when `gateway.auth` is missing on a local gateway and offers to
-generate a token. Use `SkyKoi doctor --generate-gateway-token` to force token
+generate a token. Use `SKYKOI doctor --generate-gateway-token` to force token
 creation in automation.
 
 ### 13) Gateway health check + restart
@@ -247,11 +247,11 @@ rewrite the service file/task to the current defaults.
 
 Notes:
 
-- `SkyKoi doctor` prompts before rewriting supervisor config.
-- `SkyKoi doctor --yes` accepts the default repair prompts.
-- `SkyKoi doctor --repair` applies recommended fixes without prompts.
-- `SkyKoi doctor --repair --force` overwrites custom supervisor configs.
-- You can always force a full rewrite via `SkyKoi gateway install --force`.
+- `SKYKOI doctor` prompts before rewriting supervisor config.
+- `SKYKOI doctor --yes` accepts the default repair prompts.
+- `SKYKOI doctor --repair` applies recommended fixes without prompts.
+- `SKYKOI doctor --repair --force` overwrites custom supervisor configs.
+- You can always force a full rewrite via `SKYKOI gateway install --force`.
 
 ### 16) Gateway runtime + port diagnostics
 

package/docs/gateway/gateway-lock.md

@@ -30,5 +30,5 @@ Last updated: 2025-12-11
 
 ## Operational notes
 
-- If the port is occupied by _another_ process, the error is the same; free the port or choose another with `SkyKoi gateway --port <port>`.
+- If the port is occupied by _another_ process, the error is the same; free the port or choose another with `SKYKOI gateway --port <port>`.
 - The macOS app still maintains its own lightweight PID guard before spawning the gateway; the runtime lock is enforced by the WebSocket bind.

package/docs/gateway/health.md

@@ -11,25 +11,25 @@ Short guide to verify channel connectivity without guessing.
 
 ## Quick checks
 
-- `SkyKoi status` — local summary: gateway reachability/mode, update hint, linked channel auth age, sessions + recent activity.
-- `SkyKoi status --all` — full local diagnosis (read-only, color, safe to paste for debugging).
-- `SkyKoi status --deep` — also probes the running Gateway (per-channel probes when supported).
-- `SkyKoi health --json` — asks the running Gateway for a full health snapshot (WS-only; no direct Baileys socket).
+- `SKYKOI status` — local summary: gateway reachability/mode, update hint, linked channel auth age, sessions + recent activity.
+- `SKYKOI status --all` — full local diagnosis (read-only, color, safe to paste for debugging).
+- `SKYKOI status --deep` — also probes the running Gateway (per-channel probes when supported).
+- `SKYKOI health --json` — asks the running Gateway for a full health snapshot (WS-only; no direct Baileys socket).
 - Send `/status` as a standalone message in WhatsApp/WebChat to get a status reply without invoking the agent.
-- Logs: tail `/tmp/SkyKoi/SkyKoi-*.log` and filter for `web-heartbeat`, `web-reconnect`, `web-auto-reply`, `web-inbound`.
+- Logs: tail `/tmp/SKYKOI/SKYKOI-*.log` and filter for `web-heartbeat`, `web-reconnect`, `web-auto-reply`, `web-inbound`.
 
 ## Deep diagnostics
 
-- Creds on disk: `ls -l ~/.skykoi/credentials/whatsapp/<accountId>/creds.json` (mtime should be recent).
-- Session store: `ls -l ~/.skykoi/agents/<agentId>/sessions/sessions.json` (path can be overridden in config). Count and recent recipients are surfaced via `status`.
-- Relink flow: `SkyKoi channels logout && SkyKoi channels login --verbose` when status codes 409–515 or `loggedOut` appear in logs. (Note: the QR login flow auto-restarts once for status 515 after pairing.)
+- Creds on disk: `ls -l ~/.SKYKOI/credentials/whatsapp/<accountId>/creds.json` (mtime should be recent).
+- Session store: `ls -l ~/.SKYKOI/agents/<agentId>/sessions/sessions.json` (path can be overridden in config). Count and recent recipients are surfaced via `status`.
+- Relink flow: `SKYKOI channels logout && SKYKOI channels login --verbose` when status codes 409–515 or `loggedOut` appear in logs. (Note: the QR login flow auto-restarts once for status 515 after pairing.)
 
 ## When something fails
 
-- `logged out` or status 409–515 → relink with `SkyKoi channels logout` then `SkyKoi channels login`.
-- Gateway unreachable → start it: `SkyKoi gateway --port 18789` (use `--force` if the port is busy).
+- `logged out` or status 409–515 → relink with `SKYKOI channels logout` then `SKYKOI channels login`.
+- Gateway unreachable → start it: `SKYKOI gateway --port 18789` (use `--force` if the port is busy).
 - No inbound messages → confirm linked phone is online and the sender is allowed (`channels.whatsapp.allowFrom`); for group chats, ensure allowlist + mention rules match (`channels.whatsapp.groups`, `agents.list[].groupChat.mentionPatterns`).
 
 ## Dedicated "health" command
 
-`SkyKoi health --json` asks the running Gateway for its health snapshot (no direct channel sockets from the CLI). It reports linked creds/auth age when available, per-channel probe summaries, session-store summary, and a probe duration. It exits non-zero if the Gateway is unreachable or the probe fails/timeouts. Use `--timeout <ms>` to override the 10s default.
+`SKYKOI health --json` asks the running Gateway for its health snapshot (no direct channel sockets from the CLI). It reports linked creds/auth age when available, per-channel probe summaries, session-store summary, and a probe duration. It exits non-zero if the Gateway is unreachable or the probe fails/timeouts. Use `--timeout <ms>` to override the 10s default.

package/docs/gateway/heartbeat.md

@@ -67,7 +67,7 @@ stats” or “verify gateway health”), set `agents.defaults.heartbeat.prompt`
 ## Response contract
 
 - If nothing needs attention, reply with **`HEARTBEAT_OK`**.
-- During heartbeat runs, SkyKoi treats `HEARTBEAT_OK` as an ack when it appears
+- During heartbeat runs, SKYKOI treats `HEARTBEAT_OK` as an ack when it appears
   at the **start or end** of the reply. The token is stripped and the reply is
   dropped if the remaining content is **≤ `ackMaxChars`** (default: 300).
 - If `HEARTBEAT_OK` appears in the **middle** of a reply, it is not treated
@@ -199,7 +199,7 @@ Use `accountId` to target a specific account on multi-account channels like Tele
 - `includeReasoning`: when enabled, also deliver the separate `Reasoning:` message when available (same shape as `/reasoning on`).
 - `session`: optional session key for heartbeat runs.
   - `main` (default): agent main session.
-  - Explicit session key (copy from `SkyKoi sessions --json` or the [sessions CLI](/cli/sessions)).
+  - Explicit session key (copy from `SKYKOI sessions --json` or the [sessions CLI](/cli/sessions)).
   - Session key formats: see [Sessions](/concepts/session) and [Groups](/channels/groups).
 - `target`:
   - `last` (default): deliver to the last used external channel.
@@ -259,7 +259,7 @@ Precedence: per-account → per-channel → channel defaults → built-in defaul
 - `showAlerts`: sends the alert content when the model returns a non-OK reply.
 - `useIndicator`: emits indicator events for UI status surfaces.
 
-If **all three** are false, SkyKoi skips the heartbeat run entirely (no model call).
+If **all three** are false, SKYKOI skips the heartbeat run entirely (no model call).
 
 ### Per-channel vs per-account examples
 
@@ -298,7 +298,7 @@ agent to read it. Think of it as your “heartbeat checklist”: small, stable,
 safe to include every 30 minutes.
 
 If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown
-headers like `# Heading`), SkyKoi skips the heartbeat run to save API calls.
+headers like `# Heading`), SKYKOI skips the heartbeat run to save API calls.
 If the file is missing, the heartbeat still runs and the model decides what to do.
 
 Keep it tiny (short checklist or reminders) to avoid prompt bloat.
@@ -335,7 +335,7 @@ Safety note: don’t put secrets (API keys, phone numbers, private tokens) into
 You can enqueue a system event and trigger an immediate heartbeat with:
 
 ```bash
-SkyKoi system event --text "Check for urgent follow-ups" --mode now
+SKYKOI system event --text "Check for urgent follow-ups" --mode now
 ```
 
 If multiple agents have `heartbeat` configured, a manual wake runs each of those

package/docs/gateway/index.md

@@ -12,22 +12,22 @@ Last updated: 2025-12-09
 ## What it is
 
 - The always-on process that owns the single Baileys/Telegram connection and the control/event plane.
-- Replaces the legacy `gateway` command. CLI entry point: `SkyKoi gateway`.
+- Replaces the legacy `gateway` command. CLI entry point: `SKYKOI gateway`.
 - Runs until stopped; exits non-zero on fatal errors so the supervisor restarts it.
 
 ## How to run (local)
 
 ```bash
-SkyKoi gateway --port 18789
+SKYKOI gateway --port 18789
 # for full debug/trace logs in stdio:
-SkyKoi gateway --port 18789 --verbose
+SKYKOI gateway --port 18789 --verbose
 # if the port is busy, terminate listeners then start:
-SkyKoi gateway --force
+SKYKOI gateway --force
 # dev loop (auto-reload on TS changes):
 pnpm gateway:watch
 ```
 
-- Config hot reload watches `~/.skykoi/skykoi.json` (or `SKYKOI_CONFIG_PATH`).
+- Config hot reload watches `~/.SKYKOI/SKYKOI.json` (or `SKYKOI_CONFIG_PATH`).
   - Default mode: `gateway.reload.mode="hybrid"` (hot-apply safe changes, restart on critical).
   - Hot reload uses in-process restart via **SIGUSR1** when needed.
   - Disable with `gateway.reload.mode="off"`.
@@ -36,7 +36,7 @@ pnpm gateway:watch
   - OpenAI Chat Completions (HTTP): [`/v1/chat/completions`](/gateway/openai-http-api).
   - OpenResponses (HTTP): [`/v1/responses`](/gateway/openresponses-http-api).
   - Tools Invoke (HTTP): [`/tools/invoke`](/gateway/tools-invoke-http-api).
-- Starts a Canvas file server by default on `canvasHost.port` (default `18793`), serving `http://<gateway-host>:18793/__SKYKOI__/canvas/` from `~/.skykoi/workspace/canvas`. Disable with `canvasHost.enabled=false` or `SKYKOI_SKIP_CANVAS_HOST=1`.
+- Starts a Canvas file server by default on `canvasHost.port` (default `18793`), serving `http://<gateway-host>:18793/__SKYKOI__/canvas/` from `~/.SKYKOI/workspace/canvas`. Disable with `canvasHost.enabled=false` or `SKYKOI_SKIP_CANVAS_HOST=1`.
 - Logs to stdout; use launchd/systemd to keep it alive and rotate logs.
 - Pass `--verbose` to mirror debug logging (handshakes, req/res, events) from the log file into stdio when troubleshooting.
 - `--force` uses `lsof` to find listeners on the chosen port, sends SIGTERM, logs what it killed, then starts the gateway (fails fast if `lsof` is missing).
@@ -65,13 +65,13 @@ Supported if you isolate state + config and use unique ports. Full guide: [Multi
 
 Service names are profile-aware:
 
-- macOS: `bot.molt.<profile>` (legacy `com.skykoi.*` may still exist)
-- Linux: `SkyKoi-gateway-<profile>.service`
-- Windows: `SkyKoi Gateway (<profile>)`
+- macOS: `bot.molt.<profile>` (legacy `com.SKYKOI.*` may still exist)
+- Linux: `SKYKOI-gateway-<profile>.service`
+- Windows: `SKYKOI Gateway (<profile>)`
 
 Install metadata is embedded in the service config:
 
-- `SKYKOI_SERVICE_MARKER=SkyKoi`
+- `SKYKOI_SERVICE_MARKER=SKYKOI`
 - `SKYKOI_SERVICE_KIND=gateway`
 - `SKYKOI_SERVICE_VERSION=<version>`
 
@@ -82,21 +82,21 @@ Rescue-Bot Pattern: keep a second Gateway isolated with its own profile, state d
 Fast path: run a fully-isolated dev instance (config/state/workspace) without touching your primary setup.
 
 ```bash
-SkyKoi --dev setup
-SkyKoi --dev gateway --allow-unconfigured
+SKYKOI --dev setup
+SKYKOI --dev gateway --allow-unconfigured
 # then target the dev instance:
-SkyKoi --dev status
-SkyKoi --dev health
+SKYKOI --dev status
+SKYKOI --dev health
 ```
 
 Defaults (can be overridden via env/flags/config):
 
-- `SKYKOI_STATE_DIR=~/.skykoi-dev`
-- `SKYKOI_CONFIG_PATH=~/.skykoi-dev/skykoi.json`
+- `SKYKOI_STATE_DIR=~/.SKYKOI-dev`
+- `SKYKOI_CONFIG_PATH=~/.SKYKOI-dev/SKYKOI.json`
 - `SKYKOI_GATEWAY_PORT=19001` (Gateway WS + HTTP)
 - browser control service port = `19003` (derived: `gateway.port+2`, loopback only)
 - `canvasHost.port=19005` (derived: `gateway.port+4`)
-- `agents.defaults.workspace` default becomes `~/.skykoi/workspace-dev` when you run `setup`/`onboard` under `--dev`.
+- `agents.defaults.workspace` default becomes `~/.SKYKOI/workspace-dev` when you run `setup`/`onboard` under `--dev`.
 
 Derived ports (rules of thumb):
 
@@ -116,15 +116,15 @@ Checklist per instance:
 Service install per profile:
 
 ```bash
-SkyKoi --profile main gateway install
-SkyKoi --profile rescue gateway install
+SKYKOI --profile main gateway install
+SKYKOI --profile rescue gateway install
 ```
 
 Example:
 
 ```bash
-SKYKOI_CONFIG_PATH=~/.skykoi/a.json SKYKOI_STATE_DIR=~/.skykoi-a SkyKoi gateway --port 19001
-SKYKOI_CONFIG_PATH=~/.skykoi/b.json SKYKOI_STATE_DIR=~/.skykoi-b SkyKoi gateway --port 19002
+SKYKOI_CONFIG_PATH=~/.SKYKOI/a.json SKYKOI_STATE_DIR=~/.SKYKOI-a SKYKOI gateway --port 19001
+SKYKOI_CONFIG_PATH=~/.SKYKOI/b.json SKYKOI_STATE_DIR=~/.SKYKOI-b SKYKOI gateway --port 19002
 ```
 
 ## Protocol (operator view)
@@ -140,7 +140,7 @@ SKYKOI_CONFIG_PATH=~/.skykoi/b.json SKYKOI_STATE_DIR=~/.skykoi-b SkyKoi gateway
 
 ## Methods (initial set)
 
-- `health` — full health snapshot (same shape as `SkyKoi health --json`).
+- `health` — full health snapshot (same shape as `SKYKOI health --json`).
 - `status` — short summary.
 - `system-presence` — current presence list.
 - `system-event` — post a presence/system note (structured).
@@ -200,26 +200,26 @@ See also: [Presence](/concepts/presence) for how presence is produced/deduped an
 ## Supervision (macOS example)
 
 - Use launchd to keep the service alive:
-  - Program: path to `SkyKoi`
+  - Program: path to `SKYKOI`
   - Arguments: `gateway`
   - KeepAlive: true
   - StandardOut/Err: file paths or `syslog`
 - On failure, launchd restarts; fatal misconfig should keep exiting so the operator notices.
 - LaunchAgents are per-user and require a logged-in session; for headless setups use a custom LaunchDaemon (not shipped).
-  - `SkyKoi gateway install` writes `~/Library/LaunchAgents/bot.molt.gateway.plist`
-    (or `bot.molt.<profile>.plist`; legacy `com.skykoi.*` is cleaned up).
-  - `SkyKoi doctor` audits the LaunchAgent config and can update it to current defaults.
+  - `SKYKOI gateway install` writes `~/Library/LaunchAgents/bot.molt.gateway.plist`
+    (or `bot.molt.<profile>.plist`; legacy `com.SKYKOI.*` is cleaned up).
+  - `SKYKOI doctor` audits the LaunchAgent config and can update it to current defaults.
 
 ## Gateway service management (CLI)
 
 Use the Gateway CLI for install/start/stop/restart/status:
 
 ```bash
-SkyKoi gateway status
-SkyKoi gateway install
-SkyKoi gateway stop
-SkyKoi gateway restart
-SkyKoi logs --follow
+SKYKOI gateway status
+SKYKOI gateway install
+SKYKOI gateway stop
+SKYKOI gateway restart
+SKYKOI logs --follow
 ```
 
 Notes:
@@ -232,40 +232,40 @@ Notes:
 - `gateway status` prints config path + probe target to avoid “localhost vs LAN bind” confusion and profile mismatches.
 - `gateway status` includes the last gateway error line when the service looks running but the port is closed.
 - `logs` tails the Gateway file log via RPC (no manual `tail`/`grep` needed).
-- If other gateway-like services are detected, the CLI warns unless they are SkyKoi profile services.
+- If other gateway-like services are detected, the CLI warns unless they are SKYKOI profile services.
   We still recommend **one gateway per machine** for most setups; use isolated profiles/ports for redundancy or a rescue bot. See [Multiple gateways](/gateway/multiple-gateways).
-  - Cleanup: `SkyKoi gateway uninstall` (current service) and `SkyKoi doctor` (legacy migrations).
-- `gateway install` is a no-op when already installed; use `SkyKoi gateway install --force` to reinstall (profile/env/path changes).
+  - Cleanup: `SKYKOI gateway uninstall` (current service) and `SKYKOI doctor` (legacy migrations).
+- `gateway install` is a no-op when already installed; use `SKYKOI gateway install --force` to reinstall (profile/env/path changes).
 
 Bundled mac app:
 
-- SkyKoi.app can bundle a Node-based gateway relay and install a per-user LaunchAgent labeled
-  `bot.molt.gateway` (or `bot.molt.<profile>`; legacy `com.skykoi.*` labels still unload cleanly).
-- To stop it cleanly, use `SkyKoi gateway stop` (or `launchctl bootout gui/$UID/bot.molt.gateway`).
-- To restart, use `SkyKoi gateway restart` (or `launchctl kickstart -k gui/$UID/bot.molt.gateway`).
-  - `launchctl` only works if the LaunchAgent is installed; otherwise use `SkyKoi gateway install` first.
+- SKYKOI.app can bundle a Node-based gateway relay and install a per-user LaunchAgent labeled
+  `bot.molt.gateway` (or `bot.molt.<profile>`; legacy `com.SKYKOI.*` labels still unload cleanly).
+- To stop it cleanly, use `SKYKOI gateway stop` (or `launchctl bootout gui/$UID/bot.molt.gateway`).
+- To restart, use `SKYKOI gateway restart` (or `launchctl kickstart -k gui/$UID/bot.molt.gateway`).
+  - `launchctl` only works if the LaunchAgent is installed; otherwise use `SKYKOI gateway install` first.
   - Replace the label with `bot.molt.<profile>` when running a named profile.
 
 ## Supervision (systemd user unit)
 
-SkyKoi installs a **systemd user service** by default on Linux/WSL2. We
+SKYKOI installs a **systemd user service** by default on Linux/WSL2. We
 recommend user services for single-user machines (simpler env, per-user config).
 Use a **system service** for multi-user or always-on servers (no lingering
 required, shared supervision).
 
-`SkyKoi gateway install` writes the user unit. `SkyKoi doctor` audits the
+`SKYKOI gateway install` writes the user unit. `SKYKOI doctor` audits the
 unit and can update it to match the current recommended defaults.
 
-Create `~/.config/systemd/user/SkyKoi-gateway[-<profile>].service`:
+Create `~/.config/systemd/user/SKYKOI-gateway[-<profile>].service`:
 
 ```
 [Unit]
-Description=SkyKoi Gateway (profile: <profile>, v<version>)
+Description=SKYKOI Gateway (profile: <profile>, v<version>)
 After=network-online.target
 Wants=network-online.target
 
 [Service]
-ExecStart=/usr/local/bin/SkyKoi gateway --port 18789
+ExecStart=/usr/local/bin/SKYKOI gateway --port 18789
 Restart=always
 RestartSec=5
 Environment=SKYKOI_GATEWAY_TOKEN=
@@ -285,17 +285,17 @@ Onboarding runs this on Linux/WSL2 (may prompt for sudo; writes `/var/lib/system
 Then enable the service:
 
 ```
-systemctl --user enable --now SkyKoi-gateway[-<profile>].service
+systemctl --user enable --now SKYKOI-gateway[-<profile>].service
 ```
 
 **Alternative (system service)** - for always-on or multi-user servers, you can
 install a systemd **system** unit instead of a user unit (no lingering needed).
-Create `/etc/systemd/system/SkyKoi-gateway[-<profile>].service` (copy the unit above,
+Create `/etc/systemd/system/SKYKOI-gateway[-<profile>].service` (copy the unit above,
 switch `WantedBy=multi-user.target`, set `User=` + `WorkingDirectory=`), then:
 
 ```
 sudo systemctl daemon-reload
-sudo systemctl enable --now SkyKoi-gateway[-<profile>].service
+sudo systemctl enable --now SKYKOI-gateway[-<profile>].service
 ```
 
 ## Windows (WSL2)
@@ -317,14 +317,14 @@ Windows installs should use **WSL2** and follow the Linux systemd section above.
 
 ## CLI helpers
 
-- `SkyKoi gateway health|status` — request health/status over the Gateway WS.
-- `SkyKoi message send --target <num> --message "hi" [--media ...]` — send via Gateway (idempotent for WhatsApp).
-- `SkyKoi agent --message "hi" --to <num>` — run an agent turn (waits for final by default).
-- `SkyKoi gateway call <method> --params '{"k":"v"}'` — raw method invoker for debugging.
-- `SkyKoi gateway stop|restart` — stop/restart the supervised gateway service (launchd/systemd).
+- `SKYKOI gateway health|status` — request health/status over the Gateway WS.
+- `SKYKOI message send --target <num> --message "hi" [--media ...]` — send via Gateway (idempotent for WhatsApp).
+- `SKYKOI agent --message "hi" --to <num>` — run an agent turn (waits for final by default).
+- `SKYKOI gateway call <method> --params '{"k":"v"}'` — raw method invoker for debugging.
+- `SKYKOI gateway stop|restart` — stop/restart the supervised gateway service (launchd/systemd).
 - Gateway helper subcommands assume a running gateway on `--url`; they no longer auto-spawn one.
 
 ## Migration guidance
 
-- Retire uses of `SkyKoi gateway` and the legacy TCP control port.
+- Retire uses of `SKYKOI gateway` and the legacy TCP control port.
 - Update clients to speak the WS protocol with mandatory connect and structured presence.

package/docs/gateway/local-models.md

@@ -1,5 +1,5 @@
 ---
-summary: "Run SkyKoi on local LLMs (LM Studio, vLLM, LiteLLM, custom OpenAI endpoints)"
+summary: "Run SKYKOI on local LLMs (LM Studio, vLLM, LiteLLM, custom OpenAI endpoints)"
 read_when:
   - You want to serve models from your own GPU box
   - You are wiring LM Studio or an OpenAI-compatible proxy
@@ -9,7 +9,7 @@ title: "Local Models"
 
 # Local models
 
-Local is doable, but SkyKoi expects large context + strong defenses against prompt injection. Small cards truncate context and leak safety. Aim high: **≥2 maxed-out Mac Studios or equivalent GPU rig (~$30k+)**. A single **24 GB** GPU works only for lighter prompts with higher latency. Use the **largest / full-size model variant you can run**; aggressively quantized or “small” checkpoints raise prompt-injection risk (see [Security](/gateway/security)).
+Local is doable, but SKYKOI expects large context + strong defenses against prompt injection. Small cards truncate context and leak safety. Aim high: **≥2 maxed-out Mac Studios or equivalent GPU rig (~$30k+)**. A single **24 GB** GPU works only for lighter prompts with higher latency. Use the **largest / full-size model variant you can run**; aggressively quantized or “small” checkpoints raise prompt-injection risk (see [Security](/gateway/security)).
 
 ## Recommended: LM Studio + MiniMax M2.1 (Responses API, full-size)
 

package/docs/gateway/logging.md

@@ -10,16 +10,16 @@ title: "Logging"
 
 For a user-facing overview (CLI + Control UI + config), see [/logging](/logging).
 
-SkyKoi has two log “surfaces”:
+SKYKOI has two log “surfaces”:
 
 - **Console output** (what you see in the terminal / Debug UI).
 - **File logs** (JSON lines) written by the gateway logger.
 
 ## File-based logger
 
-- Default rolling log file is under `/tmp/SkyKoi/` (one file per day): `SkyKoi-YYYY-MM-DD.log`
+- Default rolling log file is under `/tmp/SKYKOI/` (one file per day): `SKYKOI-YYYY-MM-DD.log`
   - Date uses the gateway host's local timezone.
-- The log file path and level can be configured via `~/.skykoi/skykoi.json`:
+- The log file path and level can be configured via `~/.SKYKOI/SKYKOI.json`:
   - `logging.file`
   - `logging.level`
 
@@ -29,7 +29,7 @@ The Control UI Logs tab tails this file via the gateway (`logs.tail`).
 CLI can do the same:
 
 ```bash
-SkyKoi logs --follow
+SKYKOI logs --follow
 ```
 
 **Verbose vs. log levels**
@@ -73,7 +73,7 @@ The gateway prints WebSocket protocol logs in two modes:
 
 ### WS log style
 
-`SkyKoi gateway` supports a per-gateway style switch:
+`SKYKOI gateway` supports a per-gateway style switch:
 
 - `--ws-log auto` (default): normal mode is optimized; verbose mode uses compact output
 - `--ws-log compact`: compact output (paired request/response) when verbose
@@ -84,13 +84,13 @@ Examples:
 
 ```bash
 # optimized (only errors/slow)
-SkyKoi gateway
+SKYKOI gateway
 
 # show all WS traffic (paired)
-SkyKoi gateway --verbose --ws-log compact
+SKYKOI gateway --verbose --ws-log compact
 
 # show all WS traffic (full meta)
-SkyKoi gateway --verbose --ws-log full
+SKYKOI gateway --verbose --ws-log full
 ```
 
 ## Console formatting (subsystem logging)