diff --git a/.github/workflows/pr.yml b/.github/workflows/pr.yml
index ceb68feaa17..f36bb405e28 100644
--- a/.github/workflows/pr.yml
+++ b/.github/workflows/pr.yml
@@ -434,6 +434,8 @@ jobs:
           pnpm exec vitest run --config config/vitest.config.ts
           src/main/cli/wsl-cli-powershell-boundary.test.ts
           src/main/orca-profiles/profile-index-store.test.ts
+          src/main/runtime/repo-worktree-admin-fingerprint.test.ts
+          src/main/runtime/worktree-scan-admin-fingerprint-gate.test.ts
           src/shared/secure-file-fsync-flags.test.ts
 
       - name: Build package inputs
diff --git a/src/main/runtime/repo-worktree-admin-fingerprint.test.ts b/src/main/runtime/repo-worktree-admin-fingerprint.test.ts
index 15d4aad4484..a8f2fc9d8e4 100644
--- a/src/main/runtime/repo-worktree-admin-fingerprint.test.ts
+++ b/src/main/runtime/repo-worktree-admin-fingerprint.test.ts
@@ -1,5 +1,8 @@
 // Real-binary coverage: the fingerprint's whole job is to predict what `git worktree list` would
 // report, so a mocked filesystem would only prove the assumptions, not the Git layout they model.
+// Also listed in pr.yml's Windows boundary step: reading Git's admin layout directly depends on
+// Windows path resolution, CRLF in `HEAD`/`gitdir`/`commondir`, and whether `worktree move`/`lock`
+// and deleting a live checkout behave as they do on POSIX. The Linux shards cannot reach any of it.
 import { execFile } from 'node:child_process'
 import { mkdir, mkdtemp, realpath, rm, writeFile } from 'node:fs/promises'
 import { tmpdir } from 'node:os'
diff --git a/src/main/runtime/worktree-scan-admin-fingerprint-gate.test.ts b/src/main/runtime/worktree-scan-admin-fingerprint-gate.test.ts
index 05c0fe9cd6f..de97e461f8e 100644
--- a/src/main/runtime/worktree-scan-admin-fingerprint-gate.test.ts
+++ b/src/main/runtime/worktree-scan-admin-fingerprint-gate.test.ts
@@ -1,5 +1,6 @@
 // The fingerprint's own behaviour is covered against real Git in repo-worktree-admin-fingerprint.test.ts.
 // This suite pins the cache wiring: when the probe may skip a `git worktree list`, and when it may not.
+// Also listed in pr.yml's Windows boundary step, so the gate's repo-path handling stays honest there.
 import { beforeEach, describe, expect, it, vi } from 'vitest'
 
 const electronMocks = vi.hoisted(() => {