Hyperpush app backend: define the bridge from the current Mesher contract to real app auth, session, and project selection

[snowdamiz]

Parent issue

• Hyperpush app: replace mocked operator screens with real data and workflows #34

Outcome

Define the bridge from the current Mesher project-scoped backend contract to the real multi-project operator app: auth, session, project selection, and the operator-facing API boundary.

Current state

Partial only; real backend/data workflows for the operator app remain open. Public repo truth should read hyperpush-org/hyperpush even though local workspace evidence still references mesher/frontend-exp/lib/mock-data.ts via the compatibility symlink into the sibling product repo. This issue remains active follow-through because the current operator surfaces are still partially mock-backed rather than fully shipped.

Acceptance criteria

• The bridge from current Mesher backend assumptions to the real operator app contract is explicit
• Auth/session/project-selection expectations are defined truthfully
• The app/backend boundary is stable enough that the rest of the app integration work is not guessing
• The wording stays aligned with the current repo/code truth instead of relying on stale cross-repo or local-path assumptions.
• The issue does not treat the current mock-backed operator surfaces as already shipped.

Tracker context

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