chore(deps): typescript 5.9.3→6.0, pnpm 10.28→11.0

[Mlaz-code]

Summary

• typescript 5.9.3 → 6.0.3. TS 6 turns 5.x deprecations into errors. The only fallout here: TS 6's TS2882 (stricter side-effect imports) flagged the CSS imports in app/[lang]/layout.tsx (import "../globals.css", import "nextra-theme-docs/style.css"). Fixed with a new globals.d.ts (declare module "*.css" / "*.scss") — Next's bundler still handles CSS at build time; this just satisfies tsc --noEmit.
• packageManager pnpm@10.28.2 → pnpm@11.0.9. pnpm 11 hard-fails on unapproved dependency build scripts, so pnpm-workspace.yaml now carries an allowBuilds: block: sharp: true (native image lib used by Next image optimization — its install/check.js should run), core-js: false / protobufjs: false (their postinstalls are just funding banners — nothing to build). pnpm-workspace.yaml is new (pnpm 11 generates it).
• Lockfile stayed at lockfileVersion: '9.0' (no format migration).

Verified locally

• pnpm install clean — sharp install/check.js runs, no ERR_PNPM_IGNORED_BUILDS
• tsc --noEmit → exit 0
• CI: pnpm build (next build + pagefind) — not run locally, CI will catch any bundler-side type issues

🤖 Generated with Claude Code

[Mlaz-code]

Merge gate: holding — no CI/Vercel preview status on the branch yet. docs.sharpapi.io has no PR-validation workflow, so the only signal is the Vercel preview build. A major typescript 5.9→6.0 + pnpm 10→11 bump is exactly the kind of change where the build can fail in ways tsc --noEmit won't catch (the body confirms pnpm build/next build wasn't run locally). Will autogate once the Vercel preview deploy reports green; until then this needs the preview build to pass (or a human merge if Vercel isn't posting).

[Mlaz-code]

Merge gate update: there's no automated green signal available for this PR. docs.sharpapi.io has no GH Actions PR-validation workflow, and the Vercel preview won't build it — this PR is Paperclip-authored, and Vercel rejects deployments whose git author lacks project access (same root cause that surfaces as a Vercel check FAILURE on sibling PR sharpapi-site#96: "Git author Paperclip-Paperclip must have access to the project on Vercel"). So this can't be autogated — it needs a human merge (Vercel will still build main on merge), or someone grants the Paperclip git author Vercel project access so previews run. FWIW the diff is small (+29/-21, 4 files) and the author verified tsc --noEmit exit 0, but not pnpm build/next build.