nemo-relay-migrate-from-flow

# Migrate From NeMo Flow To NeMo Relay Use this skill when a user has existing NeMo Flow code or documentation and wants it converted to NeMo Relay. Treat the migration as a mechanical rename plus language-specific validation, not a behavior rewrite. Keep compatibility exceptions explicit before applying broad renames. ## Default Workflow 1. Inspect the working tree and identify touched surfaces: Rust, Python, Node.js, Go, C FFI, CLI/config, docs, or integrations. 2. Resolve `SKILL_DIR` to the absolute directory containing this `SKILL.md` and `TARGET_PATH` to the source repository or target project. Run the bundled helper in dry-run mode before editing: `python3 "$SKILL_DIR/scripts/migrate_from_nemo_flow.py" "$TARGET_PATH" --rename-paths` 3. Review the reported text edits, path renames, and legacy project configuration warnings with the user. Do not migrate project-local `.nemo-flow/config.toml` or `.nemo-flow/plugins.toml` into `.nemo-relay`. Move those settings manually to a supported user or explicit configuration path after review. 4. Obtain explicit confirmation for the resolved target root, then rerun with `--write`, `--rename-paths`, and `--confirm-root "$TARGET_PATH"`. 5. Apply language-specific cleanup for package manager lockfiles, generated artifacts, and public API examples. 6. Search for remaining Flow names and verify the affected language surfaces. ## Mechanical Rename Map - Brand and repository: `NeMo Flow` -> `NeMo Relay`, ...