- Test renders three buttons: Light, Dark, System
- Test default state is System when localStorage is empty
- Test clicking Dark adds .dark class to documentElement
- Test clicking Light removes .dark class from documentElement
- Test clicking Dark writes to localStorage key r2b-theme
- Test active/inactive aria-pressed state
- Test group has aria-label="Theme"
- Add @custom-variant dark directive for .dark class-based toggling
- Define 15 CSS custom property token pairs (light/dark) in @layer base
- Map all tokens to Tailwind utility classes via @theme with var() references
- Include warning/success tokens (amber + green) for ReviewStep coverage
- Add body transition with prefers-reduced-motion guard
- Add inline blocking script in index.html head to prevent FOUC
- AzureAuthToggle reads sas_url/key tooltipText from BACKEND_REGISTRY and passes to PasswordField
- SftpAuthToggle adds showAuthTip state with ⓘ button above segmented control
- All 159 tests pass including UX-01 tooltip toggle tests
- Populate tooltipText for azureblob.sas_url, azureblob.key, and onedrive.token in registry
- Add tooltipText prop and showTooltip state to PasswordField with toggle button + panel
- Add showTooltip state to FieldRenderer; pass tooltipText to PasswordField for password branch
- Add ⓘ button + panel for text/select branches in FieldRenderer
- Use sr-only span for accessible name to avoid getByLabelText collision
- Replace simple ternary assignment with let schema pattern
- Chain (schema as z.ZodString).regex() when field.validate is present
- Handle optional fields: z.string() first, then .regex() if needed, then .optional()
- VALID-01 tests all pass (GREEN): azureblob account, s3 region, gcs project_number
- Add SftpAuthToggle import
- Extend backendLabel record to cover onedrive/sftp/gcs/b2
- Add sftp branch with host/user FieldRenderers + SftpAuthToggle
- onedrive/gcs/b2 render via existing registry loop (no custom branch)
- Full Vitest suite green (147 tests); zero TypeScript errors
- Password and Private Key tabs using CSS-hidden segmented control
- Both pass and key_pem fields always registered with react-hook-form
- Password tab active by default (authMethod = 'password')
- Active tab: bg-blue-600 text-white; inactive: bg-white text-gray-700 hover:bg-gray-50
- Wired into RemoteConfigStep in Plan 03 (06-03-PLAN.md)
- Create 06-00-SUMMARY.md with RED state confirmation (27 failing, 49 green)
- Update STATE.md: progress 88%, decisions, session info
- Update ROADMAP.md: phase 6 in progress (1/4 summaries)
- Mark BACK-01 through BACK-04 complete in REQUIREMENTS.md
- EXPECTED_BACKENDS now includes onedrive, sftp, gcs, b2 (7 total)
- Added describe blocks for OneDrive, SFTP, GCS, Backblaze B2 field assertions
- 9 tests fail RED because registry.ts still has only 3 BackendType values
Re-ran npx vitest run: 12/12 suites pass, 104/104 tests pass, zero act() warnings.
The Vitest v4 runner-initialization failure in the initial verification report was
specific to the verifier agent context and does not reproduce in developer environment.
No code changes needed. Phase 5 is fully complete (15/15 must-haves verified).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add afterEach to vitest imports
- Add vi.useFakeTimers() at the start of beforeEach block
- Add afterEach(() => vi.useRealTimers()) to restore timers after each test
- Freezes OutputBlock's setTimeout(setCopied(false), 2000) during tests
- Replace fireEvent import with userEvent from @testing-library/user-event
- Add const user = userEvent.setup() inside each test body using interactions
- Replace fireEvent.click(azureButton) with await user.click(azureButton)
- Replace fireEvent.change(nameInput) with await user.clear() + await user.type()
- Make all interaction tests async
kawa
