Hyperpush deployment: create generic-VM compose stack and health verification for the marketing site, operator app, and product backend #56

Parent issue

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

Outcome

Create the reference generic-VM deployment stack and a health verification flow for the marketing site, operator app, and product backend together.

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

• A repeatable generic-VM stack exists
• Health/readiness verification exists for the deployed surfaces
• The stack reflects the real product topology rather than a mock/demo shortcut
• 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