AWS Kiro: Process portability

IDE/CLI run the standalone agent harness locally rather than in the hosted Web/Mobile sandbox. This moves agent execution, not the entire Kiro service: its account, runtime and catalog/inference dependencies remain. Shared workflow recipes can run on supported clients. Exported specs alone are not evidence that the complete process can move. Whether the remaining services provide only inference or essential factory control is unresolved; local execution alone earns no portability level. Vendor documentation: Execution model ↗