daytona-electron-den

# Daytona Electron Against Den Use this skill for full-stack cloud behavior: one Daytona sandbox runs Den, and a separate Daytona sandbox runs the real Electron app pointed at that Den server. ## Start The Server Sandbox Use the server skill first: ```bash bash .devcontainer/test-server-on-daytona.sh <branch-or-commit> ``` Record the printed values: - `SERVER_SANDBOX` - `DEN_WEB_URL` - `DEN_API_URL` - `DEN_WORKER_PROXY_URL` Validate server health: ```bash curl -sf "$DEN_WEB_URL/api/den/health" curl -sf "$DEN_API_URL/health" ``` ## Start Electron Against Den ```bash bash .devcontainer/test-on-daytona.sh <branch-or-commit> \ --den-base-url "$DEN_WEB_URL" \ --den-api-base-url "$DEN_API_URL" \ --artifacts-volume ``` Add `--require-signin` when the expected behavior must be signed-out until cloud auth completes. Add `--record-video --recording-name <name>` when PR evidence is needed. ## Validate Bootstrap Before testing cloud behavior, prove Electron is using the Daytona Den server: ```js JSON.stringify({ hash: location.hash, text: document.body.innerText.slice(0, 1000) }) ``` Then inspect the desktop bootstrap file: ```bash daytona exec "$SANDBOX" -- 'cat /workspace/.ipollowork-daytona/desktop-bootstrap.json' ``` Expected: `baseUrl` is `DEN_WEB_URL` and `apiBaseUrl` is `DEN_API_URL`, not production. ## Desktop Handoff Pattern For seeded/demo auth, create the handoff URL from the Den API, then paste it into Electron's Cloud Account sign-in code field. Do n...