Centralize repo and feed logic while polishing setup and themes

[jonmartin721]

Summary

This branch pulls a few related cleanup tracks into one pass so the extension behaves more consistently day to day.

• moves watched-repo parsing, validation, and normalization into shared helpers used by onboarding and settings
• adds a shared settings schema plus feed mutation/policy helpers so popup, options, and background logic stop re-implementing the same state rules
• expands theming with shared color-theme tokens, applies those themes across popup/options/onboarding, and refreshes the onboarding copy and icon treatment
• rounds out the popup and settings flows with archive clearing, snooze refresh cleanup, better repo input handling, and more focused tests around the new bootstrap and interaction paths
• refreshes the README so setup, permissions, repo limits, and day-to-day usage match the current extension behavior

Why

A lot of this code had started to drift into similar-but-not-quite-the-same implementations. Repo input handling lived in multiple places, settings defaults were scattered, and feed actions like marking read or clearing archive were split between UI code and background listeners. The result worked, but it made follow-up changes harder and raised the odds of onboarding, popup, and settings getting out of sync.

This pass tightens that up while also finishing the theme work so the extension looks and feels like one product instead of a few separate surfaces.

Testing

• npm test -- --runInBand
• npm run lint
• npm run typecheck

Notes

• This is a fairly wide branch, but the changes cluster around shared state/theme plumbing plus the UI surfaces that consume it.
• README screenshots were not regenerated in this branch, so the copy is fresher than the image set in a few spots.

[sentry]

Codecov Report

❌ Patch coverage is 73.45679% with 172 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
background.js	30.63%	77 Missing ⚠️
options/options.js	67.40%	44 Missing ⚠️
popup/views/onboarding-view.js	57.89%	16 Missing ⚠️
popup/popup.js	79.59%	10 Missing ⚠️
shared/repo-service.js	84.12%	10 Missing ⚠️
popup/controllers/repository-controller.js	77.41%	7 Missing ⚠️
shared/feed-presentation.js	94.11%	3 Missing ⚠️
options/controllers/token-controller.js	87.50%	2 Missing ⚠️
shared/state-manager.js	87.50%	2 Missing ⚠️
shared/storage-helpers.js	93.75%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive refactoring of the extension's architecture and a major UI overhaul. Key improvements include the centralization of state management, repository resolution, and feed policies into shared modules, alongside the implementation of a new theme system and Lucide-style icons. The update also enhances the onboarding experience and significantly expands the test suite. Review feedback correctly identified a critical bug in the settings persistence logic that could overwrite user data with defaults and highlighted the need for additional permissions to ensure reliable clipboard functionality in Manifest V3.

[gemini-code-assist]

The current implementation of updateSettings has a critical bug: it uses pickSyncSettings(updates), which internally calls normalizeSettings. This causes any keys missing from the updates object to be filled with default values, effectively overwriting the user's existing settings with defaults whenever a single setting is updated.

export async function updateSettings(updates) {
  const syncUpdates = {};

  if ('watchedRepos' in updates) {
    await setWatchedRepos(updates.watchedRepos);
  }

  if ('lastCheck' in updates) {
    syncUpdates.lastCheck = updates.lastCheck;
  }

  SETTINGS_SYNC_KEYS.forEach(key => {
    if (key in updates) {
      syncUpdates[key] = updates[key];
    }
  });

  if (Object.keys(syncUpdates).length > 0) {
    await new Promise((resolve, reject) => {
      if (typeof chrome === 'undefined' || !chrome.storage) {
        resolve();
        return;
      }
      chrome.storage.sync.set(syncUpdates, () => {
        if (chrome.runtime.lastError) {
          reject(new Error(chrome.runtime.lastError.message));
        } else {
          resolve();
        }
      });
    });
  }
}

References

1. When fixing specific bugs, defer larger, unrelated refactorings to a follow-up task to keep the pull request focused.

[gemini-code-assist]

Using navigator.clipboard.writeText within an asynchronous callback (like the device auth response) is unreliable in Chrome extensions without the clipboardWrite permission. In Manifest V3, clipboard access typically requires a recent user gesture; since this call happens after a network request, the gesture may have expired. It is recommended to add "clipboardWrite" to the permissions array in manifest.json to ensure this feature works consistently.

[jonmartin721]

Reviewed the current head commit 2722682.

The blocking settings persistence regression is fixed: partial updateSettings() calls no longer overwrite unrelated preferences with defaults, and there is now a regression test covering that behavior.

I do not have any remaining blocking code-review findings on the current diff.

Residual note: the PR is still marked as draft, so it still needs to be switched to ready for review before merge.