chore: bump oxlint-tsgolint to 0.25 to fix flaky TS2307 on macOS

[rqbazan]

Summary

pnpm rr check fails now and then on macOS with TS2307 on a module that is installed:

vitest.config.ts:1:28: error typescript(TS2307): Cannot find module '@vitest/browser-playwright' or its corresponding type declarations.
test/functional/index.test.ts:2:28: error typescript(TS2307): Cannot find module 'vitest-browser-react' ...
run-run.config.mts:5:20: error typescript(TS2307): Cannot find module '@rrlab/vitest-plugin' ...
test/functional/setup.ts:1:43: error typescript(TS2307): Cannot find module 'vitest' ...

The bug is not in rr, the build or the order of steps. It is in the typescript-go build that oxlint-tsgolint@0.23.0 bundles:

rr check
  tsc (oxlint plugin) → oxlint --type-aware --type-check
    tsgolint 0.23.0 (bundles typescript-go c282336)
      fileLoader parses files on many goroutines
        module resolver → realpath(pnpm symlink)
          realpath_darwin.go: fcntl(fd, F_GETPATH, int(uintptr(&buf)))
            the buffer pointer passes through an int, so Go may move or
            reuse the buffer before the kernel writes into it
          → bad real path → resolution fails → TS2307

• The broken realpath came in with microsoft/typescript-go@a8b2a52 ("Speed up realpath on Linux and macOS"). Fix fnctl F_GETPATH call on macOS microsoft/typescript-go#4178 fixed it (issue Data race in module resolver — SIGSEGV in loadModuleFromTargetExportOrImport / OrderedMap.Keys under concurrent goroutines microsoft/typescript-go#4060), and the fix only touches realpath_darwin.go.
• The upstream report is Sporadical lint/typecheck error in monorepo oxc-project/tsgolint#987: the same TS2307 on vitest in a pnpm repo, and the reporter confirmed oxlint-tsgolint@0.24.0 fixes it.
• ^0.23.0 is a 0.x caret range, so it never moves past 0.23.x. The range has to change by hand.

-    "oxlint-tsgolint": "^0.23.0",
+    "oxlint-tsgolint": "^0.25.0",

0.25.0 is the last 0.x release. It still fits the installed oxlint@1.71.0 (peer >=0.22.1). Going to 7.x would also need oxlint ≥1.75 and new lint rules, so it is left out of this PR.

The typescript-go submodule pinned by each tsgolint tag, compared on GitHub:

tsgolint	typescript-go	has a8b2a52 (bug)	has 704847d (#4178 fix)
v0.23.0	c282336	yes	no
v0.24.0	c080da6	yes	yes
v0.25.0	2bd066d	yes	yes

Evidence

Local, macOS arm64, clean worktree:

• Before (oxlint-tsgolint@0.23.0):

  Command	Failed
  pnpm rr check	4 / 40
  oxlint --type-aware --type-check (no rr)	8 / 60
  same, --threads=1 (oxlint threads only)	6 / 80
  same, GOMAXPROCS=1 (one Go thread in tsgolint)	0 / 100
  tsc --noEmit	0 (passes)

  It still fails without rr and with plain tsc passing, so rr and the project are not the cause. With GOMAXPROCS=1 it never fails, which points to a concurrency bug inside tsgolint's typescript-go.

• After (oxlint-tsgolint@0.25.0):

  Command	Failed
  oxlint --type-aware --type-check	0 / 150
  pnpm rr check	0 / 50

  The typecheck still catches real errors: a probe file with a missing import and a bad assignment reports TS2307 and TS2322.

CI can't show this bug. CI runs on ubuntu-latest and the broken code is darwin-only. None of the CI runs on record failed with TS2307 (the red runs were zizmor and a missing gh-actions repo). So CI is green both before and after this change, and a green CI run proves nothing here. The proof is the local loop above. It still matters on macOS, where the lefthook pre-commit rr tsc and local rr check run.

Merge Danger

Door: two-way

Only a devDependency changes. Reverting package.json and the lockfile undoes it.

Blast Radius: tooling

Nothing in dist or the published package changes, so this PR has no changeset. The one effect is newer tsgolint lint rules in rr check, and with this repo's config they report nothing today.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V4iz3teZoyUZW9nXnX9RQr

[changeset-bot]

⚠️ No Changeset found

Latest commit: cda69ca

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR