What problem does it solve? Todero dev workspaces started through managed runtime services can silently break: a sibling workspace squats the pinned port, the cloned database is incomplete, the setup gate reappears, or the control plane reports healthy while the URL serves the wrong worktree. This Skill provides a disciplined run-verify-fix loop that proves real health instead of trusting a single passing probe. ## Core Features & Use Cases - Managed runtime start/stop/restart: Uses the control-plane runtime-service API with run-id headers instead of detached pnpm dev processes. - Port-owner identity verification: Confirms via /proc/<pid>/cwd that the process owning the pinned service port actually belongs to the target worktree, and resolves sibling-workspace port squats by stopping the true owner first. - Full database reseed: Runs npx todero worktree reseed --from-instance default --seed-mode full to restore a complete isolated clone when login or data is missing. - End-to-end verification: Checks /api/health bootstrap status, login readiness, populated cloned data, and runtime visibility from both the main control plane and the served workspace app. - Use Case: An agent is asked to fix a todero-dev workspace whose URL loads but shows another branch's data; the Skill walks through identifying the squatting sibling process, stopping its supervisor, restarting the target service, and verifying identity before closing the issue. ## Quick Start Ask the agent to start and verify the todero-dev workspace service for the current issue, fixing any port conflicts or database problems until health, login, and cloned data all check out.
