asm-migrationlisted

# ASM Migration Route each request to exactly one native tool: `asm_migration_validate`, `asm_migration_convert`, or `asm_migration_deploy`. The tool result is self-sufficient. Do not call `todo_write`, inspect inputs, generated artifacts, or implementation files, use shell/file/network tools, reproduce conversion logic, or use direct network tools. Deployment requests use only `asm_migration_deploy`. Do not load this skill again after it is already active. Validation requires an input type and path. Conversion requires a policy path, an `asm-migration.signatures/v1` mapping path, a namespace, and an output directory. Ask only for missing values and stop; never infer them from files, memory, nearby examples, or the working directory. Relative paths are resolved by the native tool against the xcsh working directory. Deployment plan requires an artifact directory and receipt path. Apply requires the receipt path, exact plan digest, and `APPLY <planDigest>` confirmation. Verify requires the receipt path. Cleanup requires the receipt path and `CLEANUP <planDigest>` confirmation. Credentials are never arguments and come only from the native tool environment. Default to strict conversion. Set `allowPartial` only when explicitly requested. Set `overwrite` only when explicitly requested. Never call the validator before or after conversion unless validation was the user's request. Refuse without calling any tool when a request requires source inspection, shell use, direct network