Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/renderer/App.tsx`:
- Line 203: The AnnouncementsModal component was commented out in App.tsx (the
line with {/* <AnnouncementsModal /> */}) which disables announcements for all
users; restore the normal product behavior by re-enabling the
<AnnouncementsModal /> render inside the App component, and if you must avoid it
during automated tests, add a clear, explicit runtime guard (e.g., an isE2ETest
/ process.env.E2E flag or a window.__PLAYWRIGHT__ check) around the
<AnnouncementsModal /> render so it only skips in test runs—do not leave it
commented out globally and prefer handling test-specific suppression from
Playwright or an e2e-only flag.

In `@test/playwright/smoke-screens.spec.ts`:
- Around line 10-16: The login helper currently hard-codes credentials in the
login(page: Page) function; change it to read email and password from
environment variables (e.g., process.env.E2E_ADMIN_EMAIL and
process.env.E2E_ADMIN_PASSWORD), validate they are defined and throw a clear
error (fail fast) if missing, then use those variables in the calls to
page.getByPlaceholder('Email Address').fill(...) and
page.getByPlaceholder('Password').fill(...) before clicking the Sign In button;
this removes secrets from source and makes CI configurable.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/renderer/components/Shared/AnnouncementBanner.tsx`:
- Around line 180-188: The IconButton in AnnouncementBanner.tsx that calls
handleDismiss is icon-only and lacks an accessible name; update the IconButton
(the one rendering XIcon and using onClick={handleDismiss}) to provide an
accessible label by adding an aria-label (e.g., aria-label="Dismiss
announcement") or aria-labelledby pointing to visible/visually-hidden text, or a
title prop as fallback, so screen readers can announce the button's purpose
while preserving current styling and behavior.
- Around line 16-19: The issue is that parseLocalDate returns a Date at midnight
so comparisons against now make same-day expiries effective at 00:00; change
parseLocalDate(dateString: string) to produce the end of that local day (e.g.,
new Date(year, month - 1, day, 23, 59, 59, 999)) so that checks in the
AnnouncementBanner logic (places where parseLocalDate() is compared to now in
the component) treat the entire expiry day as valid; update the single
parseLocalDate function (used by the expiry checks) accordingly so all
comparisons (the existing comparisons that currently use parseLocalDate) behave
correctly.
- Around line 54-57: The effect calls API_URL() but doesn't list it as a
dependency, so extract the result of API_URL() to a component-level constant
(e.g., const apiUrl = API_URL()) and update the useEffect to depend on apiUrl
and hasChecked; change the early-return to use apiUrl (if (!apiUrl ||
hasChecked) return) and ensure any logic that previously called API_URL() inside
the effect now uses apiUrl so the effect re-runs when API_URL transitions from
null to a value.
- Around line 23-25: Remove the unnecessary any casts around window.storage in
getStoredDate (and any other uses of (window as any).storage) and use the
globally declared StorageAPI type directly (e.g., reference
window.storage.get/localStorageKey) to restore type-safety; also define a typed
interface for the announcement API response (e.g., IAnnouncementResponse) and
replace untyped accesses to result.data with the typed shape when parsing the
fetch result in the component (the code path that reads result.data), ensuring
you validate/guard optional fields before use.

---

Nitpick comments:
In `@src/renderer/components/Shared/AnnouncementBanner.tsx`:
- Around line 16-19: Add unit tests covering the new date utility and the
announcement selection logic: write tests for parseLocalDate (verify correct
Date for various YYYY-MM-DD inputs, invalid strings, and timezone neutrality)
and for the announcement selection flow in the hook that decides expired vs
unseen vs latest (exercise cases where announcements are expired, already seen,
unseen, and where multiple candidates exist to ensure the hook returns the
correct announcement). Target the exported utility parseLocalDate and the
hook/function responsible for selection (the selection logic within lines
~54-145) and include edge cases (empty lists, all expired, duplicate timestamps)
to satisfy the "utility functions and complex hooks" guideline.