No fast CLI to reproduce CI failures locally without pushing commits and waiting for cloud builds

Developers burn 30-minute CI cycles to test one-line changes because local and CI environments diverge. The classic 'it works on my machine' problem is still unsolved for most teams in 2026. A January 2026 Ask HN thread on 'what developer tool do you wish existed' listed local CI parity as a top request, with multiple commenters describing the YAML trial-and-error cycle. DEV Community articles in 2026 document the '2-minute inner loop' as the holy grail of local dev. Tilt and Skaffold exist for Kubernetes-heavy stacks; no general-purpose CLI that mirrors a CI job locally across arbitrary runners (GitHub Actions, CircleCI, GitLab).