René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"vscode: remove the legacy settings migration","articleBody":"## What\n\nRemove the settings migration (`packages/vscode/src/migration.ts`, the `Rstack: Migrate settings` command, the activation-time prompt, `LEGACY_MAPPINGS`, the migration tests and the README section) that maps the retired standalone extensions' `rslint.*` / `rstest.*` keys to `rstack.*`.\n\n## Why\n\n- Pre-1.0 the extension owes no compatibility to earlier states, and the migration only ever served users of the two retired standalone extensions.\n- The mapping already has to model dropped features (`rslint.binPath` / `rslint.customBinPath` have no `rstack.*` equivalent since #14) and half-surfaced edge cases (a skip-only plan is not auto-prompted — flagged in #14 review, deliberately not fixed because of this removal).\n- Keeping it means every settings change in this extension carries a mapping-table update and tests for a one-off flow.\n\n## Scope\n\n- Delete `migration.ts` and its tests; drop the command, the `contributes.commands` entry, the activation prompt and `PROMPT_DISMISSED_KEY` state.\n- Update `packages/vscode/AGENTS.md` (the \"settings migration exists for users of the retired standalone extensions\" sentence in the pre-1.0 rule; adaptation #2 mentions the migration mapping) and the READMEs.\n- Decide whether to keep a one-line README note telling standalone-extension users to re-enter their settings under `rstack.*`.\n\nRefs: #14 (dropped `binPath` / `customBinPath`, added `corePath`).","author":{"url":"https://github.com/fi3ework","@type":"Person","name":"fi3ework"},"datePublished":"2026-08-18T06:40:40Z","url":"https://github.com/rstackjs/rstack-editor/issues/15"}