paperclip-dev-workspace-run-verify-fix

原文涵盖的主题

• Paperclip Dev Workspace Run / Verify / Fix
• Hard rules
• Inputs to collect
• Normal run sequence
• Managed start / stop
• Port conflicts and workspace identity
• Full database reseed
• Core verification probes

This skill is for Paperclip-specific development workspaces whose service is started through project execution workspace runtime services, typically a worktree service such as paperclip-dev. Success means all of these are true: the service was started through the normal managed runtime path, not a detached workaround the worktree database is a full bootstrapped isolated clone of the primary instance database /api/health returns status: ok and bootstrapStatus: ready the root page returns 200 and does not show the first-admin setup gate the board user can log in with their normal dev credentials the app shows populated cloned data, not only a manually copied auth user the main control plane shows the service as running / healthy with the expected URL the served workspace app also knows about that service and shows it as running / healthy the process that owns the service port really belongs to the target workspace: readlink /proc/ /cwd resolves inside the target worktree, not a sibling workspace If any item fails, keep fixing. Do not mark the issue done because one probe passed. The master checkout /srv/paperclip/home/paperclipai/paperclip (the primary repo with the real instance .en

这里只展示节选，请以完整原文和当前要求为准。