[brylee123]

Chrontab’s worker mixed scheduling, persistence, and message handling, while source formatting and machine-specific browser tests made changes difficult to review. This refactor separates those responsibilities and makes the quality checks reproducible.

The scheduler now journals completed wakeup progress in session storage and schedules a recovery alarm after persistence failures. Normal worker suspension can resume that progress without reopening completed tabs. Any-group searches also check cheap assigned-date candidates before scanning broad date lists.

• Extract scheduler, runtime API, feedback, bootstrap, recurrence-dialog, and shared-limit modules.
• Add ESLint, Prettier, EditorConfig, and a pinned, read-only GitHub Actions workflow for Node 22/24 and Chromium browser checks.
• Replace machine-specific Playwright paths with a declared dependency, temporary profiles, browser discovery, and future calendar fixtures; run unit tests in a fixed DST-aware time zone.
• Generate runtime-only dependency notices and simplify static extension asset handling.
• Guard against stale editor loads and disable inactive work-hours fields.

Validation: frozen-lockfile install, pnpm check (lint, formatting, 39 tests, production build), and pnpm test:e2e (both real-browser flows) passed locally on Windows with Node 24 and Microsoft Edge. GitHub Actions also passed on the current PR head: quality checks on Node 22 and 24, plus both Chromium browser scenarios on Ubuntu.

The concurrent dashboard-formatting commit from main was incorporated after verifying equivalent content. The existing v1.1.0 release is unchanged. A process crash before journaling or a full browser restart during unavailable local storage can still replay a wakeup; the recovery guarantee and its limits are documented.