## 1. Screen synchronization policy

- [x] 1.1 [frontend] Change the screen-sync status polling policy from one
  second to five seconds while keeping the existing `useScreenSync` interface
  and terminal-state resource observation.
  - **Covers:** `frontend-data-resilience` — `Временные сбои чтения восстанавливаются автоматически`
  - **Verification:** Run the colocated screen-sync test file and confirm its
    MSW assertions show no subsequent status or observe request before five
    seconds, with resources observed on a terminal status response.

- [x] 1.2 [frontend] Update colocated screen-sync tests with fake timers to
  cover the five-second running cadence, immediate terminal observation, and
  existing stop-on-unmount behavior.
  - **Covers:** `frontend-data-resilience` — `Временные сбои чтения восстанавливаются автоматически`
  - **Verification:** `nvm use --silent && npm test -- screen-sync.test.tsx`

## 2. Frontend delivery

- [x] 2.1 [frontend] Run the frontend's canonical verification after the
  polling-policy and regression-test changes.
  - **Covers:** `N/A` — This task verifies the affected frontend delivery; it
    introduces no separate observable behavior beyond the requirement covered
    by tasks 1.1 and 1.2.
  - **Verification:** `nvm use --silent && npm run verify`

- [x] 2.2 [specs] Verify the completed OpenSpec change against the
  `wealth-ledger-specs` store before implementation review.
  - **Covers:** `N/A` — This task validates the planning artifacts and their
    traceability; it does not introduce runtime behavior.
  - **Verification:** `openspec validate --change reduce-screen-sync-polling --store wealth-ledger-specs`