What problem does it solve? Paperclip dev workspaces run as managed worktree services on pinned ports, so sibling workspaces can squat the port, cloned databases can be incomplete, and runtime rows can report healthy while serving the wrong app. This Skill provides a disciplined run-verify-fix loop that proves real health, login readiness, cloned data, and port ownership before declaring success. ## Core Features & Use Cases - Managed runtime control: Start, stop, and restart worktree services through the Paperclip control-plane runtime-service API instead of detached shell processes. - Port conflict and identity resolution: Detect sibling workspace port squatting by checking the real process cwd via /proc/<pid>/cwd, then stop the true owner through its managed path before restarting the target. - Full database reseed and verification: Reseed the worktree with a full clone from the primary instance and verify health, bootstrap status, login, populated data, and runtime visibility from both the main control plane and the served app. - Use Case: A worktree service URL loads a working Paperclip app but shows the wrong branch's data. The Skill identifies the sibling process owning the pinned port, stops its supervising run, restarts the target service, and confirms the port owner's cwd resolves inside the target worktree. ## Quick Start Ask the agent to start and verify the paperclip-dev workspace service for the current issue, fixing any port conflicts or database problems until health, login, and cloned data all check out.
