[codex] fix Daytona validation runbooks

.opencode/skills/daytona-cloud-instance/SKILL.md

@@ -13,10 +13,10 @@ Start the Den cloud stack in Daytona, confirm it is reachable, and return the UR
 
 ## Fast Path
 
-From the repo root, prefer the existing Daytona helper when available:
+From the repo root, prefer the existing Daytona server helper when available:
 
 ```bash
-bash .devcontainer/test-on-daytona.sh $(git rev-parse --abbrev-ref HEAD) --server-only --artifacts-volume
+bash .devcontainer/test-server-on-daytona.sh $(git rev-parse --abbrev-ref HEAD)
 ```
 
 If the branch is local-only, push it first or apply the local diff manually in the sandbox before validating.

.opencode/skills/daytona-dev/SKILL.md

@@ -13,7 +13,7 @@ browser.
 
 - Daytona CLI installed: `brew install daytonaio/cli/daytona` or download from [GitHub releases](https://github.com/daytonaio/daytona/releases)
 - Logged in: `daytona login`
-- Using the "Different AI" org: `daytona organization use "Different AI"`
+- Using the right Daytona organization for your workspace: `daytona organization use "<org-name>"`
 
 ## Quick Start
 

.opencode/skills/daytona-seeded-cloud-demo/SKILL.md

@@ -148,7 +148,9 @@ Daytona cloud demo is running and seeded.
 
 ## Troubleshooting
 
-If `.devcontainer/test-on-daytona.sh --server-only` appears in older docs, do not use it unless this checkout supports that flag. Use `.devcontainer/test-server-on-daytona.sh` for server-only cloud demos.
+If older docs suggest running the Electron helper in a server-only mode, do not
+use that path unless this checkout supports it. Use
+`.devcontainer/test-server-on-daytona.sh` for server-only cloud demos.
 
 If sign-in returns `403` for email verification, Den API is not running with `OPENWORK_DEV_MODE=1` or did not restart after env changes. Restart the Den stack and rerun the seed.
 

.opencode/skills/run-evals/SKILL.md

@@ -16,7 +16,7 @@ Run the OpenWork UI evaluation flows against a real Electron app. Prefer a fresh
 ## Prerequisites
 
 - `daytona` CLI installed and logged in (`daytona login`)
-- Using the "Different AI" org (`daytona organization use "Different AI"`)
+- Using the right Daytona organization for your workspace (`daytona organization use "<org-name>"`)
 - The `.devcontainer/` files exist in the repo
 - Optional provider coverage: reusable Daytona volume `openwork-eval-secrets`
   populated with `.env` files using `bash .devcontainer/setup-daytona-secrets-volume.sh .newtoken`
@@ -38,7 +38,7 @@ Use these Daytona skills when an eval touches a specific area:
 Use the repo helper unless you need to debug a specific Daytona step manually:
 
 ```bash
-daytona organization use "Different AI"
+daytona organization use "<org-name>"
 bash .devcontainer/test-on-daytona.sh <branch-or-commit>
 ```
 

evals/README.md

@@ -61,7 +61,7 @@ display needed. See [`daytona-flows.md`](./daytona-flows.md) for full details.
 Quick start:
 
 ```bash
-daytona organization use "Different AI"
+daytona organization use "<org-name>"
 bash .devcontainer/test-on-daytona.sh [branch-or-commit]
 # Use the printed Electron CDP URL with browser_* tools.
 ```

evals/daytona-flows.md

@@ -10,7 +10,7 @@ Daytona proxy.
 ### 1. Create/start the sandbox
 
 ```bash
-daytona organization use "Different AI"
+daytona organization use "<org-name>"
 bash .devcontainer/test-on-daytona.sh [branch-or-commit]
 ```