Two fixes, both small. No behaviour change for a working install: no settings change, no reconnecting, no database change outside the uninstall path.
New: a heads-up in Firefox, where tracking protection can block an assistant from connecting
Firefox's Enhanced Tracking Protection can stop the connection part-way through — the connector is added, sign-in opens, and then nothing completes, with no error shown anywhere to explain it.
Opening a connector screen in Firefox now shows a note explaining this and how to get past it: click the shield icon to the left of the address bar and switch Enhanced Tracking Protection off for this site, then connect again. The setting is remembered per site, affects nothing else you browse, and can be switched back on once the connection is working. The note appears only in Firefox and can be dismissed.
Adopted from AcrossAI Pro 0.9.16, where it was written for a real site that could not connect at all. Connecting an assistant became this plugin's job in 0.4.0, so the warning belongs here — and the paid plugin is removing its copy.
Fixed: uninstalling left a settings row behind
The "delete all data on uninstall" sweep deliberately skipped every option starting acrossai_mcp_connector_. That was right when it was written: an earlier release had handed that namespace to the paid plugin, and deleting another plugin's settings would have been wrong.
Version 0.4.0 took that area back, which quietly inverted the exception — it stopped protecting a foreign namespace and started orphaning our own row. The only option it still matched was this plugin's own version marker for one of its four tables, a table the same uninstall drops a few lines earlier. The sweep now covers the whole namespace.
Only affects uninstalling with the delete option switched on.
Full changelog: v0.4.2…v0.4.3