Summary

parsec ship executes push → PR creation → worktree deletion sequentially. When PR creation fails (e.g., 401 Unauthorized), the worktree is already deleted, making it difficult to push fixes or manually create the PR.

Proposed Solution

• Skip worktree deletion when PR creation fails, with a warning message
• Or add --keep-on-failure flag
• Return non-zero exit code on partial failure

Context

During actual usage, PARSEC_GITHUB_TOKEN expired → 401 on PR creation → worktree deleted despite no PR → had to re-checkout branch and manually create PR with gh