skykoi 2026.3.11 → 2026.3.13

package/docs/concepts/system-prompt.md

@@ -1,5 +1,5 @@
 ---
-summary: "What the SkyKoi system prompt contains and how it is assembled"
+summary: "What the SKYKOI system prompt contains and how it is assembled"
 read_when:
   - Editing system prompt text, tools list, or time/heartbeat sections
   - Changing workspace bootstrap or skills injection behavior
@@ -8,9 +8,9 @@ title: "System Prompt"
 
 # System Prompt
 
-SkyKoi builds a custom system prompt for every agent run. The prompt is **SkyKoi-owned** and does not use the p-coding-agent default prompt.
+SKYKOI builds a custom system prompt for every agent run. The prompt is **SKYKOI-owned** and does not use the p-coding-agent default prompt.
 
-The prompt is assembled by SkyKoi and injected into each agent run.
+The prompt is assembled by SKYKOI and injected into each agent run.
 
 ## Structure
 
@@ -19,9 +19,9 @@ The prompt is intentionally compact and uses fixed sections:
 - **Tooling**: current tool list + short descriptions.
 - **Safety**: short guardrail reminder to avoid power-seeking behavior or bypassing oversight.
 - **Skills** (when available): tells the model how to load skill instructions on demand.
-- **SkyKoi Self-Update**: how to run `config.apply` and `update.run`.
+- **SKYKOI Self-Update**: how to run `config.apply` and `update.run`.
 - **Workspace**: working directory (`agents.defaults.workspace`).
-- **Documentation**: local path to SkyKoi docs (repo or npm package) and when to read them.
+- **Documentation**: local path to SKYKOI docs (repo or npm package) and when to read them.
 - **Workspace Files (injected)**: indicates bootstrap files are included below.
 - **Sandbox** (when enabled): indicates sandboxed runtime, sandbox paths, and whether elevated exec is available.
 - **Current Date & Time**: user-local time, timezone, and time format.
@@ -34,11 +34,11 @@ Safety guardrails in the system prompt are advisory. They guide model behavior b
 
 ## Prompt modes
 
-SkyKoi can render smaller system prompts for sub-agents. The runtime sets a
+SKYKOI can render smaller system prompts for sub-agents. The runtime sets a
 `promptMode` for each run (not a user-facing config):
 
 - `full` (default): includes all sections above.
-- `minimal`: used for sub-agents; omits **Skills**, **Memory Recall**, **SkyKoi
+- `minimal`: used for sub-agents; omits **Skills**, **Memory Recall**, **SKYKOI
   Self-Update**, **Model Aliases**, **User Identity**, **Reply Tags**,
   **Messaging**, **Silent Replies**, and **Heartbeats**. Tooling, **Safety**,
   Workspace, Sandbox, Current Date & Time (when known), Runtime, and injected
@@ -87,7 +87,7 @@ See [Date & Time](/date-time) for full behavior details.
 
 ## Skills
 
-When eligible skills exist, SkyKoi injects a compact **available skills list**
+When eligible skills exist, SKYKOI injects a compact **available skills list**
 (`formatSkillsForPrompt`) that includes the **file path** for each skill. The
 prompt instructs the model to use `read` to load the SKILL.md at the listed
 location (workspace, managed, or bundled). If no skills are eligible, the
@@ -108,8 +108,8 @@ This keeps the base prompt small while still enabling targeted skill usage.
 ## Documentation
 
 When available, the system prompt includes a **Documentation** section that points to the
-local SkyKoi docs directory (either `docs/` in the repo workspace or the bundled npm
+local SKYKOI docs directory (either `docs/` in the repo workspace or the bundled npm
 package docs) and also notes the public mirror, source repo, community Discord, and
-SkyKoi Skills ([https://skykoi.com/skills](https://skykoi.com/skills)) for skills discovery. The prompt instructs the model to consult local docs first
-for SkyKoi behavior, commands, configuration, or architecture, and to run
-`skykoi status` itself when possible (asking the user only when it lacks access).
+SKYKOI Skills ([https://SKYKOI.com/skills](https://SKYKOI.com/skills)) for skills discovery. The prompt instructs the model to consult local docs first
+for SKYKOI behavior, commands, configuration, or architecture, and to run
+`SKYKOI status` itself when possible (asking the user only when it lacks access).

package/docs/concepts/timezone.md

@@ -8,7 +8,7 @@ title: "Timezones"
 
 # Timezones
 
-SkyKoi standardizes timestamps so the model sees a **single reference time**.
+SKYKOI standardizes timestamps so the model sees a **single reference time**.
 
 ## Message envelopes (local by default)
 
@@ -73,7 +73,7 @@ Raw provider fields are preserved.
 ## User timezone for the system prompt
 
 Set `agents.defaults.userTimezone` to tell the model the user's local time zone. If it is
-unset, SkyKoi resolves the **host timezone at runtime** (no config write).
+unset, SKYKOI resolves the **host timezone at runtime** (no config write).
 
 ```json5
 {

package/docs/concepts/typebox.md

@@ -60,7 +60,7 @@ Authoritative list lives in `src/gateway/server.ts` (`METHODS`, `EVENTS`).
 - Server handshake + method dispatch: `src/gateway/server.ts`
 - Node client: `src/gateway/client.ts`
 - Generated JSON Schema: `dist/protocol.schema.json`
-- Generated Swift models: `apps/macos/Sources/SkyKoiProtocol/GatewayModels.swift`
+- Generated Swift models: `apps/macos/Sources/SKYKOIProtocol/GatewayModels.swift`
 
 ## Current pipeline
 
@@ -93,7 +93,7 @@ Connect (first message):
     "minProtocol": 2,
     "maxProtocol": 2,
     "client": {
-      "id": "SkyKoi-macos",
+      "id": "SKYKOI-macos",
       "displayName": "macos",
       "version": "1.0.0",
       "platform": "macos 15.1",
@@ -280,7 +280,7 @@ Unknown frame types are preserved as raw payloads for forward compatibility.
 Generated JSON Schema is in the repo at `dist/protocol.schema.json`. The
 published raw file is typically available at:
 
-- [https://raw.githubusercontent.com/SkyKoi/SkyKoi/main/dist/protocol.schema.json](https://raw.githubusercontent.com/SkyKoi/SkyKoi/main/dist/protocol.schema.json)
+- [https://raw.githubusercontent.com/SKYKOI/SKYKOI/main/dist/protocol.schema.json](https://raw.githubusercontent.com/SKYKOI/SKYKOI/main/dist/protocol.schema.json)
 
 ## When you change schemas
 

package/docs/concepts/typing-indicators.md

@@ -1,5 +1,5 @@
 ---
-summary: "When SkyKoi shows typing indicators and how to tune them"
+summary: "When SKYKOI shows typing indicators and how to tune them"
 read_when:
   - Changing typing indicator behavior or defaults
 title: "Typing Indicators"
@@ -13,7 +13,7 @@ to control **how often** it refreshes.
 
 ## Defaults
 
-When `agents.defaults.typingMode` is **unset**, SkyKoi keeps the legacy behavior:
+When `agents.defaults.typingMode` is **unset**, SKYKOI keeps the legacy behavior:
 
 - **Direct chats**: typing starts immediately once the model loop begins.
 - **Group chats with a mention**: typing starts immediately.

package/docs/concepts/usage-tracking.md

@@ -17,9 +17,9 @@ title: "Usage Tracking"
 
 - `/status` in chats: emoji‑rich status card with session tokens + estimated cost (API key only). Provider usage shows for the **current model provider** when available.
 - `/usage off|tokens|full` in chats: per-response usage footer (OAuth shows tokens only).
-- `/usage cost` in chats: local cost summary aggregated from SkyKoi session logs.
-- CLI: `SkyKoi status --usage` prints a full per-provider breakdown.
-- CLI: `SkyKoi channels list` prints the same usage snapshot alongside provider config (use `--no-usage` to skip).
+- `/usage cost` in chats: local cost summary aggregated from SKYKOI session logs.
+- CLI: `SKYKOI status --usage` prints a full per-provider breakdown.
+- CLI: `SKYKOI channels list` prints the same usage snapshot alongside provider config (use `--no-usage` to skip).
 - macOS menu bar: “Usage” section under Context (only if available).
 
 ## Providers + credentials

package/docs/date-time.md

@@ -8,7 +8,7 @@ title: "Date and Time"
 
 # Date & Time
 
-SkyKoi defaults to **host-local time for transport timestamps** and **user timezone only in the system prompt**.
+SKYKOI defaults to **host-local time for transport timestamps** and **user timezone only in the system prompt**.
 Provider timestamps are preserved so tools keep their native semantics (current time is available via `session_status`).
 
 ## Message envelopes (local by default)
@@ -102,7 +102,7 @@ System: [2026-01-12 12:19:17 PST] Model switched.
 
 ## Time format detection (auto)
 
-When `timeFormat: "auto"`, SkyKoi inspects the OS preference (macOS/Windows)
+When `timeFormat: "auto"`, SKYKOI inspects the OS preference (macOS/Windows)
 and falls back to locale formatting. The detected value is **cached per process**
 to avoid repeated system calls.
 

package/docs/debug/node-issue.md

@@ -2,7 +2,7 @@
 summary: Node + tsx "__name is not a function" crash notes and workarounds
 read_when:
   - Debugging Node-only dev scripts or watch mode failures
-  - Investigating tsx/esbuild loader crashes in SkyKoi
+  - Investigating tsx/esbuild loader crashes in SKYKOI
 title: "Node + tsx Crash"
 ---
 
@@ -10,10 +10,10 @@ title: "Node + tsx Crash"
 
 ## Summary
 
-Running SkyKoi via Node with `tsx` fails at startup with:
+Running SKYKOI via Node with `tsx` fails at startup with:
 
 ```
-[SkyKoi] Failed to start CLI: TypeError: __name is not a function
+[SKYKOI] Failed to start CLI: TypeError: __name is not a function
     at createSubsystemLogger (.../src/logging/subsystem.ts:203:25)
     at .../src/agents/auth-profiles/constants.ts:25:20
 ```
@@ -56,7 +56,7 @@ node --import tsx scripts/repro/tsx-name-repro.ts
 ## Regression history
 
 - `2871657e` (2026-01-06): scripts changed from Bun to tsx to make Bun optional.
-- Before that (Bun path), `SkyKoi status` and `gateway:watch` worked.
+- Before that (Bun path), `SKYKOI status` and `gateway:watch` worked.
 
 ## Workarounds
 
@@ -65,10 +65,10 @@ node --import tsx scripts/repro/tsx-name-repro.ts
 
   ```bash
   pnpm exec tsc --watch --preserveWatchOutput
-  node --watch SkyKoi.mjs status
+  node --watch SKYKOI.mjs status
   ```
 
-- Confirmed locally: `pnpm exec tsc -p tsconfig.json` + `node SkyKoi.mjs status` works on Node 25.
+- Confirmed locally: `pnpm exec tsc -p tsconfig.json` + `node SKYKOI.mjs status` works on Node 25.
 - Disable esbuild keepNames in the TS loader if possible (prevents `__name` helper insertion); tsx does not currently expose this.
 - Test Node LTS (22/24) with `tsx` to see if the issue is Node 25–specific.
 

package/docs/diagnostics/flags.md

@@ -57,7 +57,7 @@ SKYKOI_DIAGNOSTICS=0
 Flags emit logs into the standard diagnostics log file. By default:
 
 ```
-/tmp/SkyKoi/SkyKoi-YYYY-MM-DD.log
+/tmp/SKYKOI/SKYKOI-YYYY-MM-DD.log
 ```
 
 If you set `logging.file`, use that path instead. Logs are JSONL (one JSON object per line). Redaction still applies based on `logging.redactSensitive`.
@@ -67,22 +67,22 @@ If you set `logging.file`, use that path instead. Logs are JSONL (one JSON objec
 Pick the latest log file:
 
 ```bash
-ls -t /tmp/SkyKoi/SkyKoi-*.log | head -n 1
+ls -t /tmp/SKYKOI/SKYKOI-*.log | head -n 1
 ```
 
 Filter for Telegram HTTP diagnostics:
 
 ```bash
-rg "telegram http error" /tmp/SkyKoi/SkyKoi-*.log
+rg "telegram http error" /tmp/SKYKOI/SKYKOI-*.log
 ```
 
 Or tail while reproducing:
 
 ```bash
-tail -f /tmp/SkyKoi/SkyKoi-$(date +%F).log | rg "telegram http error"
+tail -f /tmp/SKYKOI/SKYKOI-$(date +%F).log | rg "telegram http error"
 ```
 
-For remote gateways, you can also use `SkyKoi logs --follow` (see [/cli/logs](/cli/logs)).
+For remote gateways, you can also use `SKYKOI logs --follow` (see [/cli/logs](/cli/logs)).
 
 ## Notes
 

package/docs/docs.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://mintlify.com/docs.json",
-  "name": "SkyKoi",
+  "name": "SKYKOI",
   "theme": "mint",
   "icons": {
     "library": "lucide"
@@ -27,12 +27,12 @@
     "links": [
       {
         "label": "GitHub",
-        "href": "https://github.com/SkyKoi/SkyKoi",
+        "href": "https://github.com/SKYKOI/SKYKOI",
         "icon": "github"
       },
       {
         "label": "Releases",
-        "href": "https://github.com/SkyKoi/SkyKoi/releases",
+        "href": "https://github.com/SKYKOI/SKYKOI/releases",
         "icon": "package"
       }
     ]
@@ -252,15 +252,15 @@
     },
     {
       "source": "/clawd",
-      "destination": "/start/SkyKoi"
+      "destination": "/start/SKYKOI"
     },
     {
       "source": "/start/clawd",
-      "destination": "/start/SkyKoi"
+      "destination": "/start/SKYKOI"
     },
     {
       "source": "/start/clawd/",
-      "destination": "/start/SkyKoi"
+      "destination": "/start/SKYKOI"
     },
     {
       "source": "/clawhub",
@@ -805,7 +805,7 @@
               },
               {
                 "group": "Guides",
-                "pages": ["start/SkyKoi"]
+                "pages": ["start/SKYKOI"]
               }
             ]
           },
@@ -1301,7 +1301,7 @@
               },
               {
                 "group": "指南",
-                "pages": ["zh-CN/start/SkyKoi"]
+                "pages": ["zh-CN/start/SKYKOI"]
               }
             ]
           },

package/docs/experiments/plans/cron-add-hardening.md

@@ -1,6 +1,6 @@
 ---
 summary: "Harden cron.add input handling, align schemas, and improve cron UI/agent tooling"
-owner: "SkyKoi"
+owner: "SKYKOI"
 status: "complete"
 last_updated: "2026-01-05"
 title: "Cron Add Hardening"

package/docs/experiments/plans/openresponses-gateway.md

@@ -1,6 +1,6 @@
 ---
 summary: "Plan: Add OpenResponses /v1/responses endpoint and deprecate chat completions cleanly"
-owner: "SkyKoi"
+owner: "SKYKOI"
 status: "draft"
 last_updated: "2026-01-19"
 title: "OpenResponses Gateway Plan"
@@ -10,7 +10,7 @@ title: "OpenResponses Gateway Plan"
 
 ## Context
 
-SkyKoi Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
+SKYKOI Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
 `/v1/chat/completions` (see [OpenAI Chat Completions](/gateway/openai-http-api)).
 
 Open Responses is an open inference standard based on the OpenAI Responses API. It is designed

package/docs/experiments/research/memory.md

@@ -1,15 +1,15 @@
 ---
 summary: "Research notes: offline memory system for Clawd workspaces (Markdown source-of-truth + derived index)"
 read_when:
-  - Designing workspace memory (~/.skykoi/workspace) beyond daily Markdown logs
-  - Deciding: standalone CLI vs deep SkyKoi integration
+  - Designing workspace memory (~/.SKYKOI/workspace) beyond daily Markdown logs
+  - Deciding: standalone CLI vs deep SKYKOI integration
   - Adding offline recall + reflection (retain/recall/reflect)
 title: "Workspace Memory Research"
 ---
 
 # Workspace Memory v2 (offline): research notes
 
-Target: Clawd-style workspace (`agents.defaults.workspace`, default `~/.skykoi/workspace`) where “memory” is stored as one Markdown file per day (`memory/YYYY-MM-DD.md`) plus a small set of stable files (e.g. `memory.md`, `SOUL.md`).
+Target: Clawd-style workspace (`agents.defaults.workspace`, default `~/.SKYKOI/workspace`) where “memory” is stored as one Markdown file per day (`memory/YYYY-MM-DD.md`) plus a small set of stable files (e.g. `memory.md`, `SOUL.md`).
 
 This doc proposes an **offline-first** memory architecture that keeps Markdown as the canonical, reviewable source of truth, but adds **structured recall** (search, entity summaries, confidence updates) via a derived index.
 
@@ -58,12 +58,12 @@ Two pieces to blend:
 
 ### Canonical store (git-friendly)
 
-Keep `~/.skykoi/workspace` as canonical human-readable memory.
+Keep `~/.SKYKOI/workspace` as canonical human-readable memory.
 
 Suggested workspace layout:
 
 ```
-~/.skykoi/workspace/
+~/.SKYKOI/workspace/
   memory.md                    # small: durable facts + preferences (core-ish)
   memory/
     YYYY-MM-DD.md              # daily log (append; narrative)
@@ -89,7 +89,7 @@ Notes:
 Add a derived index under the workspace (not necessarily git tracked):
 
 ```
-~/.skykoi/workspace/.memory/index.sqlite
+~/.SKYKOI/workspace/.memory/index.sqlite
 ```
 
 Back it with:
@@ -168,17 +168,17 @@ Opinion evolution (simple, explainable):
 
 ## CLI integration: standalone vs deep integration
 
-Recommendation: **deep integration in SkyKoi**, but keep a separable core library.
+Recommendation: **deep integration in SKYKOI**, but keep a separable core library.
 
-### Why integrate into SkyKoi?
+### Why integrate into SKYKOI?
 
-- SkyKoi already knows:
+- SKYKOI already knows:
   - the workspace path (`agents.defaults.workspace`)
   - the session model + heartbeats
   - logging + troubleshooting patterns
 - You want the agent itself to call the tools:
-  - `SkyKoi memory recall "…" --k 25 --since 30d`
-  - `SkyKoi memory reflect --since 7d`
+  - `SKYKOI memory recall "…" --k 25 --since 30d`
+  - `SKYKOI memory reflect --since 7d`
 
 ### Why still split a library?
 
@@ -192,7 +192,7 @@ The memory tooling is intended to be a small CLI + library layer, but this is ex
 
 If “S-Collide” refers to **SuCo (Subspace Collision)**: it’s an ANN retrieval approach that targets strong recall/latency tradeoffs by using learned/structured collisions in subspaces (paper: arXiv 2411.14754, 2024).
 
-Pragmatic take for `~/.skykoi/workspace`:
+Pragmatic take for `~/.SKYKOI/workspace`:
 
 - **don’t start** with SuCo.
 - start with SQLite FTS + (optional) simple embeddings; you’ll get most UX wins immediately.

package/docs/gateway/authentication.md

@@ -8,7 +8,7 @@ title: "Authentication"
 
 # Authentication
 
-SkyKoi supports OAuth and API keys for model providers. For Anthropic
+SKYKOI supports OAuth and API keys for model providers. For Anthropic
 accounts, we recommend using an **API key**. For Claude subscription access,
 use the long‑lived token created by `claude setup-token`.
 
@@ -20,18 +20,18 @@ layout.
 If you’re using Anthropic directly, use an API key.
 
 1. Create an API key in the Anthropic Console.
-2. Put it on the **gateway host** (the machine running `SkyKoi gateway`).
+2. Put it on the **gateway host** (the machine running `SKYKOI gateway`).
 
 ```bash
 export ANTHROPIC_API_KEY="..."
-SkyKoi models status
+SKYKOI models status
 ```
 
 3. If the Gateway runs under systemd/launchd, prefer putting the key in
-   `~/.skykoi/.env` so the daemon can read it:
+   `~/.SKYKOI/.env` so the daemon can read it:
 
 ```bash
-cat >> ~/.skykoi/.env <<'EOF'
+cat >> ~/.SKYKOI/.env <<'EOF'
 ANTHROPIC_API_KEY=...
 EOF
 ```
@@ -39,15 +39,15 @@ EOF
 Then restart the daemon (or restart your Gateway process) and re-check:
 
 ```bash
-SkyKoi models status
-SkyKoi doctor
+SKYKOI models status
+SKYKOI doctor
 ```
 
 If you’d rather not manage env vars yourself, the onboarding wizard can store
-API keys for daemon use: `SkyKoi onboard`.
+API keys for daemon use: `SKYKOI onboard`.
 
 See [Help](/help) for details on env inheritance (`env.shellEnv`,
-`~/.skykoi/.env`, systemd/launchd).
+`~/.SKYKOI/.env`, systemd/launchd).
 
 ## Anthropic: setup-token (subscription auth)
 
@@ -58,16 +58,16 @@ subscription, the setup-token flow is also supported. Run it on the **gateway ho
 claude setup-token
 ```
 
-Then paste it into SkyKoi:
+Then paste it into SKYKOI:
 
 ```bash
-SkyKoi models auth setup-token --provider anthropic
+SKYKOI models auth setup-token --provider anthropic
 ```
 
 If the token was created on another machine, paste it manually:
 
 ```bash
-SkyKoi models auth paste-token --provider anthropic
+SKYKOI models auth paste-token --provider anthropic
 ```
 
 If you see an Anthropic error like:
@@ -81,14 +81,14 @@ This credential is only authorized for use with Claude Code and cannot be used f
 Manual token entry (any provider; writes `auth-profiles.json` + updates config):
 
 ```bash
-SkyKoi models auth paste-token --provider anthropic
-SkyKoi models auth paste-token --provider openrouter
+SKYKOI models auth paste-token --provider anthropic
+SKYKOI models auth paste-token --provider openrouter
 ```
 
 Automation-friendly check (exit `1` when expired/missing, `2` when expiring):
 
 ```bash
-SkyKoi models status --check
+SKYKOI models status --check
 ```
 
 Optional ops scripts (systemd/Termux) are documented here:
@@ -99,8 +99,8 @@ Optional ops scripts (systemd/Termux) are documented here:
 ## Checking model auth status
 
 ```bash
-SkyKoi models status
-SkyKoi doctor
+SKYKOI models status
+SKYKOI doctor
 ```
 
 ## Controlling which credential is used
@@ -116,9 +116,9 @@ Use `/model` (or `/model list`) for a compact picker; use `/model status` for th
 Set an explicit auth profile order override for an agent (stored in that agent’s `auth-profiles.json`):
 
 ```bash
-SkyKoi models auth order get --provider anthropic
-SkyKoi models auth order set --provider anthropic anthropic:default
-SkyKoi models auth order clear --provider anthropic
+SKYKOI models auth order get --provider anthropic
+SKYKOI models auth order set --provider anthropic anthropic:default
+SKYKOI models auth order clear --provider anthropic
 ```
 
 Use `--agent <id>` to target a specific agent; omit it to use the configured default agent.
@@ -131,12 +131,12 @@ If the Anthropic token profile is missing, run `claude setup-token` on the
 **gateway host**, then re-check:
 
 ```bash
-SkyKoi models status
+SKYKOI models status
 ```
 
 ### Token expiring/expired
 
-Run `SkyKoi models status` to confirm which profile is expiring. If the profile
+Run `SKYKOI models status` to confirm which profile is expiring. If the profile
 is missing, rerun `claude setup-token` and paste the token again.
 
 ## Requirements

package/docs/gateway/background-process.md

@@ -8,7 +8,7 @@ title: "Background Exec and Process Tool"
 
 # Background Exec + Process Tool
 
-SkyKoi runs shell commands through the `exec` tool and keeps long‑running tasks in memory. The `process` tool manages those background sessions.
+SKYKOI runs shell commands through the `exec` tool and keeps long‑running tasks in memory. The `process` tool manages those background sessions.
 
 ## exec tool
 

package/docs/gateway/bonjour.md

@@ -8,7 +8,7 @@ title: "Bonjour Discovery"
 
 # Bonjour / mDNS discovery
 
-SkyKoi uses Bonjour (mDNS / DNS‑SD) as a **LAN‑only convenience** to discover
+SKYKOI uses Bonjour (mDNS / DNS‑SD) as a **LAN‑only convenience** to discover
 an active Gateway (WebSocket endpoint). It is best‑effort and does **not** replace SSH or
 Tailnet-based connectivity.
 
@@ -21,12 +21,12 @@ boundary. You can keep the same discovery UX by switching to **unicast DNS‑SD*
 High‑level steps:
 
 1. Run a DNS server on the gateway host (reachable over Tailnet).
-2. Publish DNS‑SD records for `_SkyKoi-gw._tcp` under a dedicated zone
-   (example: `SkyKoi.internal.`).
+2. Publish DNS‑SD records for `_SKYKOI-gw._tcp` under a dedicated zone
+   (example: `SKYKOI.internal.`).
 3. Configure Tailscale **split DNS** so your chosen domain resolves via that
    DNS server for clients (including iOS).
 
-SkyKoi supports any discovery domain; `SkyKoi.internal.` is just an example.
+SKYKOI supports any discovery domain; `SKYKOI.internal.` is just an example.
 iOS/Android nodes browse both `local.` and your configured wide‑area domain.
 
 ### Gateway config (recommended)
@@ -41,19 +41,19 @@ iOS/Android nodes browse both `local.` and your configured wide‑area domain.
 ### One‑time DNS server setup (gateway host)
 
 ```bash
-SkyKoi dns setup --apply
+SKYKOI dns setup --apply
 ```
 
 This installs CoreDNS and configures it to:
 
 - listen on port 53 only on the gateway’s Tailscale interfaces
-- serve your chosen domain (example: `SkyKoi.internal.`) from `~/.skykoi/dns/<domain>.db`
+- serve your chosen domain (example: `SKYKOI.internal.`) from `~/.SKYKOI/dns/<domain>.db`
 
 Validate from a tailnet‑connected machine:
 
 ```bash
-dns-sd -B _SkyKoi-gw._tcp SkyKoi.internal.
-dig @<TAILNET_IPV4> -p 53 _SkyKoi-gw._tcp.skykoi.internal PTR +short
+dns-sd -B _SKYKOI-gw._tcp SKYKOI.internal.
+dig @<TAILNET_IPV4> -p 53 _SKYKOI-gw._tcp.SKYKOI.internal PTR +short
 ```
 
 ### Tailscale DNS settings
@@ -64,7 +64,7 @@ In the Tailscale admin console:
 - Add split DNS so your discovery domain uses that nameserver.
 
 Once clients accept tailnet DNS, iOS nodes can browse
-`_SkyKoi-gw._tcp` in your discovery domain without multicast.
+`_SKYKOI-gw._tcp` in your discovery domain without multicast.
 
 ### Gateway listener security (recommended)
 
@@ -73,16 +73,16 @@ access, bind explicitly and keep auth enabled.
 
 For tailnet‑only setups:
 
-- Set `gateway.bind: "tailnet"` in `~/.skykoi/skykoi.json`.
+- Set `gateway.bind: "tailnet"` in `~/.SKYKOI/SKYKOI.json`.
 - Restart the Gateway (or restart the macOS menubar app).
 
 ## What advertises
 
-Only the Gateway advertises `_SkyKoi-gw._tcp`.
+Only the Gateway advertises `_SKYKOI-gw._tcp`.
 
 ## Service types
 
-- `_SkyKoi-gw._tcp` — gateway transport beacon (used by macOS/iOS/Android nodes).
+- `_SKYKOI-gw._tcp` — gateway transport beacon (used by macOS/iOS/Android nodes).
 
 ## TXT keys (non‑secret hints)
 
@@ -97,7 +97,7 @@ The Gateway advertises small non‑secret hints to make UI flows convenient:
 - `canvasPort=<port>` (only when the canvas host is enabled; default `18793`)
 - `sshPort=<port>` (defaults to 22 when not overridden)
 - `transport=gateway`
-- `cliPath=<path>` (optional; absolute path to a runnable `SkyKoi` entrypoint)
+- `cliPath=<path>` (optional; absolute path to a runnable `SKYKOI` entrypoint)
 - `tailnetDns=<magicdns>` (optional hint when Tailnet is available)
 
 ## Debugging on macOS
@@ -107,13 +107,13 @@ Useful built‑in tools:
 - Browse instances:
 
   ```bash
-  dns-sd -B _SkyKoi-gw._tcp local.
+  dns-sd -B _SKYKOI-gw._tcp local.
   ```
 
 - Resolve one instance (replace `<instance>`):
 
   ```bash
-  dns-sd -L "<instance>" _SkyKoi-gw._tcp local.
+  dns-sd -L "<instance>" _SKYKOI-gw._tcp local.
   ```
 
 If browsing works but resolving fails, you’re usually hitting a LAN policy or
@@ -130,7 +130,7 @@ The Gateway writes a rolling log file (printed on startup as
 
 ## Debugging on iOS node
 
-The iOS node uses `NWBrowser` to discover `_SkyKoi-gw._tcp`.
+The iOS node uses `NWBrowser` to discover `_SKYKOI-gw._tcp`.
 
 To capture logs:
 
@@ -159,7 +159,7 @@ sequences (e.g. spaces become `\032`).
 ## Disabling / configuration
 
 - `SKYKOI_DISABLE_BONJOUR=1` disables advertising (legacy: `SKYKOI_DISABLE_BONJOUR`).
-- `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 (legacy: `SKYKOI_SSH_PORT`).
 - `SKYKOI_TAILNET_DNS` publishes a MagicDNS hint in TXT (legacy: `SKYKOI_TAILNET_DNS`).
 - `SKYKOI_CLI_PATH` overrides the advertised CLI path (legacy: `SKYKOI_CLI_PATH`).