feat: add portable rule-owned migration dashboard

README.md

@@ -1,12 +1,12 @@
 # Solid Migration Assistant
 
-Solid Migration Assistant is an experimental, read-only analyzer for selected Solid 1.9 migration sites targeting Solid `2.0.0-rc.0`.
+Solid Migration Assistant is an experimental Solid 1.9 → Solid 2 migration assistant targeting Solid `2.0.0-rc.0`. It ships two workflows: a read-only `analyze` workflow that prints guidance for supported migration sites, and a deterministic `transform` workflow that relocates a small, pure subset of legacy import subpaths.
 
-The assistant scans project-owned `.js`, `.jsx`, `.ts`, and `.tsx` source, prints one detailed guidance string for each supported detection, and exits successfully when migration work is found. Guidance is sorted deterministically and printed to standard output; the Codemod runtime's progress lines and the final disclosure are written to standard error. The analyzer never edits the target and does not generate reports, dashboards, or other output there. Codemod analytics are disabled. Codemod may persist workflow and task state in normal platform user-data directories outside the target; the assistant does not redirect or remove that runtime state.
+The assistant scans project-owned `.js`, `.jsx`, `.ts`, and `.tsx` source, prints one detailed guidance string for each supported detection, and exits successfully when migration work is found. Guidance is sorted deterministically and printed to standard output; the Codemod runtime's progress lines and the final disclosure are written to standard error. The analyzer never edits the target and generates no artifact unless `--report FILE` is explicitly supplied. Codemod analytics are disabled. Codemod may persist workflow and task state in normal platform user-data directories outside the target; the assistant does not redirect or remove that runtime state.
 
-## Run the RC analyzer
+## Run the RC analyzer and transform
 
-> **RC scope:** this `0.2.1` analyzer targets Solid `2.0.0-rc.0`, scans project-owned `.js`, `.jsx`, `.ts`, and `.tsx` source, and covers only the detections listed below. A clean run is not proof that a project is ready for Solid 2.
+> **RC scope:** version `0.3.0` targets Solid `2.0.0-rc.0` and covers only the detections and relocations documented below. A clean analyzer run is not proof that a project is ready for Solid 2.
 
 After npm publication, run the package from a project root with Node 20 or newer and npm (no pnpm installation is needed):
 
@@ -22,6 +22,14 @@ The current directory is analyzed by default. To analyze another directory:
 npx --yes solid-migration-assistant@latest --target /path/to/a/solid-project
 ```
 
+To keep the same terminal guidance and also write the selected-rule pilot dashboard:
+
+```sh
+npx --yes solid-migration-assistant@latest --target . --report migration-report.html
+```
+
+The portable HTML covers `web-import`, `component-renames`, `create-effect`, and read-only legacy-subpath relocation previews. It contains the full matched source line range plus one complete context line before and after every finding. Treat it as project source. Existing files are refused unless `--force` is explicit; browsers open only with `--open`.
+
 The supported rules detect the complete Solid 2 RC migration quick rename / removal map:
 
 **Imports** — `solid-js/web`, store, renderer, and JSX-runtime subpath repackaging.
@@ -30,15 +38,35 @@ The supported rules detect the complete Solid 2 RC migration quick rename / remo
 **Props & store** — `mergeProps`/`splitProps`, `onMount`, `unwrap`, `produce`, and `createMutable`/`modifyMutable`.
 Coverage is deliberately limited. Even when no guidance is printed, review the documented exclusions and perform the application's normal type, build, and behavior validation; a clean analyzer run is not a readiness result.
 
+## Transform
+
+The opt-in `transform` workflow rewrites exactly five pure legacy Solid import subpaths in place and changes nothing else:
+
+- `solid-js/h` → `@solidjs/h`
+- `solid-js/html` → `@solidjs/html`
+- `solid-js/universal` → `@solidjs/universal`
+- `solid-js/jsx-runtime` → `@solidjs/web/jsx-runtime`
+- `solid-js/jsx-dev-runtime` → `@solidjs/web/jsx-dev-runtime`
+
+It covers static imports, re-exports, dynamic `import()`, and `require()` calls; preserves each reference's import form and quote style; and emits one per-edit report line (`file:line:column`, old → new, plus the migration-guide link). Every move is a pure package relocation with no removed, renamed, or behaviorally changed export, so no binding-level review is required for these five paths. The workflow is idempotent and writes no report files or other artifacts in the target. It deliberately leaves `solid-js/web`, `solid-js/store`, already-migrated paths, and near-miss subpaths such as `solid-js/h-extra` and `vendor/solid-js/h` untouched.
+
+In this repository, run `pnpm transform` against the current directory, or invoke the Codemod CLI directly to target another directory:
+
+```sh
+node ./node_modules/codemod/codemod --disable-analytics workflow run -w transform.yaml -t /path/to/a/solid-project --allow-dirty --no-interactive
+```
+
+After publication, select the `transform` workflow from the Codemod platform (it is registered with `default: false`).
+
 ## Verify the repository
 
 ```sh
 pnpm install --frozen-lockfile
 pnpm verify
 ```
 
-Verification runs comprehensive rule fixtures and an end-to-end project fixture, checks exact ordered guidance across repeated runs, and proves analysis leaves every target file unchanged.
+Verification runs comprehensive analysis and transformation rule fixtures plus end-to-end analyzer and transform fixtures; it checks exact ordered guidance, proves the analyzer leaves every target file unchanged, and proves the transform is idempotent and changes nothing outside the five relocated module strings.
 
 See [`codemods/solid-migration-assistant/README.md`](codemods/solid-migration-assistant/README.md) for rule boundaries. Feedback is collected through ordinary [public GitHub issues](https://github.com/devagrawal09/solid-migration-assistant/issues/new).
 
-Automated migrations are a possible future roadmap item; this preview ships no executable transforms. The project is licensed under the [MIT License](LICENSE).
+Broader automated migrations remain a possible future roadmap item. The project is licensed under the [MIT License](LICENSE).

codemods/solid-migration-assistant/README.md

@@ -1,12 +1,12 @@
 # Solid Migration Assistant
 
-This package implements Solid Migration Assistant as a single read-only workflow for a narrow Solid 1.9 client-application profile. It scans project-owned `.js`, `.jsx`, `.ts`, and `.tsx` source files and prints one detailed, location-bearing guidance string per supported migration site. The workflow returns no edits and writes no files.
+This package implements Solid Migration Assistant as two workflows for a narrow Solid 1.9 client-application profile. The read-only `analyze` workflow scans project-owned `.js`, `.jsx`, `.ts`, and `.tsx` source files and prints one detailed, location-bearing guidance string per supported migration site; without an explicit report option it returns no edits and writes no files. The `transform` workflow deterministically relocates a small, pure subset of legacy import subpaths.
 
 The migration target is pinned to Solid `2.0.0-rc.0` at upstream commit [`ff4d3c44`](https://github.com/solidjs/solid/tree/ff4d3c4479163fbdd3327f5b22d0c3ea7bd1a2c5).
 
 ## Analyze with npm
 
-> **RC scope:** version `0.2.1` targets Solid `2.0.0-rc.0`, analyzes project-owned `.js`, `.jsx`, `.ts`, and `.tsx` source, and implements only the detections documented below. A clean run is not proof that a project is ready for Solid 2.
+> **RC scope:** version `0.3.0` targets Solid `2.0.0-rc.0` and implements only the detections and relocations documented below. A clean run is not proof that a project is ready for Solid 2.
 
 After npm publication, run this from the project root with Node 20 or newer and npm (pnpm is not required):
 
@@ -22,6 +22,20 @@ The current directory is the default target. An explicit target may be absolute
 npx --yes solid-migration-assistant@latest --target /path/to/a/solid-project
 ```
 
+### Portable pilot report
+
+Add `--report FILE` to keep all current terminal guidance and also write one portable, hash-routed HTML report for that immutable run:
+
+```sh
+npx --yes solid-migration-assistant@latest --target . --report migration-report.html
+```
+
+The pilot dashboard includes only `web-import`, `component-renames`, `create-effect`, and the read-only `legacy-subpath-relocation` edit preview. Other supported rules remain terminal-only; their absence from the dashboard is not a clean result or a full-migration claim. The preview proposes safe relocation edits but never applies them during analysis.
+
+The command refuses an existing destination. Add `--force` to replace it atomically. It never launches a browser unless `--open` is also supplied. Every generated HTML embeds project source—the complete matched line range plus one complete line before and after—and the absolute analyzed target path used by editor links. Treat and share the report as project source and local machine metadata. VS Code actions use that fixed generation-time path; if the project is moved or the report is opened on another machine, those links will not point at the project copy there.
+
+The dashboard starts in the current operating-system light or dark preference. Its accessible theme switch changes only the open page; the choice is not stored, so reload and reopen return to the current system preference. Each finding offers a direct VS Code deep link and a small extensible overflow menu with a portable `relative/path:line:column` copy fallback. The header’s wrapped target-root utility row also copies the fixed absolute analyzed root.
+
 A run with detections exits successfully. Complete opaque guidance strings are exact-deduplicated, sorted lexically as whole strings, and printed once to standard output as a terminal aggregate. The Codemod runtime's progress lines and the final disclosure are written to standard error. To capture the findings in a file, redirect standard output: `npx --yes solid-migration-assistant@latest --target . > report.txt`; to also capture progress and the disclosure, redirect both streams: `npx --yes solid-migration-assistant@latest --target . > report.txt 2>&1`. The analyzer does not edit the target or create persistent output there, and Codemod analytics are disabled. Codemod may persist workflow and task state in normal platform user-data directories outside the target; the assistant does not redirect or remove that runtime state.
 
 ## Supported detections
@@ -63,11 +77,31 @@ A run with detections exits successfully. Complete opaque guidance strings are e
 
 Every finding links the immutable pinned [RC migration guide](https://github.com/solidjs/solid/blob/ff4d3c4479163fbdd3327f5b22d0c3ea7bd1a2c5/documentation/solid-2.0/MIGRATION.md). Coverage follows the guide's complete quick rename / removal map.
 
+## Transform
+
+The opt-in `transform` workflow relocates exactly five pure legacy Solid import subpaths and changes nothing else:
+
+- `solid-js/h` → `@solidjs/h`
+- `solid-js/html` → `@solidjs/html`
+- `solid-js/universal` → `@solidjs/universal`
+- `solid-js/jsx-runtime` → `@solidjs/web/jsx-runtime`
+- `solid-js/jsx-dev-runtime` → `@solidjs/web/jsx-dev-runtime`
+
+The transform covers static imports, re-exports, dynamic `import()`, and `require()` calls; preserves each reference's import form and quote style; and emits one per-edit report line (`file:line:column`, old → new, plus the migration-guide link). Every move is a pure package relocation with no removed, renamed, or behaviorally changed export, so the rewrite is safe without binding-level review. The workflow is idempotent and writes no report files or other artifacts in the target. It deliberately leaves `solid-js/web`, `solid-js/store`, already-migrated paths, and near-miss subpaths such as `solid-js/h-extra` and `vendor/solid-js/h` untouched.
+
+In this repository, run `pnpm transform` against the current directory, or invoke the Codemod CLI directly to target another directory:
+
+```sh
+node ./node_modules/codemod/codemod --disable-analytics workflow run -w transform.yaml -t /path/to/a/solid-project --allow-dirty --no-interactive
+```
+
+After publication, select the `transform` workflow from the Codemod platform (it is registered with `default: false`).
+
 ## Deliberate limits
 
 Current coverage is deliberately limited: the analyzer does not cover indirect calls, shadowed bindings, unsupported argument counts, re-exports, dynamic imports, `require`, TypeScript `import()` type expressions, configuration, dependencies, SSR, libraries, monorepos, or cross-file intent. Binding-sensitive call and JSX rules also exclude aliased and namespace bindings. No guidance—or a clean run—is not a readiness result and does not imply complete Solid 2 migration coverage.
 
-Automated transforms are roadmap-only. This package exposes no transform command, workflow, test, or implementation.
+The read-only `analyze` workflow remains detection-only. Broader automated transforms remain roadmap items beyond the five pure import-path relocations implemented by the `transform` workflow.
 
 ## Verify
 
@@ -77,4 +111,4 @@ From the workspace root:
 pnpm verify
 ```
 
-Verification checks detection-only architecture, comprehensive rule boundaries, exact and repeatable terminal output, fixture immutability, TypeScript types, and workflow schema validity.
+Verification checks the two-workflow architecture, comprehensive analysis and transformation rule boundaries, exact and repeatable terminal output, analyzer fixture immutability, transform idempotency, TypeScript types, and workflow schema validity.

codemods/solid-migration-assistant/codemod.yaml

@@ -1,8 +1,8 @@
 schema_version: "1.0"
 
 name: "solid-migration-assistant"
-version: "0.2.1"
-description: "Read-only Solid 1.9 to Solid 2 RC migration analyzer for project-owned JavaScript and TypeScript source"
+version: "0.3.0"
+description: "Solid 1.9 to Solid 2 RC migration assistant: read-only analyzer plus deterministic legacy import-path relocation for project-owned JavaScript and TypeScript source"
 author: "Solid Migration Assistant Contributors"
 license: "MIT"
 category: "migration"
@@ -22,3 +22,6 @@ workflows:
   - name: analyze
     default: true
     path: workflow.yaml
+  - name: transform
+    default: false
+    path: transform.yaml