[sanskarIN]

Third phase of #70 — remove obsolete framework dependencies

The official Pages build has already switched to Scarp-owned TypeScript and has passed production build/deploy/live smoke in merged PR #72. This cleanup removes the VitePress and vue-tsc npm packages and replaces the legacy Vue-based type-checking policy with the standalone TypeScript compiler, without changing published source content or routes.

• Remove vitepress and vue-tsc devDependencies; change npm run typecheck to tsc --noEmit -p tsconfig.json.
• Scope TS checks to authored scripts, neutral pure TS release/search metadata and the Scarp-owned browser/build code. Old unused Vue SFCs are deliberately not type-checked because production does not load them.
• New toolchain mutation tests require the independent production build, own dev/preview server, pinned TypeScript + Markdown/YAML parsing dependencies and retention of TypeScript-major Dependabot review; forbid accidentally reintroducing VitePress/vue-tsc packages.
• Remove obsolete vue-tsc Dependabot exception; retain cautious TypeScript 7 major-update hold while the owned compiler's programmatic API is verified.
• Update README, architecture notes and CI descriptions to reflect actual production implementation.

Migration honesty

Some old .vitepress source/config files remain as historical fixtures for release evidence and bilingual validation until those policies are migrated; they are not the website renderer. See Issue #70 for removal of these remaining fixtures. Do not weaken compiler conformance, and do not publish a stable release.

Merge gate

All 8 CI checks, including the real extracted-offline Chromium/axe checks and existing pinned compiler conformance, must be green before merge; verify Pages again after merge.