feat: migrate workflows to TypeScript orchestration

[devagrawal09]

Summary

Migrates Solid Migration Assistant from the YAML/Butterflow workflows (workflow.yaml, transform.yaml, codemod.yaml, 41 per-rule scripts/ entrypoints, emit-report.ts, and codemod:workflow shared state) to two inline TypeScript orchestration workflows on @codemod.com/orchestration.

• workflows/analyze.ts: each of the 37 named analyzers is its own inline jssg() definition, awaited as its own sequential workspace-semantic command, in the order the YAML workflow ran its steps.
• workflows/transform.ts: the three deterministic rewrites stay three separate sequential commands, so later rules see earlier output.
• shared/entrypoint.ts is now a per-file adapter (analyzeFile / transformFile) returning structured { content, output } results instead of accumulating into workflow state under a lock. It is bundled into every transform artifact and imports nothing from the runtime.
• shared/workflow.ts holds the shared include/exclude globs, the FileStrings output guard, and aggregateReport, which flattens, exact-deduplicates, and sorts each command's per-file strings exactly as the removed report emitter did.
• shared/run-workflow.mjs no longer spawns the Codemod CLI. launch() re-runs the module as a Node 24 workflow process (--experimental-transform-types plus shared/register-ts.mjs, a module hook that strips types for .ts under node_modules), loads the workflow through the orchestration build step, and runs it with one BridgeExecutor per command. SIGINT/SIGTERM are forwarded and cancel the command in flight.

Behavior changes

• CLI gains a transform subcommand: solid-migration-assistant [analyze|transform] [--target <dir>]. analyze remains the default.
• Guidance and transform report lines are printed to stdout by the launcher; only the final disclosure (analyze only) goes to stderr. There are no runtime progress lines anymore.
• Usage/target errors exit 2; a failed or cancelled command exits 1. The launcher fails before starting anything when no bridge binary exists.
• Exact guidance output, deterministic ordering, cross-file references() resolution, analyzer immutability, and transform idempotency are unchanged and covered by the same fixtures.
• Node engine bumped to >=24.0.0 (needed for registerHooks/stripTypeScriptTypes and type transformation).
• pnpm validate (YAML schema validation) is gone; check-types now typechecks both the sandbox-side program (tsconfig.json) and the workflow-side program (tsconfig.workflows.json).
• The opt-in benchmark generates temporary inline workflow modules instead of YAML and times in-process workflow runs.

Validation

pnpm verify passes from codemods/solid-migration-assistant (Node v24.18.0, pnpm 11.20.0):

Suite	Result
architecture	7/7 pass
cli + packaging	13/13 pass
rules (per-rule jssg run)	28 adapters, 48 fixture cases, 0 targets changed
transform-rules	3 adapters, 29 fixture cases, 0 targets changed
workflow (exact output, cross-file semantics, missing bridge, failed command, SIGINT cancellation, artifact bundling, scripted command sequencing)	12/12 pass
transform (exact tree, idempotency, cwd default, usage failure)	3/3 pass
tsc --noEmit for both programs	clean
git diff --check	clean

The packaging test packs the tarball, extracts it by hand into a consumer's node_modules, links the orchestration prototype in, and runs the analyzer twice from that layout with pnpm off PATH.

Publication blocker

This version is not publishable, and this PR does not claim npm publish readiness.

• @codemod.com/orchestration is private: true and unpublished. The committed dependency is a relative link to a sibling checkout: "@codemod.com/orchestration": "link:../../../codemod/packages/orchestration" (the codemod monorepo on its prototype/typescript-orchestration branch, at 97a3695).
• The Rust execution bridge (butterflow-execution-bridge) is not distributed; the launcher resolves it from that checkout's target/debug/ or from CODEMOD_BRIDGE_BIN.
• A registry install cannot resolve the link: dependency, so npm install of the packed tarball fails. Both READMEs document this and the local setup steps.

Not in scope

• No changes to rule logic, guidance text, fixtures, or the per-rule jssg run tests.
• Nothing in the sibling codemod checkout is modified by this PR.

🤖 Generated with Claude Code