Post-v0.2 roadmap: deployment breadth, CLI UX and product polish

[gODtECH-Ctl-Create]

Context

StackPilot v0.2.0 is publicly released with the core repository-engineering contract complete: inspect/readiness, safe remediation, security baseline, AWS ECS/Fargate deployment intelligence, and golden-path lifecycle upgrades.

This issue carries forward intentionally deferred breadth and polish. None of these items should weaken the deterministic/safety-first boundaries established in v0.2.

Deployment breadth

• Evaluate AWS App Runner and add it only where it is materially simpler than ECS/Fargate
• Add Azure Container Apps foundation with independent Terraform validation
• Add Google Cloud Run foundation with independent Terraform validation
• Define explicit production criteria before adding Kubernetes/EKS generation
• Keep network/credential/runtime operations outside StackPilot's long-running responsibilities

CLI UX

• Improve terminal presentation and progress feedback
• Improve validation/error messages
• Clearly distinguish recommended defaults from explicit overrides
• Add more actionable stackpilot doctor output
• Keep preview/apply boundaries obvious for fix and upgrade

Product documentation and proof

• Add real terminal recordings/demos
• Add generated examples for each golden path
• Expand public roadmap/changelog presentation where useful
• Keep website/release metadata automatically aligned with package versions

Lifecycle and readiness evolution

• Add future golden-path migrations only through explicit versioned steps
• Preserve application/business logic across lifecycle upgrades
• Introduce a future readiness model version only if scored controls materially change the published readiness-v1 contract

Guardrails

• Do not add languages/clouds/Kubernetes for feature count alone.
• Do not turn StackPilot into a hosted deployment control plane.
• Keep generic repository housekeeping in Steward.
• Keep cross-product orchestration/governance in FORGE.