{"id":87498,"plugin_id":"plugin_asdk_app_6a8f6c526c5481918eb8a48806fa112b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T18:08:05.820Z","digest":"1e4f48d3ad778991be1925cb25faa8d38321b36ac2d3d52b9cb51c57d12347a1","against":null,"payload":{"description":"Plan and implement an explicitly requested Lumen version upgrade, including version-specific migration diagnostics and consumer verification. Use when updating an application's Lumen dependencies or replacing older Lumen contracts.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":217},{"relative_path":"references/v4.md","size_in_bytes":1114},{"relative_path":"references/v5.md","size_in_bytes":2299}],"name":"lumen-migrate","skill_md_contents":"---\nname: lumen-migrate\ndescription: Plan and implement an explicitly requested Lumen version upgrade, including version-specific migration diagnostics and consumer verification. Use when updating an application's Lumen dependencies or replacing older Lumen contracts.\n---\n\n# Migrate a Lumen consumer\n\nResolve the installed versions from package metadata and lock files, the requested target, the\nframework/platform, and the application's integration boundaries. Preserve existing user changes.\nDo not infer an upgrade request from ordinary UI work or pick a newer major than the user requested.\n\nCompare target contracts with MCP metadata using `lumen_check_compatibility`. A latest catalog is\nnot the installed API. For another version, use a matching published MCP package or installed public\ntypes and release documentation. Verify target publication independently of workspace package metadata.\n\nRead the migration guide and release notes for the requested source and target versions. Determine\nwhich preview/apply commands the target CLI actually supports; do not assume every major has the\nsame automation. Read [references/v4.md](references/v4.md) for Lumen 4 or\n[references/v5.md](references/v5.md) for Lumen 5. When MCP\nis connected, read the migration contract without a package filter before narrowing to affected\npackages so cross-package changes are not missed. If shell execution is unavailable, inspect a\nsupplied target-CLI preview and report remaining commands as unverified.\n\nApply only the reviewed migration scope. Use `--apply` for supported deterministic edits; inspect\ntheir diff. Use the target release manifest for individual package pins and update the lock file with the\nconsumer's package manager. V5 companions can remain on v4; never assign one version to the family.\nReview the changed public contracts and affected consumer workarounds. Keep ambiguous expressions\nand application-owned policy for explicit review.\nNever remove a workaround until the equivalent target behavior is verified. For changed setup,\nread only the matching target from [framework contracts](../lumen-ui/references/frameworks.md).\n\nRun the consumer's relevant types, tests, lint, build, and rendered interaction checks. Include\nphone/desktop and keyboard/focus for web changes; use native compilation and accessibility checks\nfor native adapters. Re-run the supported preview to establish idempotence. Read\n[the interaction checklist](../lumen-ui/references/verification.md) for affected UI behavior.\nReport remaining manual findings and local versus published/deployed evidence accurately.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}