Allow Standalone Clones as Carry Targets

[ptr727]

Summary

• Allow an isolated standalone feature clone to serve as a carry target.
• Retain the repository-root, origin, branch, ancestry, registration, and unrelated-change guards.
• Add coverage that exercises a standalone clone against the target verifier.

Validation

• Ruff check and format check passed across the repository.
• mypy passed.
• All 19 carry-engine tests passed.

This addresses the actionable review finding on promotion PR #811.

[Copilot]

Pull request overview

This PR updates the carry-engine target verifier to accept an isolated, standalone feature-branch clone (not only linked worktrees) as a valid carry target, and adds a regression test to cover that scenario.

Changes:

• Relax carry.verify_target() by removing the guard that rejected primary checkouts (standalone clones).
• Extend the carry verifier tests to confirm a standalone clone on a feature branch is accepted.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
scripts/carry.py	Allows standalone feature-branch clones to pass verify_target() by removing the linked-worktree-only check.
scripts/tests/test_carry.py	Adds coverage that clones the remote into a standalone checkout and verifies it is accepted as a target.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.