• A "Save" button in the sidebar lets you save the current analysis to your
  Cruxly account, so it shows up under "My Summaries" on the site instead of
  only in the extension's local recents list. Requires signing in and an
  active Study or Pro plan; the button shows a checkmark once saved.
• The page banner (shown on regular webpages and PDFs) now has a "don't show
  on this site" option next to its close button. Muting a site is
  remembered locally and stops the banner from reappearing there on future
  visits — other sites are unaffected.

• The page banner no longer shows a text label ("PDF detected" / "Analyze
  this page") — just the icon and the "Analyze with Cruxly" button, a
  cleaner look.
• The extension's store listing description now mentions web pages
  alongside video and PDF.

• New "Analyze this page" button for any regular webpage, not just YouTube
  and PDF. A small banner now appears in the bottom-right corner of any
  http(s) page — excluding YouTube and PDF pages, which keep their own
  existing banners, and cruxly.tech itself — offering to run the page
  through Cruxly's website analyzer. Clicking it queues the analysis and
  follows the same "click the toolbar icon" flow already used for the PDF
  banner, since Firefox never lets a content-page button open the sidebar
  directly.
• The sidebar's manual "Analyze a URL" field now recognizes any http(s)
  link as a website-analysis candidate. Previously, anything that wasn't a
  YouTube link or a .pdf URL silently fell back to being submitted as a
  video. The toolbar popup does the same for the current tab: a regular
  webpage now shows as "Webpage" with its own "Analyze Page" button
  instead of "No content detected".

• content/pdf-detector.js renamed to content/page-detector.js — same
  file, same injection rule (<all_urls>, excluding YouTube), now also
  handling the website banner alongside its existing PDF-page and
  PDF-link jobs. It reuses the same overlay container, toast, and
  message-passing helpers, just parameterized per banner type.
• New locale strings added to en and ru for the new banner, badge, and
  status labels. No existing strings were removed or repurposed.

Sidebar auto-open suppression on reload/update, queued-analysis flow
instead of a jarring new-tab fallback, token auto-detect picking the right
tab, and several sidebar rendering fixes (loading steps, details/summary
widgets, multi-line paragraphs). See git history for full detail.

• Sidebar no longer auto-opens on addon reload/update. Firefox has a known
  bug (Bugzilla #1892667) where the sidebar pops open on reload/update even
  with open_at_install: false set. manifest.json sets that flag for
  genuine installs, and service-worker.js adds a short polling backstop
  (up to 2s) that closes the sidebar the instant Firefox opens it on its
  own — without touching a sidebar the user opened themselves.
• "Analyze" no longer dead-ends by jumping to cruxly.tech. Firefox never
  lets a content-page button (Analyze on YouTube/a PDF) open the sidebar
  directly — no user gesture on a third-party page. Previously this opened
  the analysis on the website in a new tab, yanking the user away from what
  they were reading. Now the analysis is queued in local storage, the
  toolbar icon gets a badge as a guaranteed fallback, action.openPopup()
  is tried automatically on Firefox 149+, and on any version clicking the
  icon opens the popup, which immediately retries sidebarAction.open()
  (a real user gesture) and closes itself — or, if that still fails, shows
  one explicit "open it" button instead of the normal popup UI.
• Token auto-detect could pick a stale Cruxly tab. It used to read the auth
  token from whichever matching tab came back first from the tab query,
  which could be a stale tab from before login, in another window. It now
  tries every matching tab and uses the first one that actually has a
  token.
• Loading-step indicator no longer guesses from status text. It used to
  infer the fetch/analyze/structure step by substring-matching the
  backend's human-readable status message, which isn't guaranteed to be in
  English. It now reads the backend's machine-readable stage field
  directly, and a step can no longer regress once reached.
• <details>/<summary> collapsible sections (Key Moments, Practical
  Advice) now render as widgets instead of literal text — the markdown
  renderer's blanket < escaping was catching them. A narrow,
  attribute-free exception now protects exactly this shape before
  escaping, plus matching CSS for border/chevron/hover state.
• Multi-line analysis sections could lose their line breaks: a block
  starting with an already-converted heading used to have everything after
  it collapsed onto one line. Consecutive lines are now grouped into their
  own paragraph, while headings, lists, and details/summary keep their own
  line as before.

• Copy for the content-page Analyze buttons switched from "Opened in a new
  tab" to "Click the icon to view", matching the new queued-analysis flow.
  New locale strings added to en and ru.

Fixes
1. popup.js was unconditionally opening the sidebar the instant the popup was opened — even with nothing pending — which is why settings and the sidebar both appeared after install with no way to close the sidebar. Removed that; the sidebar now only opens from an explicit button click.
2. Both extensions' background scripts now fall back to opening the analysis in a new website tab when the sidebar/side panel can't be opened, instead of leaving the user with just a badge and a "go click the toolbar" message. On Firefox this fires every time from that button (expected);
3. Updated the toast/button copy in both languages to reflect "opened in a new tab" instead of the old dead-end hint.

1.0.1 — Compatibility fixes

Switched all extension APIs from Chrome's callback-based chrome. namespace to Firefox's native promise-based browser. namespace. This fixes intermittent failures in context menu registration, tab badge updates (YT/PDF indicators), settings sync, and sidebar opening that could occur because chrome.* is only a compatibility shim in Firefox and doesn't reliably behave like the real API. No new features or permission changes.