skykoi 2026.3.11 → 2026.3.13

package/dist/{widearea-dns-vPa3VRwl.js → widearea-dns-Bxls47LT.js}

@@ -44,7 +44,7 @@ function extractSerial(zoneText) {
 	return Number.isFinite(parsed) ? parsed : null;
 }
 function extractContentHash(zoneText) {
-	return zoneText.match(/^\s*;\s*SkyKoi-content-hash:\s*(\S+)\s*$/m)?.[1] ?? null;
+	return zoneText.match(/^\s*;\s*SKYKOI-content-hash:\s*(\S+)\s*$/m)?.[1] ?? null;
 }
 function computeContentHash(body) {
 	let h = 2166136261;
@@ -57,7 +57,7 @@ function computeContentHash(body) {
 function renderZone(opts) {
 	const hostname = os.hostname().split(".")[0] ?? "skykoi";
 	const hostLabel = dnsLabel(opts.hostLabel ?? hostname, "skykoi");
-	const instanceLabel = dnsLabel(opts.instanceLabel ?? `${hostname}-gateway`, "SkyKoi-gw");
+	const instanceLabel = dnsLabel(opts.instanceLabel ?? `${hostname}-gateway`, "SKYKOI-gw");
 	const domain = normalizeWideAreaDomain(opts.domain) ?? "local.";
 	const txt = [
 		`displayName=${opts.displayName.trim() || hostname}`,
@@ -81,11 +81,11 @@ function renderZone(opts) {
 	records.push(`ns1 IN A ${opts.tailnetIPv4}`);
 	records.push(`${hostLabel} IN A ${opts.tailnetIPv4}`);
 	if (opts.tailnetIPv6) records.push(`${hostLabel} IN AAAA ${opts.tailnetIPv6}`);
-	records.push(`_SkyKoi-gw._tcp IN PTR ${instanceLabel}._SkyKoi-gw._tcp`);
-	records.push(`${instanceLabel}._SkyKoi-gw._tcp IN SRV 0 0 ${opts.gatewayPort} ${hostLabel}`);
-	records.push(`${instanceLabel}._SkyKoi-gw._tcp IN TXT ${txt.map(txtQuote).join(" ")}`);
+	records.push(`_SKYKOI-gw._tcp IN PTR ${instanceLabel}._SKYKOI-gw._tcp`);
+	records.push(`${instanceLabel}._SKYKOI-gw._tcp IN SRV 0 0 ${opts.gatewayPort} ${hostLabel}`);
+	records.push(`${instanceLabel}._SKYKOI-gw._tcp IN TXT ${txt.map(txtQuote).join(" ")}`);
 	const contentBody = `${records.join("\n")}\n`;
-	return `; SkyKoi-content-hash: ${computeContentHash(`${records.map((line) => line === soaLine ? `@ IN SOA ns1 hostmaster SERIAL 7200 3600 1209600 60` : line).join("\n")}\n`)}\n${contentBody}`;
+	return `; SKYKOI-content-hash: ${computeContentHash(`${records.map((line) => line === soaLine ? `@ IN SOA ns1 hostmaster SERIAL 7200 3600 1209600 60` : line).join("\n")}\n`)}\n${contentBody}`;
 }
 function renderWideAreaGatewayZoneText(opts) {
 	return renderZone(opts);

package/dist/{widearea-dns-bdiHwdn3.js → widearea-dns-Cr9yVcsB.js}

@@ -1,4 +1,4 @@
-import { s as ensureDir, t as CONFIG_DIR } from "./utils-Dq030IDo.js";
+import { s as ensureDir, t as CONFIG_DIR } from "./utils-CV3CeN0V.js";
 import os from "node:os";
 import path from "node:path";
 import fs from "node:fs";
@@ -44,7 +44,7 @@ function extractSerial(zoneText) {
 	return Number.isFinite(parsed) ? parsed : null;
 }
 function extractContentHash(zoneText) {
-	return zoneText.match(/^\s*;\s*SkyKoi-content-hash:\s*(\S+)\s*$/m)?.[1] ?? null;
+	return zoneText.match(/^\s*;\s*SKYKOI-content-hash:\s*(\S+)\s*$/m)?.[1] ?? null;
 }
 function computeContentHash(body) {
 	let h = 2166136261;
@@ -57,7 +57,7 @@ function computeContentHash(body) {
 function renderZone(opts) {
 	const hostname = os.hostname().split(".")[0] ?? "skykoi";
 	const hostLabel = dnsLabel(opts.hostLabel ?? hostname, "skykoi");
-	const instanceLabel = dnsLabel(opts.instanceLabel ?? `${hostname}-gateway`, "SkyKoi-gw");
+	const instanceLabel = dnsLabel(opts.instanceLabel ?? `${hostname}-gateway`, "SKYKOI-gw");
 	const domain = normalizeWideAreaDomain(opts.domain) ?? "local.";
 	const txt = [
 		`displayName=${opts.displayName.trim() || hostname}`,
@@ -81,11 +81,11 @@ function renderZone(opts) {
 	records.push(`ns1 IN A ${opts.tailnetIPv4}`);
 	records.push(`${hostLabel} IN A ${opts.tailnetIPv4}`);
 	if (opts.tailnetIPv6) records.push(`${hostLabel} IN AAAA ${opts.tailnetIPv6}`);
-	records.push(`_SkyKoi-gw._tcp IN PTR ${instanceLabel}._SkyKoi-gw._tcp`);
-	records.push(`${instanceLabel}._SkyKoi-gw._tcp IN SRV 0 0 ${opts.gatewayPort} ${hostLabel}`);
-	records.push(`${instanceLabel}._SkyKoi-gw._tcp IN TXT ${txt.map(txtQuote).join(" ")}`);
+	records.push(`_SKYKOI-gw._tcp IN PTR ${instanceLabel}._SKYKOI-gw._tcp`);
+	records.push(`${instanceLabel}._SKYKOI-gw._tcp IN SRV 0 0 ${opts.gatewayPort} ${hostLabel}`);
+	records.push(`${instanceLabel}._SKYKOI-gw._tcp IN TXT ${txt.map(txtQuote).join(" ")}`);
 	const contentBody = `${records.join("\n")}\n`;
-	return `; SkyKoi-content-hash: ${computeContentHash(`${records.map((line) => line === soaLine ? `@ IN SOA ns1 hostmaster SERIAL 7200 3600 1209600 60` : line).join("\n")}\n`)}\n${contentBody}`;
+	return `; SKYKOI-content-hash: ${computeContentHash(`${records.map((line) => line === soaLine ? `@ IN SOA ns1 hostmaster SERIAL 7200 3600 1209600 60` : line).join("\n")}\n`)}\n${contentBody}`;
 }
 function renderWideAreaGatewayZoneText(opts) {
 	return renderZone(opts);

package/dist/{ws-log-CqjxtHs1.js → ws-log-DxXqar2k.js}

@@ -1,5 +1,5 @@
 import { v as parseAgentSessionKey } from "./session-key-DrNCyvP1.js";
-import { O as isVerbose, o as shouldLogSubsystemToConsole, t as createSubsystemLogger } from "./subsystem-Bn-Knx2Q.js";
+import { O as isVerbose, o as shouldLogSubsystemToConsole, t as createSubsystemLogger } from "./subsystem-B6KC_eUM.js";
 import { n as redactSensitiveText, t as getDefaultRedactPatterns } from "./redact-DJCFY628.js";
 import chalk from "chalk";
 

package/dist/{wsl-Dgpt12tO.js → wsl-D52TsyFE.js}

@@ -1,4 +1,4 @@
-import { t as registerBrowserRoutes } from "./routes-Kek_zngV.js";
+import { t as registerBrowserRoutes } from "./routes-C8t8rAsZ.js";
 import { execFile } from "node:child_process";
 import os from "node:os";
 import { promisify } from "node:util";

package/docs/.i18n/README.md

@@ -1,4 +1,4 @@
-# SkyKoi docs i18n assets
+# SKYKOI docs i18n assets
 
 This folder stores **generated** and **config** files for documentation translations.
 

package/docs/.i18n/glossary.zh-CN.json

@@ -1,7 +1,7 @@
 [
   {
-    "source": "SkyKoi",
-    "target": "SkyKoi"
+    "source": "SKYKOI",
+    "target": "SKYKOI"
   },
   {
     "source": "Gateway",

package/docs/automation/auth-monitoring.md

@@ -8,13 +8,13 @@ title: "Auth Monitoring"
 
 # Auth monitoring
 
-SkyKoi exposes OAuth expiry health via `SkyKoi models status`. Use that for
+SKYKOI exposes OAuth expiry health via `SKYKOI models status`. Use that for
 automation and alerting; scripts are optional extras for phone workflows.
 
 ## Preferred: CLI check (portable)
 
 ```bash
-SkyKoi models status --check
+SKYKOI models status --check
 ```
 
 Exit codes:
@@ -30,15 +30,15 @@ This works in cron/systemd and requires no extra scripts.
 These live under `scripts/` and are **optional**. They assume SSH access to the
 gateway host and are tuned for systemd + Termux.
 
-- `scripts/claude-auth-status.sh` now uses `SkyKoi models status --json` as the
+- `scripts/claude-auth-status.sh` now uses `SKYKOI models status --json` as the
   source of truth (falling back to direct file reads if the CLI is unavailable),
-  so keep `SkyKoi` on `PATH` for timers.
+  so keep `SKYKOI` on `PATH` for timers.
 - `scripts/auth-monitor.sh`: cron/systemd timer target; sends alerts (ntfy or phone).
-- `scripts/systemd/SkyKoi-auth-monitor.{service,timer}`: systemd user timer.
-- `scripts/claude-auth-status.sh`: Claude Code + SkyKoi auth checker (full/json/simple).
+- `scripts/systemd/SKYKOI-auth-monitor.{service,timer}`: systemd user timer.
+- `scripts/claude-auth-status.sh`: Claude Code + SKYKOI auth checker (full/json/simple).
 - `scripts/mobile-reauth.sh`: guided re‑auth flow over SSH.
 - `scripts/termux-quick-auth.sh`: one‑tap widget status + open auth URL.
 - `scripts/termux-auth-widget.sh`: full guided widget flow.
-- `scripts/termux-sync-widget.sh`: sync Claude Code creds → SkyKoi.
+- `scripts/termux-sync-widget.sh`: sync Claude Code creds → SKYKOI.
 
 If you don’t need phone automation or systemd timers, skip these scripts.

package/docs/automation/cron-jobs.md

@@ -22,7 +22,7 @@ Troubleshooting: [/automation/troubleshooting](/automation/troubleshooting)
 ## TL;DR
 
 - Cron runs **inside the Gateway** (not inside the model).
-- Jobs persist under `~/.skykoi/cron/` so restarts don’t lose schedules.
+- Jobs persist under `~/.SKYKOI/cron/` so restarts don’t lose schedules.
 - Two execution styles:
   - **Main session**: enqueue a system event, then run on the next heartbeat.
   - **Isolated**: run a dedicated agent turn in `cron:<jobId>`, with delivery (announce by default or none).
@@ -33,7 +33,7 @@ Troubleshooting: [/automation/troubleshooting](/automation/troubleshooting)
 Create a one-shot reminder, verify it exists, and run it immediately:
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Reminder" \
   --at "2026-02-01T16:00:00Z" \
   --session main \
@@ -41,15 +41,15 @@ SkyKoi cron add \
   --wake now \
   --delete-after-run
 
-SkyKoi cron list
-SkyKoi cron run <job-id>
-SkyKoi cron runs --id <job-id>
+SKYKOI cron list
+SKYKOI cron run <job-id>
+SKYKOI cron runs --id <job-id>
 ```
 
 Schedule a recurring isolated job with delivery:
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Morning brief" \
   --cron "0 7 * * *" \
   --tz "America/Los_Angeles" \
@@ -66,9 +66,9 @@ For the canonical JSON shapes and examples, see [JSON schema for tool calls](/au
 
 ## Where cron jobs are stored
 
-Cron jobs are persisted on the Gateway host at `~/.skykoi/cron/jobs.json` by default.
+Cron jobs are persisted on the Gateway host at `~/.SKYKOI/cron/jobs.json` by default.
 The Gateway loads the file into memory and writes it back on changes, so manual edits
-are only safe when the Gateway is stopped. Prefer `SkyKoi cron add/edit` or the cron
+are only safe when the Gateway is stopped. Prefer `SKYKOI cron add/edit` or the cron
 tool call API for changes.
 
 ## Beginner-friendly overview
@@ -173,7 +173,7 @@ Delivery config (isolated jobs only):
 Announce delivery suppresses messaging tool sends for the run; use `delivery.channel`/`delivery.to`
 to target the chat instead. When `delivery.mode = "none"`, no summary is posted to the main session.
 
-If `delivery` is omitted for isolated jobs, SkyKoi defaults to `announce`.
+If `delivery` is omitted for isolated jobs, SKYKOI defaults to `announce`.
 
 #### Announce delivery flow
 
@@ -321,8 +321,8 @@ Notes:
 
 ## Storage & history
 
-- Job store: `~/.skykoi/cron/jobs.json` (Gateway-managed JSON).
-- Run history: `~/.skykoi/cron/runs/<jobId>.jsonl` (JSONL, auto-pruned).
+- Job store: `~/.SKYKOI/cron/jobs.json` (Gateway-managed JSON).
+- Run history: `~/.SKYKOI/cron/runs/<jobId>.jsonl` (JSONL, auto-pruned).
 - Override store path: `cron.store` in config.
 
 ## Configuration
@@ -331,7 +331,7 @@ Notes:
 {
   cron: {
     enabled: true, // default true
-    store: "~/.skykoi/cron/jobs.json",
+    store: "~/.SKYKOI/cron/jobs.json",
     maxConcurrentRuns: 1, // default 1
   },
 }
@@ -347,7 +347,7 @@ Disable cron entirely:
 One-shot reminder (UTC ISO, auto-delete after success):
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Send reminder" \
   --at "2026-01-12T18:00:00Z" \
   --session main \
@@ -359,7 +359,7 @@ SkyKoi cron add \
 One-shot reminder (main session, wake immediately):
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Calendar check" \
   --at "20m" \
   --session main \
@@ -370,7 +370,7 @@ SkyKoi cron add \
 Recurring isolated job (announce to WhatsApp):
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Morning status" \
   --cron "0 7 * * *" \
   --tz "America/Los_Angeles" \
@@ -384,7 +384,7 @@ SkyKoi cron add \
 Recurring isolated job (deliver to a Telegram topic):
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Nightly summary (topic)" \
   --cron "0 22 * * *" \
   --tz "America/Los_Angeles" \
@@ -398,7 +398,7 @@ SkyKoi cron add \
 Isolated job with model and thinking override:
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Deep analysis" \
   --cron "0 6 * * 1" \
   --tz "America/Los_Angeles" \
@@ -415,24 +415,24 @@ Agent selection (multi-agent setups):
 
 ```bash
 # Pin a job to agent "ops" (falls back to default if that agent is missing)
-SkyKoi cron add --name "Ops sweep" --cron "0 6 * * *" --session isolated --message "Check ops queue" --agent ops
+SKYKOI cron add --name "Ops sweep" --cron "0 6 * * *" --session isolated --message "Check ops queue" --agent ops
 
 # Switch or clear the agent on an existing job
-SkyKoi cron edit <jobId> --agent ops
-SkyKoi cron edit <jobId> --clear-agent
+SKYKOI cron edit <jobId> --agent ops
+SKYKOI cron edit <jobId> --clear-agent
 ```
 
 Manual run (force is the default, use `--due` to only run when due):
 
 ```bash
-SkyKoi cron run <jobId>
-SkyKoi cron run <jobId> --due
+SKYKOI cron run <jobId>
+SKYKOI cron run <jobId> --due
 ```
 
 Edit an existing job (patch fields):
 
 ```bash
-SkyKoi cron edit <jobId> \
+SKYKOI cron edit <jobId> \
   --message "Updated prompt" \
   --model "opus" \
   --thinking low
@@ -441,20 +441,20 @@ SkyKoi cron edit <jobId> \
 Run history:
 
 ```bash
-SkyKoi cron runs --id <jobId> --limit 50
+SKYKOI cron runs --id <jobId> --limit 50
 ```
 
 Immediate system event without creating a job:
 
 ```bash
-SkyKoi system event --mode now --text "Next heartbeat: check battery."
+SKYKOI system event --mode now --text "Next heartbeat: check battery."
 ```
 
 ## Gateway API surface
 
 - `cron.list`, `cron.status`, `cron.add`, `cron.update`, `cron.remove`
 - `cron.run` (force or due), `cron.runs`
-  For immediate system events without a job, use [`SkyKoi system event`](/cli/system).
+  For immediate system events without a job, use [`SKYKOI system event`](/cli/system).
 
 ## Troubleshooting
 

package/docs/automation/cron-vs-heartbeat.md

@@ -98,7 +98,7 @@ Cron jobs run at **exact times** and can run in isolated sessions without affect
 ### Cron example: Daily morning briefing
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Morning briefing" \
   --cron "0 7 * * *" \
   --tz "America/New_York" \
@@ -115,7 +115,7 @@ This runs at exactly 7:00 AM New York time, uses Opus for quality, and announces
 ### Cron example: One-shot reminder
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Meeting reminder" \
   --at "20m" \
   --session main \
@@ -174,13 +174,13 @@ The most efficient setup uses **both**:
 
 ```bash
 # Daily morning briefing at 7am
-SkyKoi cron add --name "Morning brief" --cron "0 7 * * *" --session isolated --message "..." --announce
+SKYKOI cron add --name "Morning brief" --cron "0 7 * * *" --session isolated --message "..." --announce
 
 # Weekly project review on Mondays at 9am
-SkyKoi cron add --name "Weekly review" --cron "0 9 * * 1" --session isolated --message "..." --model opus
+SKYKOI cron add --name "Weekly review" --cron "0 9 * * 1" --session isolated --message "..." --model opus
 
 # One-shot reminder
-SkyKoi cron add --name "Call back" --at "2h" --session main --system-event "Call back the client" --wake now
+SKYKOI cron add --name "Call back" --at "2h" --session main --system-event "Call back the client" --wake now
 ```
 
 ## Lobster: Deterministic workflows with approvals
@@ -232,7 +232,7 @@ Use `--session main` with `--system-event` when you want:
 - No separate isolated run
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Check project" \
   --every "4h" \
   --session main \
@@ -250,7 +250,7 @@ Use `--session isolated` when you want:
 - History that doesn't clutter main session
 
 ```bash
-SkyKoi cron add \
+SKYKOI cron add \
   --name "Deep analysis" \
   --cron "0 6 * * 0" \
   --session isolated \

package/docs/automation/gmail-pubsub.md

@@ -1,20 +1,20 @@
 ---
-summary: "Gmail Pub/Sub push wired into SkyKoi webhooks via gogcli"
+summary: "Gmail Pub/Sub push wired into SKYKOI webhooks via gogcli"
 read_when:
-  - Wiring Gmail inbox triggers to SkyKoi
+  - Wiring Gmail inbox triggers to SKYKOI
   - Setting up Pub/Sub push for agent wake
 title: "Gmail PubSub"
 ---
 
-# Gmail Pub/Sub -> SkyKoi
+# Gmail Pub/Sub -> SKYKOI
 
-Goal: Gmail watch -> Pub/Sub push -> `gog gmail watch serve` -> SkyKoi webhook.
+Goal: Gmail watch -> Pub/Sub push -> `gog gmail watch serve` -> SKYKOI webhook.
 
 ## Prereqs
 
 - `gcloud` installed and logged in ([install guide](https://docs.cloud.google.com/sdk/docs/install-sdk)).
 - `gog` (gogcli) installed and authorized for the Gmail account ([gogcli.sh](https://gogcli.sh/)).
-- SkyKoi hooks enabled (see [Webhooks](/automation/webhook)).
+- SKYKOI hooks enabled (see [Webhooks](/automation/webhook)).
 - `tailscale` logged in ([tailscale.com](https://tailscale.com/)). Supported setup uses Tailscale Funnel for the public HTTPS endpoint.
   Other tunnel services can work, but are DIY/unsupported and require manual wiring.
   Right now, Tailscale is what we support.
@@ -25,7 +25,7 @@ Example hook config (enable Gmail preset mapping):
 {
   hooks: {
     enabled: true,
-    token: "SkyKoi_HOOK_TOKEN",
+    token: "SKYKOI_HOOK_TOKEN",
     path: "/hooks",
     presets: ["gmail"],
   },
@@ -39,7 +39,7 @@ that sets `deliver` + optional `channel`/`to`:
 {
   hooks: {
     enabled: true,
-    token: "SkyKoi_HOOK_TOKEN",
+    token: "SKYKOI_HOOK_TOKEN",
     presets: ["gmail"],
     mappings: [
       {
@@ -92,20 +92,20 @@ under `hooks.transformsDir` (see [Webhooks](/automation/webhook)).
 
 ## Wizard (recommended)
 
-Use the SkyKoi helper to wire everything together (installs deps on macOS via brew):
+Use the SKYKOI helper to wire everything together (installs deps on macOS via brew):
 
 ```bash
-SkyKoi webhooks gmail setup \
-  --account SkyKoi@gmail.com
+SKYKOI webhooks gmail setup \
+  --account SKYKOI@gmail.com
 ```
 
 Defaults:
 
 - Uses Tailscale Funnel for the public push endpoint.
-- Writes `hooks.gmail` config for `skykoi webhooks gmail run`.
+- Writes `hooks.gmail` config for `SKYKOI webhooks gmail run`.
 - Enables the Gmail hook preset (`hooks.presets: ["gmail"]`).
 
-Path note: when `tailscale.mode` is enabled, SkyKoi automatically sets
+Path note: when `tailscale.mode` is enabled, SKYKOI automatically sets
 `hooks.gmail.serve.path` to `/` and keeps the public path at
 `hooks.gmail.tailscale.path` (default `/gmail-pubsub`) because Tailscale
 strips the set-path prefix before proxying.
@@ -122,14 +122,14 @@ Gateway auto-start (recommended):
 
 - When `hooks.enabled=true` and `hooks.gmail.account` is set, the Gateway starts
   `gog gmail watch serve` on boot and auto-renews the watch.
-- Set `SkyKoi_SKIP_GMAIL_WATCHER=1` to opt out (useful if you run the daemon yourself).
+- Set `SKYKOI_SKIP_GMAIL_WATCHER=1` to opt out (useful if you run the daemon yourself).
 - Do not run the manual daemon at the same time, or you will hit
   `listen tcp 127.0.0.1:8788: bind: address already in use`.
 
 Manual daemon (starts `gog gmail watch serve` + auto-renew):
 
 ```bash
-SkyKoi webhooks gmail run
+SKYKOI webhooks gmail run
 ```
 
 ## One-time setup
@@ -167,7 +167,7 @@ gcloud pubsub topics add-iam-policy-binding gog-gmail-watch \
 
 ```bash
 gog gmail watch start \
-  --account SkyKoi@gmail.com \
+  --account SKYKOI@gmail.com \
   --label INBOX \
   --topic projects/<project-id>/topics/gog-gmail-watch
 ```
@@ -180,13 +180,13 @@ Local example (shared token auth):
 
 ```bash
 gog gmail watch serve \
-  --account SkyKoi@gmail.com \
+  --account SKYKOI@gmail.com \
   --bind 127.0.0.1 \
   --port 8788 \
   --path /gmail-pubsub \
   --token <shared> \
   --hook-url http://127.0.0.1:18789/hooks/gmail \
-  --hook-token SkyKoi_HOOK_TOKEN \
+  --hook-token SKYKOI_HOOK_TOKEN \
   --include-body \
   --max-bytes 20000
 ```
@@ -194,10 +194,10 @@ gog gmail watch serve \
 Notes:
 
 - `--token` protects the push endpoint (`x-gog-token` or `?token=`).
-- `--hook-url` points to SkyKoi `/hooks/gmail` (mapped; isolated run + summary to main).
-- `--include-body` and `--max-bytes` control the body snippet sent to SkyKoi.
+- `--hook-url` points to SKYKOI `/hooks/gmail` (mapped; isolated run + summary to main).
+- `--include-body` and `--max-bytes` control the body snippet sent to SKYKOI.
 
-Recommended: `skykoi webhooks gmail run` wraps the same flow and auto-renews the watch.
+Recommended: `SKYKOI webhooks gmail run` wraps the same flow and auto-renews the watch.
 
 ## Expose the handler (advanced, unsupported)
 
@@ -228,8 +228,8 @@ Send a message to the watched inbox:
 
 ```bash
 gog gmail send \
-  --account SkyKoi@gmail.com \
-  --to SkyKoi@gmail.com \
+  --account SKYKOI@gmail.com \
+  --to SKYKOI@gmail.com \
   --subject "watch test" \
   --body "ping"
 ```
@@ -237,8 +237,8 @@ gog gmail send \
 Check watch state and history:
 
 ```bash
-gog gmail watch status --account SkyKoi@gmail.com
-gog gmail history --account SkyKoi@gmail.com --since <historyId>
+gog gmail watch status --account SKYKOI@gmail.com
+gog gmail history --account SKYKOI@gmail.com --since <historyId>
 ```
 
 ## Troubleshooting
@@ -250,7 +250,7 @@ gog gmail history --account SkyKoi@gmail.com --since <historyId>
 ## Cleanup
 
 ```bash
-gog gmail watch stop --account SkyKoi@gmail.com
+gog gmail watch stop --account SKYKOI@gmail.com
 gcloud pubsub subscriptions delete gog-gmail-watch-push
 gcloud pubsub topics delete gog-gmail-watch
 ```