Hyperpush deployment: define frontend plus meshable backend topology

[snowdamiz]

Parent epic

• Hyperpush: generic Docker-on-a-VM deployment baseline for frontend and meshable backend #23

Outcome

Define the actual product deployment topology: frontend container plus meshable backend cluster.

Current state

Current reconciliation evidence does not show this product row as shipped, but its project metadata is incomplete or too broad after the repo split, so the tracker scope needs rewrite/split before downstream execution.

Acceptance criteria

• Product topology is explicit
• Frontend and backend responsibilities are clear
• Cluster assumptions are documented
• The wording stays aligned with the current repo/code truth instead of relying on stale cross-repo or local-path assumptions.

Tracker context

• Labels: enhancement, roadmap
• Project-backed: yes