Set up a project on another machine by cloning or copying its checkout and settings

[aaronvanston]

When a project is set up on one connected machine but has no checkout on another, Settings → Projects reports that the checkout is missing. I have to clone or copy the files separately and recreate the project settings before I can work there.

Could that screen offer a way to set up the project on another connected machine?

• Fresh checkout: clone the repository using the destination machine’s Git credentials, then carry over the project settings and actions.
• One-time copy: copy the current files and Git state, including staged and unstaged work, with a choice about ignored files.

The destination should use the existing folder browser, avoid overwriting an existing folder, and only offer machines missing a checkout. The source would remain intact. Ongoing sync, conversation transfer, and provider credential transfer are outside this request.

This is a narrower setup step related to Cross-device continuity #7838.

I have a working implementation in PR #10825, with anonymized before/after images and a short interaction video. I realise the PR is large, so I’m opening this proposal to discuss whether the feature fits T3 Code and what scope maintainers would prefer. The implementation is a concrete reference and can be reduced or split if there is interest.