migrate-skaile-manifest

To migrate a legacy skaile.yaml manifest, provide the file path and a publisher map, then run the conversion to rewrite repositories, ai_resources, and dependencies into canonical sources, pins, and refs with publisher resolution.

Converting ai_resources to canonical sources involves transforming arrays or objects into sources entries and top-level dependencies, inferring the publisher, and rewriting dependency refs to the canonical kind:name@publisher[#pin] form.

Yes, you can preview skaile.yaml migration changes safely by using the dry-run mode, which generates a canonical-identity manifest preview without modifying the original legacy file.

Yes, the skaile.yaml migration preserves unknown keys in the manifest to maintain compatibility, ensuring that fields outside repositories, ai_resources, and dependencies remain intact during canonical-identity conversion.

The best way to resolve publishers when rewriting dependency refs is to use a publisher map, which rebrands the @skaile namespace to @skaile-ai as needed and applies canonical kind:name@publisher[#pin] formatting.

Yes, you need the ruamel.yaml dependency to parse and rewrite legacy manifests, as the conversion process relies on it to safely transform skaile.yaml files into the canonical-identity shape.