fix(onboarding): relaunch MainActivity after onboarding finishes

[0xbrayo]

MainActivity.onCreate starts OnboardingActivity and then calls finish() on itself. When the user grants Usage Access during onboarding and taps FINISH, OnboardingActivity only called finish(), leaving nothing on the back stack: the user lands on the launcher and no BackgroundService (aw-server-rust, sync scheduler) starts until the app is opened a second time.

This starts MainActivity explicitly before finishing onboarding so the normal startup path runs right away.

Fixes #170.

Validation: :mobile:compileStandardDebugKotlin passes. Not yet exercised on a device.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the new launch follows the existing onboarding state and permission checks and restores the intended startup flow.

Summary

This PR fixes onboarding completion by explicitly relaunching MainActivity after recording completion, allowing the normal service and scheduler startup path to run immediately.

• Starts MainActivity after the user grants usage access and finishes onboarding.
• Preserves the existing permission gate and first-run preference update.
• Closes OnboardingActivity after initiating the replacement activity.

Diagram

sequenceDiagram
    participant U as User
    participant O as OnboardingActivity
    participant P as AWPreferences
    participant M as MainActivity
    participant B as BackgroundService

    U->>O: Tap FINISH
    O->>O: Verify usage access
    O->>P: Clear first-run flag
    O->>M: startActivity(MainActivity)
    O->>O: finish()
    M->>M: Run normal startup path
    M->>B: Start foreground service

Loading

_{Reviews (1) · Last reviewed commit: "fix(onboarding): relaunch MainActivity a..."}

[ErikBjare]

@0xbrayo ready?

[0xbrayo]

Tested on device, ready to merge 👍🏼