Added:
- Cross-seed: assemble a season pack from several episode torrents, as qui's own dialog does since qui 1.29.0. The picker preselects the episodes qui suggests, shows coverage and missing bytes for the selection, and applies through POST /api/cross-seed/manual/assemble. Instances without hardlink or reflink mode still pick one target.

Changed:
- Dependencies: update React to 19.3, lucide-react, tailwind-merge, and the Bun and React types (#36).

Added:
- Menu: choose Top, Bottom, or Disabled for the cross-seed action. Top remains the default. Hide empty instance menus and show a settings hint when no actions remain.

Fixed:
- Menu: skip the instance submenu when only one enabled instance has visible actions.
- Tests: use typed cached data and fix typechecking for menu order expectations.

Changed:
- Dependencies: update lucide-react and the Bun and React DOM types.

Changed:
- Menu: group cross-seed, categories, and saved paths under one "qui" menu (#31). One enabled instance needs no instance submenu. Favorites only filters categories.

Changed:
- Release: bun run submit builds the zips and uploads them to the Chrome Web Store and Firefox Add-ons through wxt submit. Store credentials live in .env.submit, which git ignores. docs/agents/release.md has the layout. The Firefox version gets the CHANGELOG section of the release as its release notes.

Docs:
- Add docs/agents/release.md with the release steps, the .env.submit layout, and store error meanings.

Fixed:
- Firefox: adding a .torrent link failed with "Fetch failed" since 0.4.0. The in-tab download succeeded, but Firefox blocks typed-array methods on the response bytes across its realm boundary, and the error text was lost. The encode now uses FileReader, and the notification shows the real Firefox error when a fetch fails.
- CI: the release job downloads the build artifact into extensions/ again, so tagged builds attach the zips to the GitHub release.

Added
- Save paths: send a torrent to a configured save path. Set the paths in options, one per line. Each instance submenu lists them after the categories.
- Cross-seed in qui: a new context menu item for .torrent links. Pick an instance, then a target torrent from the ranked list or by name search, set category and tags, and qui adds the torrent pinned to that target with a full recheck. Needs qui 1.28.0 or newer. Magnet links are not supported because they carry no file list.

Changed
- Permissions: the extension no longer asks for access to all websites and has no always-on content script. Torrent files are fetched inside the clicked tab with activeTab and scripting, granted by the click itself.
- Server access: the qui server origin is now an optional permission. Save in options requests it. Existing users see a "Grant access" button in options until they grant it.
- Errors: notifications and the options page show the error text qui returns instead of only the HTTP status.

Removed
- The toolbar button no longer toggles based on torrent links found on the page. It is always enabled.

Changelog for 0.2.0:

What's New

• Added browser-side torrent file fetching for private tracker support
• .torrent files are now downloaded in the browser using the page's authenticated session
• This allows adding torrents from private trackers that use cookie-based authentication
• Magnet links continue to work as before (sent directly to qui server)

Technical Changes

• Added content script to fetch .torrent files with page cookies
• Added addTorrentFile API function for uploading torrent file data
• Changed from optional to required host permissions (<all_urls>) for content script injection
• Removed dynamic script injection in favor of manifest-declared content script

Added optional HTTP Basic Auth support for users behind reverse proxies (e.g., nginx with basic auth). Configure username/password in the collapsible "Basic Auth" section in options.

Fixed an issue where HTTP connections to qui servers would fail on Firefox. HTTPS connections are unaffected.