@sdods/cli 0.20.0 → 0.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sdods/cli",
-  "version": "0.20.0",
+  "version": "0.22.0",
   "description": "SDODS command line: run, record, analyze, agents, MCP server, scheduler and the web server.",
   "license": "Apache-2.0",
   "funding": "https://sdods.com/sponsor/",
@@ -26,22 +26,22 @@
     "node": ">=22"
   },
   "dependencies": {
-    "@sdods/contracts": "0.20.0",
-    "@sdods/core": "0.20.0",
+    "@sdods/contracts": "0.22.0",
+    "@sdods/core": "0.22.0",
     "commander": "^15.0.0",
     "execa": "^10.2.1",
     "picocolors": "^1.1.1",
     "semver": "^7.8.5",
     "yaml": "^2.9.1",
     "zod": "^4.6.7",
-    "@playwright/test": "^1.64.0",
-    "playwright-core": "^1.64.0",
-    "@sdods/integrations": "0.20.0",
-    "@sdods/mcp": "0.20.0",
-    "@sdods/agents": "0.20.0",
-    "@sdods/db": "0.20.0",
+    "@playwright/test": "^1.64.1",
+    "playwright-core": "^1.64.1",
+    "@sdods/integrations": "0.22.0",
+    "@sdods/mcp": "0.22.0",
+    "@sdods/agents": "0.22.0",
+    "@sdods/db": "0.22.0",
     "csv-parse": "^7.0.3",
-    "@sdods/server": "0.20.0"
+    "@sdods/server": "0.22.0"
   },
   "homepage": "https://sdods.com",
   "bugs": {

package/skills/sdods-start-ui/SKILL.md

@@ -101,7 +101,7 @@ Read the rows in order and take the first that matches:
 |---|---|---|
 | `package.json` says `sdods-monorepo` — **even if `sdods` is on PATH** | a **source checkout** | `bun run web:build`, then `bun run sdods serve --open` |
 | `sdods` on PATH, anywhere else | a **global install** (installer, npm, Homebrew) | `sdods serve --open` |
-| neither, Docker is running | the **container** | `docker run --rm -p 8080:8080 -v sdods-data:/data ghcr.io/yarlisaisolutions/sdods-server` |
+| neither, Docker is running | the **container** | `docker run --rm -p 8080:8080 -v sdods-data:/data sdods/sdods-server` |
 | you want no terminal at all | the **desktop app** | install from <https://sdods.com/download>, launch it |
 
 > **Inside a checkout, always use `bun run sdods`, never the global `sdods`.** The two drift, and
@@ -155,19 +155,14 @@ The CLI is identical on every OS; only the shell and the paths differ.
 | Windows (PowerShell) | `sdods serve --open` |
 | Windows (cmd) | `sdods serve --open` — the installer writes both `sdods.cmd` and `sdods.ps1` |
 | WSL | use the Linux command inside WSL, not the PowerShell one |
-| Docker (any host) | `docker run --rm -p 8080:8080 -v sdods-data:/data ghcr.io/yarlisaisolutions/sdods-server` |
+| Docker (any host) | `docker run --rm -p 8080:8080 -v sdods-data:/data sdods/sdods-server` |
 
 Defaults: **`http://127.0.0.1:4444`** for the CLI, **`http://localhost:8080`** for Docker (the
 image binds `0.0.0.0:8080`). `--open` launches the browser (`open` / `start` / `xdg-open` by
 platform). `--host 0.0.0.0` exposes it on the LAN — only do that deliberately.
 
-The image is published for `linux/amd64` and `linux/arm64`, so the same command runs natively on
-Apple silicon and arm64 servers. Tags up to `0.9.0` carry amd64 only, and Docker refuses that pull
-on arm64 rather than emulating; for those, add the platform flag:
-
-```bash
-docker run --rm --platform linux/amd64 -p 8080:8080 -v sdods-data:/data ghcr.io/yarlisaisolutions/sdods-server:0.9.0
-```
+The image is published on Docker Hub for `linux/amd64` and `linux/arm64` (tags from `0.20.0`), so
+the same command runs natively on Apple silicon and arm64 servers.
 
 If the run must come from a source checkout, `bun run web:build` is not optional — see
 Troubleshooting.