ips-migration

IP-Symcon subtree migration

Migrate an IP-Symcon object subtree from a source instance to a target instance: carry structure, logic and module instances across, and rewire every ID reference so the copy actually works on the new system. This is the agentic counterpart to the deterministic ips_export_subtree / ips_import_subtree primitives — it orchestrates them, then does the reasoning the primitives deliberately don't (instances, references, flagging).

REQUIRED BACKGROUND: the ipsymcon skill — same MCP, same plan-before-you-touch rule, and the same optional instance parameter on every tool (read from source, write to target). This skill is migration-specific orchestration layered on top of it.

What it does — and deliberately does not (v1)

Does: greenfield migration (target empty/fresh) — recreate categories, variables, scripts, events, links and instances under a target parent, and remap every ID reference (script object IDs, link targets, event triggers, instance configuration) through one old→new id_map. Plan-first, write-gated, verified by re-export.

Does not:

• Semantic matching onto objects that already exist on the target (matching an old MQTT instance to an existing one) — that is a later skill. v1 assumes greenfield.
• Evaluation / refactoring of the config — also a later skill. v1 only flags smells; it never "improves" anything silently.
• Install modules on the target — it checks that required modules are present and flags the missing ones (a missing module blocks its instances).

Faithful-but-flagged, not blind 1:1. v1 transports correctly and surfaces what looks wrong; deciding what to fix is the human's (or the later refactoring skill's) call.

Core shape

read (source)  →  plan + flag (NO writes)  →  approve  →  two-pass write  →  verify
                                                          (1: create all
                                                           2: wire references)