Make remote push the primary flow

[chruffins]

summary

• make hypeman push SOURCE TARGET the primary remote-registry flow
• wait for direct pushes by default; keep push create detached for compatibility and add --detach
• make structured formats return the final direct-push result unless detached
• render one live status line in terminals and plain newline status in CI/pipes
• validate source/target references and required target tags before creating jobs
• keep local Docker-daemon uploads via hypeman push local IMAGE [TARGET] plus the one-argument legacy form
• add --password-stdin, push ls, and push inspect

tests

• GOCACHE=/tmp/hypeman-go-build go test ./...

---

Note

Medium Risk
CLI contract changes (default remote vs local push) can break existing automation; registry credentials and push orchestration are sensitive though logic remains client-side.

Overview
hypeman push SOURCE TARGET is now the main way to export a cached Hypeman image to a remote registry. It blocks until the job finishes, polling status and showing Docker-style progress on stderr; --detach (and legacy push create) still queue and print the job ID only.

Local Docker → Hypeman uploads move to hypeman push local; a single argument on push still runs the old local upload for script compatibility. Local pushes gain stricter base-URL checks, optional HTTP/insecure registry parsing, byte progress, and digest/size output.

Remote pushes add --password-stdin, shared registry flags on the parent command, reference validation (target must have an explicit tag), and ls / inspect aliases for listing and inspecting jobs.

^{Reviewed by Cursor Bugbot for commit 6ce0768. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 0a20e7e. Configure here.}