Summary
Define and execute a migration strategy so QuickFolders no longer depends on window.quickFilters side effects, and instead uses a single stable cross-addon interface.
Strategy
Route all quickFilters interactions through one background bridge abstraction.
Treat missing or older quickFilters as a normal availability state, not an exceptional failure path.
Keep behavior-compatible return contracts for legacy callers during transition.
Use capability discovery to gate optional features and version differences.
Complete migration in phases, then remove legacy side-effect paths once parity is confirmed.
Related tracking items in quickFilters:
issue 373: Modernize calling assistant: use external Message list
issue 374: External API discovery function: add and document listExternalCommands
Summary
Define and execute a migration strategy so QuickFolders no longer depends on window.quickFilters side effects, and instead uses a single stable cross-addon interface.
Strategy
Route all quickFilters interactions through one background bridge abstraction.
Treat missing or older quickFilters as a normal availability state, not an exceptional failure path.
Keep behavior-compatible return contracts for legacy callers during transition.
Use capability discovery to gate optional features and version differences.
Complete migration in phases, then remove legacy side-effect paths once parity is confirmed.
Related tracking items in quickFilters:
issue 373: Modernize calling assistant: use external Message list
issue 374: External API discovery function: add and document listExternalCommands