pr create opens a pull request from a fork into the repository -R selects
tangled.org opens a pull request from a fork the way it opens one within a repository: a ticket in the target repository's store, then submitPatch on the target's knot, with sourceRepo naming the fork's DID, the repository the knot fetches the head from (PullCompose.svelte and org.tangled.review.submitPatch in tangled.org/core). tang only ever named the target there. When --repo/-R or TANG_REPO selects the target and the clone's own remote is another repository, pr create now takes the clone as the fork: it checks the head branch on the clone's remote, fetches the target's base branch into FETCH_HEAD, and compares the head with that rather than with a local branch of the same name, for the behind check, the diff and the merge base. The patch names the fork as its sourceRepo, and the result shows fork:branch → target:branch. A target without a store is refused before anything is fetched or written, since the legacy pull record's fork form is no longer in tangled.org's lexicons. PullData gains sourceRepo, which pr create --json now gives. Seen red first: the four fork cases in pr.test.ts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>