spectre-migrate

You need to be in a root directory of the service being migrated, and have `spectre` CLI tool available. # Migrate the next node - If there is no state.toml yet, Plan the migration with the `spectre-plan` skill. - Pick a node that is `pending` and whose `depends_on` are all `migrated`. Prefer libraries and egress clients, which other nodes need first. - Implement the node in the candidate so it behaves exactly like the reference, including errors and the dependency calls it makes. Match behaviour, not code. - Add or update the comparison scripts for its routes and dependency calls with the `spectre-schema` skill. - Set the node's `status` to `"migrated"` in `spectre/state.toml`, changing only that line, and run `spectre state validate`. - Commit the candidate change and the state change together, so the mirror only compares routes the candidate implements. When the mirror reports a difference or quarantines the candidate, fix the candidate, not the reference. Normalise a difference only when it does not matter to clients. Use any environment specific `spectre-migration-<env>` skills if avialable.