[Epic] Phase 2 — Git-native application delivery

Parent

#132

Outcome

Provide an end-to-end path from repository or container source to a running application: connect source, choose a build strategy, configure environment/domain/health, deploy through a durable queue, inspect live progress, create previews, and promote or roll back a release.

Product scope

• GitHub, GitLab, Bitbucket, Gitea, and generic Git/SSH connections.
• Dockerfile, buildpack-style detection, static output, prebuilt image, and multi-service Compose paths.
• Secure webhook-driven auto-deploy and branch/monorepo controls.
• Durable deployment history, cancellation, retry, concurrency, promotion, and rollback.
• Pull-request previews with stable URLs and automatic cleanup.

Existing work incorporated

• #117
• #118

Children

• #146
• #147
• #148
• #149
• #150
• #151

Exit criteria

A new user can deploy a representative server app, static site, serverless app, container image, and Compose stack without hand-editing generated state, while an expert can reproduce the same result through the CLI/API.

All Phase 2 children and incorporated work are complete except the live acceptance run in #117. The code path, safety guards, rollback, verification, tests, and cost model are shipped; #117 is currently blocked solely by expired local AWS credentials, with no live mutation attempted. This epic should remain open until the real CloudFront/Lambda verification is recorded.