Revisit the operator setup wizard

[erik-sutton95]

Revisit the first-pair / operator setup wizard. The 4-step BLE → Approve → Wi-Fi → datalink flow exists and is cloned from OpenZCine’s Pocket steps. It still reads as a prototype in a few places.

Related: Live-view FTUE · Finish Nano · roadmap index

What already exists

• Empty store → first-pair wizard; otherwise saved-camera home (CameraStartupPolicy)
• Steps 1–4 from ConnectionPhase.pocketWizardStep
• Two-column layout at width ≥ 640 (iPad / large phone landscape)
• Android pairing copy-matched (PairingExperience)
• Separate Operator Setup (SettingsRootView): Link / Sharing / View Assist / Controls / Display / Storage / System
• Sharing tab is still “Coming soon…”

Workstreams

1. Pairing copy and recovery

• Nano-specific copy (AVC, no AF, Approve on Nano, D-Log M)
• Failed step: retry this step vs start over; saved-camera “Wi-Fi didn’t join” is the painful one
• Do not mention sister apps or other camera brands in operator strings

2. After first live

• Optional post-pair checklist: LUT Auto, Face Priority, stick sensitivity, keep-awake
• Decide whether Sharing stays visible while every row is a stub

3. Saved-camera reconnect

• Wizard vs one-tap reconnect: first-pair chrome should not reappear for a camera we already know
• Persist hotspot copy: why the system Wi-Fi dialog looks different the second time

Out of scope

Replacing the live-view first-run overlay (that is the FTUE thread).

Done when

First pair, failed pair, and saved reconnect each have copy that matches the body (Pocket vs Nano) and do not dump the operator into a stub Sharing tab as if it were a feature.

[erik-sutton95]

Tracked as maintainer task #94.