[JJJ]

Summary

• Allow the internal onboardingVersion setting to use the validated save path invoked by Welcome and Settings.
• Save Welcome completion immediately rather than waiting for the usual settings debounce.
• Add a persistence test covering completion, relaunch, reopening, and invalid values.

Closes #378

Related to #3.

Validation

• npm run test:frontend
• npm run test:native

[Copilot]

🟢 Approval recommended

No active review issues block the Welcome completion persistence change.

No open issues 🎉

What changed in this PR

Fixes Welcome completion persistence across launches, addressing #378 while leaving the broader onboarding redesign in #3 out of scope.

Changes:

• Allows validated saves of the internal onboardingVersion setting.
• Saves Welcome state immediately instead of using the settings debounce.
• Adds a regression test for completion across restart, explicit reopening, and invalid-value rejection.

File	Description
src/​hooks/​useAppSettings.ts	Saves onboarding state without debounce.
src-tauri/​src/​settings_service.rs	Tests onboarding persistence, reopening, and validation.
shared/​settings-contract.json	Permits direct validated updates to onboardingVersion.

_{Review effort: Balanced}