Hyperpush deployment: add a production Dockerfile and container startup path for the operator app #55

Parent issue

• Hyperpush deployment: ship generic Docker VM reference deployment and cluster health verification #50

Outcome

Give the operator app a real production container path instead of relying on local-only dev assumptions.

Current state

Current reconciliation evidence does not show this product row as already shipped, so it should stay open until implementation proof exists; repo/surface wording should also normalize to the canonical public hyperpush ownership truth. Public issue wording should refer to hyperpush-org/hyperpush; local hyperpush-mono compatibility paths remain supporting workspace context only.

Acceptance criteria

• frontend-exp has a production Dockerfile or equivalent container build path
• Container startup contract is explicit
• The app can run as a real service in the generic VM deployment model
• The wording stays aligned with the current repo/code truth instead of relying on stale cross-repo or local-path assumptions.

Tracker context

• Public repo: hyperpush-org/hyperpush
• Workspace compatibility path: mesher -> ../hyperpush-mono/mesher