feat(toolbox): first-run lands on the Apps picker (not silent auto-apply) #25

SilverLABS · 2026-06-10T13:11:32Z

SilverLABS commented

2026-06-10 13:11:32 +00:00

Why

Hands-on VM testing of SP1: the install completed and BitLocker enrolled (verified — C: is -FVE-FS- encrypted, recovery key saved to EFI), but first-run auto-applied and skipped the Apps picker — the operator couldn't review/adjust apps before install ("jumped straight to the recovery-key/Done screen; couldn't select apps"). The whole app-recipes picker is wasted if it's never shown.

Change

First-run now lands on the Apps step, pre-checked with the collector flavour's defaults, then the user walks Apps → Prefs → Apply → Done. The collector already owns account + flavour, so Welcome/Flavour are skipped. (Reverses the earlier auto-apply behavior from brainstorm Q3, per operator feedback after seeing it live.)

Routes.razor SeedFromPreconfig: first-run sets _currentStep = 2 (Apps) instead of 4 + _autoApply. Apply waits for the user (its existing Start button). Pre-seeding (flavour, app defaults, BitLocker PIN) and the configured-marker/toolbox-home logic are unchanged.

Test Plan

dotnet test windows/welcome/SilverOS.Welcome.sln -c Release → 31/31
dotnet build …App -c Release → 0 errors
VM: collector → install → first logon opens on Apps (flavour defaults checked) → adjust → Apply → Done

🤖 Generated with Claude Code

## Why Hands-on VM testing of SP1: the install completed and BitLocker enrolled (verified — C: is `-FVE-FS-` encrypted, recovery key saved to EFI), but first-run **auto-applied and skipped the Apps picker** — the operator couldn't review/adjust apps before install ("jumped straight to the recovery-key/Done screen; couldn't select apps"). The whole app-recipes picker is wasted if it's never shown. ## Change First-run now lands on the **Apps step**, pre-checked with the collector flavour's defaults, then the user walks **Apps → Prefs → Apply → Done**. The collector already owns account + flavour, so Welcome/Flavour are skipped. (Reverses the earlier auto-apply behavior from brainstorm Q3, per operator feedback after seeing it live.) `Routes.razor` `SeedFromPreconfig`: first-run sets `_currentStep = 2` (Apps) instead of `4` + `_autoApply`. Apply waits for the user (its existing Start button). Pre-seeding (flavour, app defaults, BitLocker PIN) and the configured-marker/toolbox-home logic are unchanged. ## Test Plan - [x] `dotnet test windows/welcome/SilverOS.Welcome.sln -c Release` → **31/31** - [x] `dotnet build …App -c Release` → 0 errors - [ ] VM: collector → install → first logon opens on Apps (flavour defaults checked) → adjust → Apply → Done 🤖 Generated with [Claude Code](https://claude.com/claude-code)

SilverLABS added 1 commit 2026-06-10 13:11:32 +00:00

feat(toolbox): first-run lands on the Apps picker (not silent auto-apply)

Build SilverMetal Enhanced - Windows ISO / build (pull_request) Failing after 6m14s

Details

18475fa731

Hands-on VM testing showed auto-apply skipped the app picker entirely -- the user
couldn't review/adjust apps before install. Land first-run on the Apps step instead
(pre-checked with the collector flavour's defaults); the user adjusts then walks
Apps -> Prefs -> Apply -> Done. The collector already owns account + flavour, so
Welcome/Flavour are skipped. Reverses the earlier auto-apply behavior per operator
feedback.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

SilverLABS merged commit 75f97778f8 into main

2026-06-10 13:11:42 +00:00

SilverLABS deleted branch fix/first-run-apps-picker

2026-06-10 13:11:42 +00:00

SilverLABS referenced this issue from a commit

2026-06-10 13:11:44 +00:00

Merge pull request 'feat(toolbox): first-run lands on the Apps picker (not silent auto-apply)' (#25) from fix/first-run-apps-picker into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SilverLABS/SilverMetal#25