@symerian/symi 3.0.20 → 3.0.22

package/docs/install/render.mdx

@@ -1,158 +0,0 @@
----
-title: Deploy on Render
----
-
-Deploy Symi on Render using Infrastructure as Code. The included `render.yaml` Blueprint defines your entire stack declaratively, service, disk, environment variables, so you can deploy with a single click and version your infrastructure alongside your code.
-
-## Prerequisites
-
-- A [Render account](https://render.com) (free tier available)
-- An API key from your preferred [model provider](/providers)
-
-## Deploy with a Render Blueprint
-
-[Deploy to Render](https://render.com/deploy?repo=https://github.com/symi/symi)
-
-Clicking this link will:
-
-1. Create a new Render service from the `render.yaml` Blueprint at the root of this repo.
-2. Prompt you to set `SETUP_PASSWORD`
-3. Build the Docker image and deploy
-
-Once deployed, your service URL follows the pattern `https://<service-name>.onrender.com`.
-
-## Understanding the Blueprint
-
-Render Blueprints are YAML files that define your infrastructure. The `render.yaml` in this
-repository configures everything needed to run Symi:
-
-```yaml
-services:
-  - type: web
-    name: symi
-    runtime: docker
-    plan: starter
-    healthCheckPath: /health
-    envVars:
-      - key: PORT
-        value: "8080"
-      - key: SETUP_PASSWORD
-        sync: false # prompts during deploy
-      - key: SYMI_STATE_DIR
-        value: /data/.symi
-      - key: SYMI_WORKSPACE_DIR
-        value: /data/workspace
-      - key: SYMI_GATEWAY_TOKEN
-        generateValue: true # auto-generates a secure token
-    disk:
-      name: symi-data
-      mountPath: /data
-      sizeGB: 1
-```
-
-Key Blueprint features used:
-
-| Feature               | Purpose                                                    |
-| --------------------- | ---------------------------------------------------------- |
-| `runtime: docker`     | Builds from the repo's Dockerfile                          |
-| `healthCheckPath`     | Render monitors `/health` and restarts unhealthy instances |
-| `sync: false`         | Prompts for value during deploy (secrets)                  |
-| `generateValue: true` | Auto-generates a cryptographically secure value            |
-| `disk`                | Persistent storage that survives redeploys                 |
-
-## Choosing a plan
-
-| Plan      | Spin-down         | Disk          | Best for                      |
-| --------- | ----------------- | ------------- | ----------------------------- |
-| Free      | After 15 min idle | Not available | Testing, demos                |
-| Starter   | Never             | 1GB+          | Personal use, small teams     |
-| Standard+ | Never             | 1GB+          | Production, multiple channels |
-
-The Blueprint defaults to `starter`. To use free tier, change `plan: free` in your fork's
-`render.yaml` (but note: no persistent disk means config resets on each deploy).
-
-## After deployment
-
-### Complete the setup wizard
-
-1. Navigate to `https://<your-service>.onrender.com/setup`
-2. Enter your `SETUP_PASSWORD`
-3. Select a model provider and paste your API key
-4. Click **Run setup**
-
-### Access the Control UI
-
-The web dashboard is available at `https://<your-service>.onrender.com/symi`.
-
-## Render Dashboard features
-
-### Logs
-
-View real-time logs in **Dashboard → your service → Logs**. Filter by:
-
-- Build logs (Docker image creation)
-- Deploy logs (service startup)
-- Runtime logs (application output)
-
-### Shell access
-
-For debugging, open a shell session via **Dashboard → your service → Shell**. The persistent disk is mounted at `/data`.
-
-### Environment variables
-
-Modify variables in **Dashboard → your service → Environment**. Changes trigger an automatic redeploy.
-
-### Auto-deploy
-
-If you use the original Symi repository, Render will not auto-deploy your Symi. To update it, run a manual Blueprint sync from the dashboard.
-
-## Custom domain
-
-1. Go to **Dashboard → your service → Settings → Custom Domains**
-2. Add your domain
-3. Configure DNS as instructed (CNAME to `*.onrender.com`)
-4. Render provisions a TLS certificate automatically
-
-## Scaling
-
-Render supports horizontal and vertical scaling:
-
-- **Vertical**: Change the plan to get more CPU/RAM
-- **Horizontal**: Increase instance count (Standard plan and above)
-
-For Symi, vertical scaling is usually sufficient. Horizontal scaling requires sticky sessions or external state management.
-
-## Backups and migration
-
-Export your configuration and workspace at any time:
-
-```
-https://<your-service>.onrender.com/setup/export
-```
-
-This downloads a portable backup you can restore on any Symi host.
-
-## Troubleshooting
-
-### Service won't start
-
-Check the deploy logs in the Render Dashboard. Common issues:
-
-- Missing `SETUP_PASSWORD` — the Blueprint prompts for this, but verify it's set
-- Port mismatch — ensure `PORT=8080` matches the Dockerfile's exposed port
-
-### Slow cold starts (free tier)
-
-Free tier services spin down after 15 minutes of inactivity. The first request after spin-down takes a few seconds while the container starts. Upgrade to Starter plan for always-on.
-
-### Data loss after redeploy
-
-This happens on free tier (no persistent disk). Upgrade to a paid plan, or
-regularly export your config via `/setup/export`.
-
-### Health check failures
-
-Render expects a 200 response from `/health` within 30 seconds. If builds succeed but deploys fail, the service may be taking too long to start. Check:
-
-- Build logs for errors
-- Whether the container runs locally with `docker build && docker run`

package/docs/install/uninstall.md

@@ -1,128 +0,0 @@
----
-summary: "Uninstall Symi completely (CLI, service, state, workspace)"
-read_when:
-  - You want to remove Symi from a machine
-  - The gateway service is still running after uninstall
-title: "Uninstall"
----
-
-# Uninstall
-
-Two paths:
-
-- **Easy path** if `symi` is still installed.
-- **Manual service removal** if the CLI is gone but the service is still running.
-
-## Easy path (CLI still installed)
-
-Recommended: use the built-in uninstaller:
-
-```bash
-symi uninstall
-```
-
-Non-interactive (automation / npx):
-
-```bash
-symi uninstall --all --yes --non-interactive
-npx -y symi uninstall --all --yes --non-interactive
-```
-
-Manual steps (same result):
-
-1. Stop the gateway service:
-
-```bash
-symi gateway stop
-```
-
-2. Uninstall the gateway service (launchd/systemd/schtasks):
-
-```bash
-symi gateway uninstall
-```
-
-3. Delete state + config:
-
-```bash
-rm -rf "${SYMI_STATE_DIR:-$HOME/.symi}"
-```
-
-If you set `SYMI_CONFIG_PATH` to a custom location outside the state dir, delete that file too.
-
-4. Delete your workspace (optional, removes agent files):
-
-```bash
-rm -rf ~/.symi/workspace
-```
-
-5. Remove the CLI install (pick the one you used):
-
-```bash
-npm rm -g symi
-pnpm remove -g symi
-bun remove -g symi
-```
-
-6. If you installed the macOS app:
-
-```bash
-rm -rf /Applications/Symi.app
-```
-
-Notes:
-
-- If you used profiles (`--profile` / `SYMI_PROFILE`), repeat step 3 for each state dir (defaults are `~/.symi-<profile>`).
-- In remote mode, the state dir lives on the **gateway host**, so run steps 1-4 there too.
-
-## Manual service removal (CLI not installed)
-
-Use this if the gateway service keeps running but `symi` is missing.
-
-### macOS (launchd)
-
-Default label is `bot.molt.gateway` (or `bot.molt.<profile>`; legacy `com.symi.*` may still exist):
-
-```bash
-launchctl bootout gui/$UID/bot.molt.gateway
-rm -f ~/Library/LaunchAgents/bot.molt.gateway.plist
-```
-
-If you used a profile, replace the label and plist name with `bot.molt.<profile>`. Remove any legacy `com.symi.*` plists if present.
-
-### Linux (systemd user unit)
-
-Default unit name is `symi-gateway.service` (or `symi-gateway-<profile>.service`):
-
-```bash
-systemctl --user disable --now symi-gateway.service
-rm -f ~/.config/systemd/user/symi-gateway.service
-systemctl --user daemon-reload
-```
-
-### Windows (Scheduled Task)
-
-Default task name is `Symi Gateway` (or `Symi Gateway (<profile>)`).
-The task script lives under your state dir.
-
-```powershell
-schtasks /Delete /F /TN "Symi Gateway"
-Remove-Item -Force "$env:USERPROFILE\.symi\gateway.cmd"
-```
-
-If you used a profile, delete the matching task name and `~\.symi-<profile>\gateway.cmd`.
-
-## Normal install vs source checkout
-
-### Normal install (install.sh / npm / pnpm / bun)
-
-If you used `https://jaysteelmind.github.io/getsymi/install.sh` or `install.ps1`, the CLI was installed with `npm install -g @symerian/symi@latest`.
-Remove it with `npm rm -g symi` (or `pnpm remove -g` / `bun remove -g` if you installed that way).
-
-### Source checkout (git clone)
-
-If you run from a repo checkout (`git clone` + `symi ...` / `bun run symi ...`):
-
-1. Uninstall the gateway service **before** deleting the repo (use the easy path above or manual service removal).
-2. Delete the repo directory.
-3. Remove state + workspace as shown above.

package/docs/install/updating.md

@@ -1,231 +0,0 @@
----
-summary: "Updating Symi safely (global install or source), plus rollback strategy"
-read_when:
-  - Updating Symi
-  - Something breaks after an update
-title: "Updating"
----
-
-# Updating
-
-Symi is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart (or use `symi update`, which restarts) → verify.
-
-## Recommended: re-run the website installer (upgrade in place)
-
-The **preferred** update path is to re-run the installer from the website. It
-detects existing installs, upgrades in place, and runs `symi doctor` when
-needed.
-
-```bash
-curl -fsSL https://jaysteelmind.github.io/getsymi/install.sh | bash
-```
-
-Notes:
-
-- Add `--no-onboard` if you don’t want the onboarding wizard to run again.
-- For **source installs**, use:
-
-  ```bash
-  curl -fsSL https://jaysteelmind.github.io/getsymi/install.sh | bash -s -- --install-method git --no-onboard
-  ```
-
-  The installer will `git pull --rebase` **only** if the repo is clean.
-
-- For **global installs**, the script uses `npm install -g @symerian/symi@latest` under the hood.
-- Legacy note: `symi` remains available as a compatibility shim.
-
-## Before you update
-
-- Know how you installed: **global** (npm/pnpm) vs **from source** (git clone).
-- Know how your Gateway is running: **foreground terminal** vs **supervised service** (launchd/systemd).
-- Snapshot your tailoring:
-  - Config: `~/.symi/symi.json`
-  - Credentials: `~/.symi/credentials/`
-  - Workspace: `~/.symi/workspace`
-
-## Update (global install)
-
-Global install (pick one):
-
-```bash
-npm i -g @symerian/symi@latest
-```
-
-```bash
-pnpm add -g symi@latest
-```
-
-We do **not** recommend Bun for the Gateway runtime (WhatsApp/Telegram bugs).
-
-To switch update channels (git + npm installs):
-
-```bash
-symi update --channel beta
-symi update --channel dev
-symi update --channel stable
-```
-
-Use `--tag <dist-tag|version>` for a one-off install tag/version.
-
-See [Development channels](/install/development-channels) for channel semantics and release notes.
-
-Note: on npm installs, the gateway logs an update hint on startup (checks the current channel tag). Disable via `update.checkOnStart: false`.
-
-Then:
-
-```bash
-symi doctor
-symi gateway restart
-symi health
-```
-
-Notes:
-
-- If your Gateway runs as a service, `symi gateway restart` is preferred over killing PIDs.
-- If you’re pinned to a specific version, see “Rollback / pinning” below.
-
-## Update (`symi update`)
-
-For **source installs** (git checkout), prefer:
-
-```bash
-symi update
-```
-
-It runs a safe-ish update flow:
-
-- Requires a clean worktree.
-- Switches to the selected channel (tag or branch).
-- Fetches + rebases against the configured upstream (dev channel).
-- Installs deps, builds, builds the Control UI, and runs `symi doctor`.
-- Restarts the gateway by default (use `--no-restart` to skip).
-
-If you installed via **npm/pnpm** (no git metadata), `symi update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead.
-
-## Update (Control UI / RPC)
-
-The Control UI has **Update & Restart** (RPC: `update.run`). It:
-
-1. Runs the same source-update flow as `symi update` (git checkout only).
-2. Writes a restart sentinel with a structured report (stdout/stderr tail).
-3. Restarts the gateway and pings the last active session with the report.
-
-If the rebase fails, the gateway aborts and restarts without applying the update.
-
-## Update (from source)
-
-From the repo checkout:
-
-Preferred:
-
-```bash
-symi update
-```
-
-Manual (equivalent-ish):
-
-```bash
-git pull
-pnpm install
-pnpm build
-pnpm ui:build # auto-installs UI deps on first run
-symi doctor
-symi health
-```
-
-Notes:
-
-- `pnpm build` matters when you run the packaged `symi` binary ([`symi.mjs`](https://github.com/symi/symi/blob/main/symi.mjs)) or use Node to run `dist/`.
-- If you run from a repo checkout without a global install, use `pnpm symi ...` for CLI commands.
-- If you run directly from TypeScript (`pnpm symi ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor.
-- Switching between global and git installs is easy: install the other flavor, then run `symi doctor` so the gateway service entrypoint is rewritten to the current install.
-
-## Always Run: `symi doctor`
-
-Doctor is the “safe update” command. It’s intentionally boring: repair + migrate + warn.
-
-Note: if you’re on a **source install** (git checkout), `symi doctor` will offer to run `symi update` first.
-
-Typical things it does:
-
-- Migrate deprecated config keys / legacy config file locations.
-- Audit DM policies and warn on risky “open” settings.
-- Check Gateway health and can offer to restart.
-- Detect and migrate older gateway services (launchd/systemd; legacy schtasks) to current Symi services.
-- On Linux, ensure systemd user lingering (so the Gateway survives logout).
-
-Details: [Doctor](/gateway/doctor)
-
-## Start / stop / restart the Gateway
-
-CLI (works regardless of OS):
-
-```bash
-symi gateway status
-symi gateway stop
-symi gateway restart
-symi gateway --port 18789
-symi logs --follow
-```
-
-If you’re supervised:
-
-- macOS launchd (app-bundled LaunchAgent): `launchctl kickstart -k gui/$UID/bot.molt.gateway` (use `bot.molt.<profile>`; legacy `com.symi.*` still works)
-- Linux systemd user service: `systemctl --user restart symi-gateway[-<profile>].service`
-- Windows (WSL2): `systemctl --user restart symi-gateway[-<profile>].service`
-  - `launchctl`/`systemctl` only work if the service is installed; otherwise run `symi gateway install`.
-
-Runbook + exact service labels: [Gateway runbook](/gateway)
-
-## Rollback / pinning (when something breaks)
-
-### Pin (global install)
-
-Install a known-good version (replace `<version>` with the last working one):
-
-```bash
-npm i -g @symerian/symi@<version>
-```
-
-```bash
-pnpm add -g symi@<version>
-```
-
-Tip: to see the current published version, run `npm view symi version`.
-
-Then restart + re-run doctor:
-
-```bash
-symi doctor
-symi gateway restart
-```
-
-### Pin (source) by date
-
-Pick a commit from a date (example: “state of main as of 2026-01-01”):
-
-```bash
-git fetch origin
-git checkout "$(git rev-list -n 1 --before=\"2026-01-01\" origin/main)"
-```
-
-Then reinstall deps + restart:
-
-```bash
-pnpm install
-pnpm build
-symi gateway restart
-```
-
-If you want to go back to latest later:
-
-```bash
-git checkout main
-git pull
-```
-
-## If you’re stuck
-
-- Run `symi doctor` again and read the output carefully (it often tells you the fix).
-- Check: [Troubleshooting](/gateway/troubleshooting)
-- Check: [FAQ](https://docs.symi.ai/help/faq)

package/docs/ja-JP/AGENTS.md

@@ -1,37 +0,0 @@
-# AGENTS.md - ja-JP docs translation workspace
-
-## Read When
-
-- Maintaining `docs/ja-JP/**`
-- Updating the Japanese translation pipeline (glossary/TM/prompt)
-- Handling Japanese translation feedback or regressions
-
-## Pipeline (docs-i18n)
-
-- Source docs: `docs/**/*.md`
-- Target docs: `docs/ja-JP/**/*.md`
-- Glossary: `docs/.i18n/glossary.ja-JP.json`
-- Translation memory: `docs/.i18n/ja-JP.tm.jsonl`
-- Prompt rules: `scripts/docs-i18n/prompt.go`
-
-Common runs:
-
-```bash
-# Bulk (doc mode; parallel OK)
-cd scripts/docs-i18n
-go run . -docs ../../docs -lang ja-JP -mode doc -parallel 6 ../../docs/**/*.md
-
-# Single file
-cd scripts/docs-i18n
-go run . -docs ../../docs -lang ja-JP -mode doc ../../docs/start/getting-started.md
-
-# Small patches (segment mode; uses TM; no parallel)
-cd scripts/docs-i18n
-go run . -docs ../../docs -lang ja-JP -mode segment ../../docs/start/getting-started.md
-```
-
-Notes:
-
-- Prefer `doc` mode for whole-page translation; `segment` mode for small fixes.
-- If a very large file times out, do targeted edits or split the page before rerunning.
-- After translation, spot-check: code spans/blocks unchanged, links/anchors unchanged, placeholders preserved.