chore(deps): update dependency typescript to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	~6.0.0 → ~7.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
readma	Error		Jul 26, 2026 10:58am

[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

Scope: all 5 workspace projects
? Verifying lockfile against supply-chain policies (1431 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 12, reused 0, downloaded 0, added 0
Progress: resolved 14, reused 0, downloaded 0, added 0
Progress: resolved 15, reused 0, downloaded 0, added 0
Progress: resolved 18, reused 0, downloaded 0, added 0
Progress: resolved 20, reused 0, downloaded 1, added 0
Progress: resolved 21, reused 0, downloaded 1, added 0
Progress: resolved 94, reused 0, downloaded 1, added 0
Progress: resolved 211, reused 0, downloaded 1, added 0
Progress: resolved 456, reused 0, downloaded 1, added 0
Progress: resolved 637, reused 0, downloaded 1, added 0
Progress: resolved 945, reused 0, downloaded 1, added 0
Progress: resolved 1242, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (1431 entries in 14s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 7 lockfile entries failed verification:
  @turbo/darwin-64@2.10.7 was published at 2026-07-25T15:21:18.000Z, within the minimumReleaseAge cutoff (2026-07-25T10:57:47.697Z)
  @turbo/darwin-arm64@2.10.7 was published at 2026-07-25T15:21:26.000Z, within the minimumReleaseAge cutoff (2026-07-25T10:57:47.697Z)
  @turbo/linux-64@2.10.7 was published at 2026-07-25T15:21:33.000Z, within the minimumReleaseAge cutoff (2026-07-25T10:57:47.697Z)
  @turbo/linux-arm64@2.10.7 was published at 2026-07-25T15:21:39.000Z, within the minimumReleaseAge cutoff (2026-07-25T10:57:47.697Z)
  @turbo/windows-64@2.10.7 was published at 2026-07-25T15:21:46.000Z, within the minimumReleaseAge cutoff (2026-07-25T10:57:47.697Z)
  @turbo/windows-arm64@2.10.7 was published at 2026-07-25T15:21:53.000Z, within the minimumReleaseAge cutoff (2026-07-25T10:57:47.697Z)
  turbo@2.10.7 was published at 2026-07-25T15:22:03.000Z, within the minimumReleaseAge cutoff (2026-07-25T10:57:47.697Z)

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.