research(mobile): validate native mobile vs PWA for maintainer digests

[JSONbored]

Background

A native mobile app may be useful later for digests and alerts, but contribution work is desktop-heavy. We should validate before building.

Goal

Research whether native mobile is worth building versus a PWA for maintainer digests and operator checks.

Current Behavior

Mobile is an idea, not a validated requirement.

Desired Behavior

The project has a clear recommendation on native mobile timing and scope.

Implementation Requirements

• Define likely mobile use cases.
• Compare PWA vs native app tradeoffs.
• Identify notification/privacy constraints.
• Estimate maintenance cost.
• Recommend defer/build/prototype decision.

Public/Private Output Boundaries

Public GitHub output must never include wallets, hotkeys, payout/reward estimates, raw trust scores, public score estimates, private reviewability, private scoreability context, or farming language. Private API/MCP/control-panel surfaces may show authenticated scoreability, blockers, projections, and evidence, but must not claim guaranteed payout outcomes.

Acceptance Criteria

• Defines mobile use cases: digest, alerts, install health, review queue.
• Compares PWA vs native app.
• Recommends whether to defer native.
• No implementation required.

Testing Requirements

• npm run test:ci must pass.
• Global coverage must remain at or above 97% for lines, statements, functions, and branches.
• Aim for 98%+ branch coverage locally.
• Add tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, scoring, source-upload safety, public/private boundaries, or telemetry privacy.
• MCP/local tooling must prove source contents are not uploaded when local metadata is involved.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.