Release v1.0.7 — Editor checksum fix + Markdown preview stability · udah1/rtl-for-vs-code-and-cursor-agents

RTL for VS Code & Cursor Agents — v1.0.7

Right-to-left support for AI chat in VS Code and Cursor (Cursor Composer, Claude Code, Copilot, Codex, Gemini, and more).

Fix “Your installation appears to be corrupt” — Built-in checksum reconciliation for product.json after the Custom CSS and JS Loader modifies workbench.html. Same idea as community “Fix Checksums” extensions, integrated into this extension.
Auto-fix on startup — Setting rtlForVsCodeAgents.autoFixChecksums (default: true) reconciles checksums when the extension loads.
Manual commands — From the status bar quick menu or Command Palette:
- RTL for VS Code Agents: Fix Editor Checksums (corrupt warning)
- RTL for VS Code Agents: Restore Editor Checksums
Backup — Original product.json is saved as product.json.orig.<editor-version> before changes.

Markdown preview freeze fix — RTL processing is skipped on Markdown document surfaces only (.markdown-editor-react, .ui-rich-text-editor[data-variant="document"], .markdown-preview, .markdown-body), so opening .md in Preview no longer freezes the IDE.
Cursor chat RTL preserved — Composer/agent chat is not blocked by overly broad editor-container selectors.

The corrupt warning appears because Custom CSS patches workbench.html, which no longer matches the hashes in product.json.
Auto-fix runs after extensions load (onStartupFinished). Cursor checks integrity at launch, so you may still see the warning once on a session where product.json was reset (e.g. after uninstalling another checksum-fix extension). A full quit (Cmd+Q) and restart after checksums are reconciled usually clears it.
Re-run fix (or restart with auto-fix on) after each Cursor/VS Code update or Enable/Disable Custom CSS cycle.
On Windows, writing to the install folder may require Run as administrator for the manual fix command.
Use Restore Editor Checksums to revert product.json from the backup.