Improvements

• More reliable Firefox support — Hardened the Firefox native-messaging connection handling (wrapping browser APIs so async storage and messaging calls behave consistently) and refreshed the extension naming/manifest for consistent identification across browsers.
• Clearer diagnostics when saving in-progress state fails — Failures to persist the open segment snapshot to local storage are now logged instead of being silently swallowed, making segment/queue issues easier to diagnose.

Maintenance

• Normalized "ScalePad" and "macOS" branding throughout the extension.
• Updated build and development dependencies (@types/chrome, esbuild).

Improvements

Tracking now survives the browser suspending the extension — Chrome, Edge, and Firefox aggressively shut down extension background scripts when idle. Previously the in-progress segment could be lost (or could resume incorrectly) when this happened. The extension now persists its open segment to local storage and rebuilds state when the background script restarts, so a segment in progress when the browser suspended the extension is no longer lost.

No more phantom segments after sleep, hibernate, or other unobserved gaps — Previously, if the machine slept while a segment was open, that segment kept running until the next observation, producing a single long segment that included the entire sleep duration. A new reconciliation loop now detects gaps of more than 30 seconds without an observation and closes the open segment at the last observed time instead.

Self-healing delivery when the desktop agent returns errors — When the desktop agent rejects a segment (for example because its database is briefly locked), the extension now applies an exponential backoff between retries (2s → 5s → 15s → 1 min → 5 min) instead of retrying as fast as possible. After repeated failures on the same segment (10 consecutive errors, or 30 minutes of failure) that segment is set aside in a capped dead-letter queue so the next segment in line can still be delivered — the queue can no longer get permanently stuck behind a single failing message.

🛠 Fix: Firefox & Edge activity tracking issues

Resolves an issue where Firefox and Edge extensions failed to record web activity segments (Chrome unaffected).

What was fixed
- Active tab detection failure (DevTools interaction)
- When DevTools was focused, the extension couldn’t detect a valid browser tab, preventing tracking from starting.
- Fixed by falling back to normal browser windows when no trackable tab is found.
Native messaging host not found
- Firefox and Edge could enter a reconnect loop due to a missing com.scalepad.agent manifest.

Fixed by:
- Registering both com.scalepad.agent and com.scalepad.agent.main
- Adding fallback logic to recover from failed connections
- Improved connection resilience
- Extension now detects failed connections earlier and retries immediately, improving compatibility with older agent installs.

Result
- Activity tracking now works reliably in Firefox and Edge
- Extension recovers automatically from missing or outdated agent configurations

Version 4.0.6 — Bug fix
Fixed: First website visit not tracked after opening the browser
When opening the browser (or switching to it) and navigating to a URL, the first visit was not recorded as activity. The extension only started tracking after a second interaction — such as switching away and back to the tab or clicking on the page.
Root cause: When a tab becomes active, the browser fires the tab-activated event before the URL is fully set. The extension received the activation event with no URL, skipped tracking, and then when the URL arrived via a second event, it incorrectly required an existing tracking session to already be in progress before it would react.
Fix: The extension now starts a tracking session when a URL loads into an already-active tab even if no session was previously in progress. Domain-change logic (ending the current session and starting a new one) is unaffected.
Affected browsers: Firefox (macOS and Windows), Microsoft Edge (Windows). Chrome was not affected in practice but benefits from the same fix.

Fix Firefox support

Updated stability for browser->desktop agent communication.