Issue 15023 real app after proof
Head: 60c4f3549f7a66028c7ed730658edf2972121d24. Integrated main: 6e79211743. Before app reproduction base: bb7783e295.
Same Linux fs-35 vp run dev server, isolated .t3 state, browser 1280x800, same disposable checkout and config as runtime-before.txt.
The Node watch server restarted when the resolver changed. Its project identity enrichment completed asynchronously.
Browser authenticated GET /api/orchestration/shell with x-t3-orchestration-protocol: 2 returned HTTP 200:
{
  "id": "c1167c54-a7a8-4a3b-be84-2925b57d2d75",
  "title": "checkout",
  "workspaceRoot": "/tmp/issue-15023-repro/checkout",
  "repositoryIdentity": {
    "canonicalKey": "github.com/juliusmarminge/t3code",
    "locator": { "source": "git-remote", "remoteName": "origin", "remoteUrl": "https://github.com/juliusmarminge/t3code.git" },
    "rootPath": "/tmp/issue-15023-repro/checkout",
    "displayName": "juliusmarminge/t3code",
    "provider": "github", "owner": "juliusmarminge", "name": "t3code"
  }
}
Result: the marked fork now determines project identity; locator retains the actual origin name and URL.
No PR create, merge, close or update action was executed. No renderer was changed by this patch.

Final integrated real app rerun: browser navigated back to http://localhost:6451/ after dependency refresh; authenticated shell request again returned the exact fork repositoryIdentity above on final HEAD60c4f3549f.