Address coderabbitai review feedback: add Safari distribution artifacts, cross-references, remove specific file sizes, update AI provider list, and improve consistency

Co-authored-by: PeterDaveHello <[email protected]>

Author: Copilot

.github/copilot-instructions.md

@@ -11,6 +11,7 @@ Always reference these instructions first and fall back to search or bash comman
 - Install dependencies: `npm ci` -- npm audit warnings may appear; for development-only dependencies they generally do not affect the shipped extension. Review and address runtime-impacting advisories separately.
 - Development build: `npm run dev` -- runs webpack in watch mode. Do not kill mid-compilation, but stop gracefully when switching branches or after dependency/config changes, then restart to avoid stale watchers and inconsistent state.
 - Production build: `npm run build` -- Avoid force-killing mid-bundle; stop, fix, then rebuild.
+  See "Time Expectations" and "Build Issues" for the hung-build policy and recovery steps.
 - Format code: `npm run pretty` -- uses Prettier to format all JS/JSX/CSS files. Run this before linting.
 - Lint code: `npm run lint` -- uses ESLint.
 - Safari build: `npm run build:safari` -- macOS with Xcode required.
@@ -26,6 +27,7 @@ Production build creates multiple variants in `build/` directory:
 - Distribution artifacts:
   - Chromium: `build/chromium-*.zip` (e.g., `build/chromium-<version>.zip`)
   - Firefox: `build/firefox-*.xpi` (e.g., `build/firefox-<version>.xpi`)
+  - Safari: `Fission - ChatBox.app` and `safari.dmg` (see Safari Build section for details)
 
 ## Architecture Overview
 
@@ -41,7 +43,7 @@ Production build creates multiple variants in `build/` directory:
 ### Manifests
 
 - `src/manifest.json` - Manifest v3 for Chromium browsers (Chrome, Edge, Opera, etc.)
-- `src/manifest.v2.json` - Manifest v2 for Firefox
+- `src/manifest.v2.json` - Manifest v2 for Firefox (current status; future MV3 migration may change this)
   - Background runs as service worker (MV3) vs background page (MV2)
   - Different permission models between manifest versions
 
@@ -79,15 +81,17 @@ Since this is a browser extension with no automated tests, ALWAYS manually test
 
 Ensure these files exist in `build/chromium/` after successful build:
 
-- `manifest.json` (~2.4KB, contains proper extension metadata)
-- `background.js` (~427KB, service worker)
-- `content-script.js` (~1MB, main functionality)
-- `content-script.css` (~650KB, styling)
+- `manifest.json` (contains proper extension metadata)
+- `background.js` (service worker bundle)
+- `content-script.js` (main functionality)
+- `content-script.css` (styling)
 - `popup.html` and `popup.js` (popup interface)
 - `IndependentPanel.html` and `IndependentPanel.js` (standalone chat page)
-- `shared.js` (typically around ~2MB; size may vary slightly by environment and dependencies)
-- `logo.png` (~18KB, extension icon)
-- `rules.json` (~1.4KB, declarative net request rules)
+- `shared.js` (shared vendor/runtime; size varies by environment and dependencies)
+- `logo.png` (extension icon)
+- `rules.json` (declarative net request rules)
+
+Bundle sizes are approximate and not validation criteria.
 
 ### Verify Script Limitations
 
@@ -154,9 +158,9 @@ src/
 
 The extension supports multiple AI providers:
 
-- **Web APIs** (free): ChatGPT, Claude, Kimi Moonshot (requires browser cookies)
-- **API Keys**: OpenAI GPT models, Claude API, OpenRouter, AI/ML, DeepSeek, Ollama
-- **Custom models**: Support for self-hosted and alternative API endpoints
+- **Web (cookie-based)**: ChatGPT (Web), Claude.ai (Web), Kimi.Moonshot (Web), Bing (Web), Gemini (Web)
+- **APIs (key-based)**: OpenAI (API), Azure OpenAI (API), Claude.ai (API), OpenRouter (API), AI/ML (API), DeepSeek (API), Ollama (local), ChatGLM (API), Waylaidwanderer (API), Kimi.Moonshot (API)
+- **Custom/self-hosted**: Alternative endpoints and self-hosted backends
 
 ## Troubleshooting
 
@@ -183,11 +187,11 @@ The extension supports multiple AI providers:
 
 - Do not interrupt builds or long-running commands unless they appear hung or unresponsive.
 - `npm ci`: ~30 seconds
-- `npm run build`: ~33 seconds (measured). Set timeout to 5–10 minutes to allow for slowdowns; if it exceeds this window and appears hung, use troubleshooting steps from Build Issues section.
+- `npm run build`: ~33 seconds (measured). Set timeout to 5–10 minutes; if it exceeds this and appears hung, see "Build Issues" for recovery steps.
 - `npm run dev`: ~13 seconds initial build, then watches for changes; use Ctrl+C to stop when switching branches or after config/dependency changes.
 - `npm run lint`: ~3–5 seconds
-- Manual extension testing: 5-10 minutes for thorough validation
-- Safari build: 2-5 minutes (macOS only)
+- Manual extension testing: 5–10 minutes for thorough validation
+- Safari build: 2–5 minutes (macOS only)
 
 ## Critical Validation Steps