One-time IP validation on myipaddress.biglove.ai — simplified proxy UX

Summary
The extension no longer runs periodic proxy monitoring or shows a proxyMonitoring toggle. Instead, it performs a single IP validation when a tab loads the IP-check page (https://myipaddress.biglove.ai/). The content script scrapes the IP from <span id="MyIpAddress">, the background compares it once to proxy IPs stored in Airtable, and the result is shown in the floating bar.

Why
- Remove dependency on another addon and background intervals.
- Reduce background/network activity and surface area.
- Provide a nicer default visual (NO_CONFIG) and persistent status per container.

Key user-visible changes
- One-time check on https://myipaddress.biglove.ai/ only (no periodic intervals).
- Default startup status: NO_CONFIG (yellow loading dot).
- Floating bar hidden for non-container (Default) tabs; shown only for real container tabs.
- Last validated status is persisted per-container and shown on other pages (so status does not flip-flop).
- A new "Check Proxy" globe button (🌐) in the floating bar opens https://myipaddress.biglove.ai/ in the current tab.
- Statuses available: CONNECTED, MISMATCH, NO_PROXY, NO_CONFIG, ERROR.

One-time IP validation on myipaddress.biglove.ai — proxyMonitoring removed
Summary
The extension no longer runs periodic proxy monitoring or exposes a proxyMonitoring toggle. Instead, it performs a single IP validation when a tab finishes loading the IP-check page (https://myipaddress.biglove.ai/). The content script scrapes the IP from <span id="MyIpAddress"> and the background script compares it once against proxy IPs stored in Airtable. The floating bar defaults to a NO_CONFIG state on first run and is shown only for non-default Firefox containers.

🔧 Default Proxy Monitoring Disabled
Summary
Proxy status monitoring is now disabled by default across all components. Users must explicitly enable "Enable Proxy Status Monitoring" in the popup settings to activate background proxy checks and status indicators.

Why This Change
Privacy First: Eliminates unexpected background network requests for users who don't opt-in
Performance: Reduces default resource usage and potential overhead for new installations
User Control: Ensures users make an informed choice about enabling monitoring features

What Changed
✅ Default Value: proxyMonitoring setting now defaults to false when no saved preference exists
✅ UI Behavior: "Enable Proxy Status Monitoring" checkbox appears unchecked by default
✅ Background Script: No monitoring intervals created unless explicitly enabled
✅ Content Script: Status dots and proxy-based styling disabled by default
✅ Storage Consistency: All storage read operations use false as fallback value

Files Modified
popup.js - Updated restore logic: result.proxyMonitoring !== undefined ? result.proxyMonitoring : false
content.js - Global variable initialization: let isMonitoringEnabled = false
content.js - Settings defaults object: proxyMonitoring: false
content.js - Background color logic: Added isMonitoringEnabled gate for proxy status colors
background.js - Monitoring start logic: Defaults to false when setting absent

User Impact
New Users: Checkbox unchecked, no background monitoring, standard floating bar colors
Existing Users: Saved preferences preserved - no behavior change for users with proxyMonitoring: true
Visual Changes: Floating bar uses user-selected background color instead of status-based colors when monitoring disabled

Release Notes Version 1.7.3

Disable proxy monitoring by default

Summary
Proxy status monitoring is now disabled by default. Users must explicitly enable the "Enable Proxy Status Monitoring" option in the popup settings to start background proxy checks.

Why
- Avoid unexpected background network checks for users who do not opt in.
- Reduce default privacy surface and potential performance overhead for new installs.

What changed
- Default value for the proxyMonitoring setting is now false when the setting key is absent.
- UI: the "Enable Proxy Status Monitoring" checkbox in the popup appears unchecked by default for fresh installs (no stored setting).
- Background: no monitoring intervals are started unless the user opts in.
- Content script: in-page monitoring / status-dot behavior that depends on monitoring is gated by this setting.

Files touched
- popup.js — restore/save logic uses result.proxyMonitoring !== undefined ? result.proxyMonitoring : false so checkbox defaults to unchecked.
- content.js — ensure any monitoring flag (e.g., isMonitoringEnabled) defaults to false and monitoring is gated.
- background.js — ensure startProxyMonitoring() reads the setting and defaults to false; do not create monitoring intervals when setting is absent/false.

User-visible behavior
- New users or users with no saved proxyMonitoring key: checkbox unchecked; no background proxy checks run.
- Existing users with proxyMonitoring: true remain unaffected unless they change the setting.

Suggested changelog entry
- "Default proxy monitoring disabled; users must opt-in to enable proxy status checks."

Automatic rollback based on version [1.2.1].

Version 1.2.2 - Maintenance Update

This update focuses on internal improvements to enhance the extension's stability and maintainability. While there are no new features, these changes ensure a smoother experience and make it easier to develop new features in the future.

• Code Refinements: The extension's codebase has been cleaned up and better documented.
• Improved Stability: Removed debugging code to streamline performance.

What's New

• Added phone number extraction feature for container names containing phone numbers in parentheses
• Added copy button with visual feedback for quick phone number copying
• Improved visual separation between container name and actions

Improvements

• Enhanced UI with visual separator between container name and copy button
• Added hover effects and visual feedback for better user interaction
• Improved accessibility with clear button states and tooltips
• Added semi-transparent backgrounds for better readability

Bug Fixes

• Fixed pointer events handling for interactive elements
• Improved position handling for different bar positions
• Enhanced dark mode compatibility

Technical Updates

• Optimized DOM manipulation for better performance
• Improved clipboard interaction handling
• Enhanced state management for visual feedback