[sanskarIN]

Production migration — Issue #70 (phase 2)

The independently tested Scarp Docs engine from merged PR #71 now becomes the official static-site renderer, replacing VitePress for production generation, Pages upload, local dev/preview and the downloaded offline documentation archive. This PR preserves all original Markdown content and compiler-release baselines.

What changes

• npm run docs:build: build docs/.scarp/dist with the own TypeScript Markdown renderer; no VitePress or Vue renderer is invoked.
• npm run docs:dev / docs:preview: standalone loopback-only Node HTTP server, with Markdown source watch for development.
• GitHub Pages workflow uploads docs/.scarp/dist, and the same existing 138-route canonical/hreflang/sitemap test now checks this output.
• Offline archive is generated from Scarp's own build. Archive hashing, per-file checksums, English/Hindi routes, Node local server and asset smoke tests remain required.
• The extracted archive is checked by Scarp's own independent Playwright/axe browser test, covering local search, language switching, accessible Command Finder, appearance, mobile layout and zero external requests. The shadow build is also independently browser-tested.
• Updated English/Hindi help, README, and maintainer/engine migration guide to describe the production engine accurately.

Keep verification honest

Legacy VitePress/Vue source and type-checker dependencies remain temporarily to avoid weakening >80 release-pinned compiler/documentation regression tests. They are NOT used to render or deploy the new website; complete cleanup remains tracked under #70. This PR does not publish a stable docs release or change the Scarp compiler.

Merge gate

All eight PR CI jobs must pass, including production archive, independent static page parity and both extracted/offline and shadow browser acceptance. After merge, confirm main CI, Pages build/deploy/smoke and downloadable artifact before saying the migration is deployed. Do not merge on partial test success.