fix(ci): check-ui-mcp-version-copy.mjs's hardcoded stale-version literals are frozen 3 majors behind the real minimum floor

[JSONbored]

Context

scripts/check-ui-mcp-version-copy.mjs:48,51,54 hardcode v0.2/0.2.x/0.2.0 as the "stale version"/"minimum-supported floor" literals this script scans docs copy for. Git history confirms the real minimum floor moved 0.2.0 → 0.5.0 without this script ever being updated, and the known-latest has since moved 0.3.0 → 0.9.0 → 1.0.0/2.0.0/3.0.0 via subsequent releases. The script's only remaining real defense against version-copy drift is a best-effort live npm-registry diff; its deterministic text-scan half targets a version several majors out of date and can't catch current drift.

Requirements

• Update the hardcoded version literals to reflect the actual current minimum-supported floor (check packages/loopover-mcp/CHANGELOG.md/current compatibility docs for the real current value, don't just guess).
• Consider whether this floor should be read from a single source of truth (e.g. the same place src/services/mcp-compatibility.ts derives LATEST_RECOMMENDED_MCP_VERSION) instead of a separately hardcoded literal here, to prevent this exact drift from recurring — this is the same root-cause pattern as the sibling smoke-production.mjs issue filed alongside this one.

Test Coverage Requirements

A test confirming the script's literals match the actual current floor (or, better, that it reads the floor dynamically and therefore can't drift).

Deliverables

• Version literals corrected to the actual current floor, or converted to a dynamic read from the single source of truth.

Expected Outcome

This script's deterministic drift-detection actually detects current drift instead of checking against a value from years-old code.

Links & Resources

• scripts/check-ui-mcp-version-copy.mjs:48,51,54
• The companion smoke-production.mjs issue (same root-cause pattern)

[linear-code]

JSO-4377