chore(deps): update dependency typescript to v7

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
typescript (source)	devDependencies	major	~6.0.3 → ~7.0.2

---

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: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

Scope: Renovate dependency bump only — docs/package.json and docs/yarn.lock, bumping typescript from ~6.0.3 to ~7.0.2 (major version). No application/engine source is touched, so the repo's core CRITICAL RULES (dual-mode source-gen/reflection, snapshot tests, AOT) don't apply here.

Findings

• ✅ No manual review comments outstanding to address — only the automated Codacy check has posted (0 issues).
• ⚠️ Major version bump with no dedicated type-check gate. docs/tsconfig.json explicitly says it's "not used in compilation... here just for a nice editor experience," and docusaurus build (the yarn build step used in deploy-pages.yml / deploy-pages-test.yml) transpiles via Babel/SWC rather than doing a full tsc type-check. There's no CI step invoking the typecheck script (tsc) in package.json. That means TS7's stricter/changed type-checking behavior won't actually be exercised by CI — a build-breaking config/type issue would only surface if it also breaks the JS emit, not from type errors alone. This is a pre-existing gap, not something introduced by this PR, but it's worth being aware of: the green "Test Deploy to GitHub Pages" check isn't a reliable signal that TS7 is fully compatible, since it won't catch pure type-level breakage. Worth running yarn typecheck locally (or adding it as a CI step) before trusting this major bump on faith.
• No architectural concerns otherwise — this is a self-contained devDependency bump confined to the docs workspace, with no runtime/production code impact (TypeScript here is dev-only, used for editor tooling, not part of the published site).

Recommendation: Safe to merge once the "Test Deploy to GitHub Pages" and modularpipeline checks (pending at review time) go green. Given this is a major SemVer bump for a dev-only tool with no CI type-check gate, consider a quick local cd docs && yarn typecheck sanity check before/after merging, and consider adding yarn typecheck to CI generally so future major bumps here are actually verified rather than just build-tested.