chore(deps): update tooling to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	~5.9.3 → ~6.0.3

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • On day 1 and 15 of the month (* * 1,15 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (197 entries)...
✗ Lockfile failed supply-chain policy check (197 entries in 2.9s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 11 lockfile entries failed verification:
  @typescript-eslint/eslint-plugin@8.60.1 was published at 2026-06-01T18:56:00.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/parser@8.60.1 was published at 2026-06-01T18:55:38.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/project-service@8.60.1 was published at 2026-06-01T18:55:12.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/scope-manager@8.60.1 was published at 2026-06-01T18:55:30.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/tsconfig-utils@8.60.1 was published at 2026-06-01T18:55:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/type-utils@8.60.1 was published at 2026-06-01T18:55:46.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/types@8.60.1 was published at 2026-06-01T18:55:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/typescript-estree@8.60.1 was published at 2026-06-01T18:55:21.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/utils@8.60.1 was published at 2026-06-01T18:55:37.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  @typescript-eslint/visitor-keys@8.60.1 was published at 2026-06-01T18:55:12.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)
  typescript-eslint@8.60.1 was published at 2026-06-01T18:56:08.000Z, within the minimumReleaseAge cutoff (2026-06-01T08:54:26.283Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.