Fix content script build and chrome.storage errors

[BitcoinErrorLog]

Summary

• Build content script as IIFE format instead of ES modules using separate Vite config
• Add chrome.storage availability check in logger to prevent errors in content scripts
• Update package.json build script to run both Vite builds

Problem

Content scripts were failing with:

1. "Cannot use import statement outside a module" - because content.js was built as ES module
2. "Cannot read properties of undefined (reading 'local')" - because the shared logger tried to access chrome.storage in content script context

Solution

• Created vite.content.config.ts to build content script as IIFE format
• Added isStorageAvailable check in logger before accessing chrome.storage.local
• Updated build script to run both builds sequentially

Test Plan

• Extension builds successfully
• Content script loads without errors
• Annotation button appears on text selection
• No chrome.storage errors in console

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Dev build no longer emits content script

The main Vite config now omits the content script from rollupOptions.input, but npm run dev (and any watch build using the default config) still relies solely on this file. Running the documented dev build now produces a dist without content.js, so the extension fails to load its content script when loaded in Chrome even though the manifest still references it.

Useful? React with 👍 / 👎.