Kiro Crew One-Click Deploy (MVP)

Shipped by Kiro Crew core (src/kiro_crew/deploy/), not by an installable app. Gateway startup copies this skill into ~/.kiro/crew/skills/artifact-deploy/. The /deploy console owns AWS profile setup, verification, pending confirmations, and the fleet/cost view; this skill prepares and previews deployments.

AWS config -- resolve the profile from the core registry, don't ask

The Artifact Deploy core module owns the AWS configuration as a multi-profile registry at ~/.kiro/crew/deploy/profiles.json ({"profiles": [{"name", "region", ...}], "default": "<name>"}). Resolve the deploy profile in this order, before asking the user anything:

1. User picked one: if the deploy request names a profile (the artifact card's dropdown injects Use the AWS profile "<name>".), use that entry's name/region from the registry. If the name is not in the registry, stop and send the user to the /deploy console to register it -- never deploy with an unregistered profile name.
2. Registry default: otherwise use the entry named by default.
3. Legacy fallback: if the core registry doesn't exist, read the old ~/.kiro/crew/apps/deploy-web/data/profiles.json, then its sibling config.json ({"profile", "region"}).
4. Unconfigured (no registry, no legacy profile): do NOT walk the user through manual profile setup in chat -- link them to the /deploy console (Artifacts -> Artifact Deploy), which has the Profiles control plane (register / create + Verify access + IAM policy generator). Resume once a profile exists.

After a successful deploy, back-fill webapp_metadata.deploy_target.profile with the profile NAME actually used, so the fleet table and the artifact's control card show which identity owns the deployment.