Updated after the refactor discussion. The page keeps the earlier visual samples, but the decisions are now explicit: launcher-style maintenance console, Duplicate Review as the default work surface, status on navigation instead of a dashboard pane, Bulk ID Check with a popup-launched quick window plus a full Console tool, and debug/testing surfaces pulled out of the daily workflow.
Frequent maintenance tools get focused destinations. The navigation carries status instead of a separate dashboard pane.
Default landing after uploads. Keep Ranking Rules and delete history stay with the workflow that uses them.
Keep Ranking Rules live inside Duplicate Review, not as a distant general setting.
Cache & Scans owns the scan detail. The sidebar badge is enough while you review dupes.
Library Issues and Bulk ID Check remain direct tools, not settings fieldsets.
Chosen: Console / Settings / Support sidebar, Duplicate Review first, no dashboard pane.
The page should open focused maintenance views instead of collecting every heavy tool as a permanent fieldset.
Full space for filters, keep reasons, and delete queue safety.
Chosen for the big surfaces: Duplicate Review, Cache & Scans, Library Issues, and Bulk ID Check.
Console, Settings, and Support stay distinct through sidebar groups, not a second top-level mode control.
Chosen conceptually, simplified visually: sidebar groups do the separating work.
The maintenance order is real, but it should be encoded by the Console tools themselves rather than another page.
The sidebar and focused tools make the flow clear without adding a separate wizard surface.
Rejected as a dedicated home page. Useful order, unnecessary extra destination.
This would turn the popup into a two-mode mini-app with cramped result review.
Rejected even for 5-20 IDs. The popup gets a doorway into a focused Bulk Check surface, not a permanent second mode.
Typical batches are expected to be about 5-20 IDs, so the popup opens a compact focused window while the Console owns the full tool.
Quick batch window
Chosen: popup opens a compact Bulk Check window for short batches. The Console remains the full batch-review surface.
Debug history and standalone tests move out of daily workflow. Sim Dupe leaves the extension UI entirely.
Popup state samples live in a repo HTML file such as samples/popup-states.html, not as a hidden extension page.
Chosen: standalone support/debug tools remain available; Sim Dupe is removed from extension UI.
Rule editors keep local feedback. Only standalone troubleshooting benches move to Debug Tools.
Chosen: contextual inline tests stay. General troubleshooting tools move to Support.