[sanskarIN]

Why

Issue #70 requires the framework-free Scarp documentation engine to stop importing production data from the legacy docs/.vitepress tree. The published CLI version table and command selector were still owned by the previous VitePress theme, even though the current Scarp-owned renderer does not run Vue/VitePress.

Changes

• Move the complete, unchanged, release-pinned TypeScript command table to scripts/lib/command-finder.ts.
• Migrate production site generation, current-release validation, real browser tests, static site tests, compiler release evidence and command selector tests to the framework-neutral import.
• Retain the old theme path as an explicit one-line compatibility re-export for the historical Vue demo; it no longer duplicates source data.
• Add positive identity assertions that the legacy export and the real production module expose the same release array and selector function, preventing silent divergence.
• Update SCARP-DOCS-ENGINE.md to document remaining legacy-file removal work.

Merge gates

Run TypeScript, all docs and bilingual tests, browser/axe/offline, and every pinned compiler conformance job before merging. No changes to CLI commands, compiler support claims, generated public URLs, or stable release policy.

Addresses a migration gate in #70.