migration-to-aws: bring power to parity with awslabs plugin

[ayn-builds]

Summary

Brings the Kiro migration-to-aws power up to parity with the upstream awslabs/startups/migrate/plugins/migration-to-aws plugin (Apache-2.0), which has moved ahead of the Kiro version.

Fork-only draft PR for review — nothing merged upstream to kirodotdev/powers yet.

What changed

Four scoped commits, all inside migration-to-aws/:

1. Restructure steering/ → references/ — 49 pure git mv renames flattening the single-directory layout into references/{phases,design-refs,clustering/terraform,shared}/ to match awslabs. No content changes; file history preserved.

2. Port 16 missing files from awslabs (verbatim, Apache-2.0):

   • design-refs/: ai-anthropic-to-bedrock.md, security.md, design-ref-harness.md, design-ref-agentic-to-agentcore.md
   • shared/: ai-migration-guardrails.md, ai-model-lifecycle.md, bedrock-quotas.md, handoff-gates.md, migration-complexity.md, pricing-fallback.md, retarget-gotchas.md, terraform-validation.md, validate-artifacts.md
   • phases/discover/discover-preview.md, phases/generate/generate-artifacts-report.md
   • data/sdk-capability-map.json

3. Rewrite POWER.md to mirror the upstream SKILL.md — adds context-loading budget rules, BigQuery specialist gate, hybrid-stack budget warning, fail-closed handoff-gate orchestration, "Clarify is mandatory" guardrail, 7-check state validation, read-merge-write phase-status protocol, and out-of-scope guardrails. Kiro-specific frontmatter, File Writing Protocol, Telemetry Disclosure, Integrations, and License sections preserved.

4. Update content of 43 of 49 moved files to match awslabs — refreshed pricing cache, richer AI merge logic in Discover, current_phase field, expanded design-refs and generate artifacts, updated schemas. Six files were already up to date (pure moves). Also replaced 3 stray SKILL.md references with POWER.md.

Attribution

Ported content is from https://github.com/awslabs/startups/tree/main/migrate/plugins/migration-to-aws under the Apache License 2.0. License header retained in POWER.md.

Review focus areas

• Frontmatter: POWER.md keeps Kiro schema (name, displayName, description, keywords, author) — description was expanded with the awslabs trigger phrases and out-of-scope guardrails. Verify field names still match Kiro's power schema.
• File paths: Every internal link now references references/... instead of steering/.... Grep-verified no stale steering/ or SKILL.md references remain.
• mcp.json: unchanged (already had both awsknowledge + awspricing, only whitespace diff from upstream).
• Not touching: everything outside migration-to-aws/ — no other powers modified.

Test plan

• Skim commit 1 diff in GitHub — confirm all 49 show as pure renames
• Spot-check 2-3 ported files in commit 2 against their awslabs sources
• Read the new POWER.md end-to-end for Kiro-format compatibility
• Sample-diff 2-3 of the updated files in commit 4 (e.g., discover.md, pricing-cache.md) to confirm expected drift
• Run the power in Kiro against a small GCP fixture (Terraform-only) and confirm phase transitions still work
• Confirm no broken links: grep -rn "steering/" migration-to-aws/ returns empty

[ayn-builds]

Addressed reviewer feedback that Kiro powers require a flat steering/ directory (nested folders don't load).

Two additive commits on this branch:

• df27337 flatten references/ back to steering/ — 65 files (git mv), pure renames. Uses original Kiro naming conventions:
  • design-refs/foo.md → steering/design-ref-foo.md
  • shared/pricing-cache.md → steering/cached-prices.md
  • clustering/terraform/classification-rules.md → steering/clustering-classification-rules.md
  • data/sdk-capability-map.json → steering/sdk-capability-map.json
• e533976 rewrite internal paths for flat steering layout — updates every internal references/… reference across all 65 files + POWER.md's file tree. Grep-verified no stale nested path fragments remain.

Everything else (content updates, new files, POWER.md body) is unchanged from the original review.

[ayn-builds]

Fixed Kiro reviewer's broken-reference findings in commit ee83be1.

All three categories addressed:

• pricing-cache.md → cached-prices.md (~20 sites across POWER.md and multiple steering files)
• artifact-validation.md → validate-artifacts.md (generate.md line 161)
• Short-form design-ref-* / clustering-* references without prefix — 13 filename patterns, applied globally using placeholder-swap so compound names like clarify-compute, design-ai, estimate-ai are not double-prefixed

Cross-checked with comm -23 — every .md substring in the corpus now resolves to an existing file in steering/, except two negative-instruction refs in discover.md (discovery-log.md, discovery-summary.md) which are correctly saying "do NOT create these".