Hyperpush core parity: audit and harden existing Mesher ingestion and project/event model

[snowdamiz]

Parent issue

• Hyperpush: core parity for ingestion, grouping, regression, alerts, ownership, and environments #13

Outcome

Audit and harden the existing Mesher ingestion and project/event model so the operator app and future SDK parity work build on something stable and truthful.

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; repo/surface wording should also normalize to the canonical public hyperpush ownership truth. Public repo truth should read hyperpush-org/hyperpush even though local workspace evidence still references local compatibility path mesher -> ../hyperpush-mono/mesher; workspace helper canonicalizes both hyperpush and hyperpush-mono to workspace root hyperpush-mono.

Acceptance criteria

• The current Mesher ingestion and project/event model are audited against the operator app and SDK needs
• Gaps in the current shape are identified and closed or explicitly deferred
• The model is stable enough to support the next wave of app integration work
• 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