feat: plugin quicktool adapter

[deadlyjack]

• allow plugin to adapt quicktool
• allow plugin to hook save, save event
• fix icon size in file explorer
• feat: icon button tooltip

[greptile-apps]

Confidence Score: 5/5

The changes appear safe to merge, with only the existing non-blocking plugin API documentation concern remaining.

Findings

1.  Plugin Contract Lacks Documentation ▶

Summary

• Routes quick-tool actions, modifiers, focus, selection, and cancellation through per-tab adapters.
• Adds asynchronous save-event handling for custom tabs and safer save-all/close workflows.
• Defers plugin-backed file loading until filesystem providers initialize while preserving cached restoration state.
• Adds delegated long-press tooltips and adjusts file-browser icon sizing.
• The previously reported quick-tools capture issue is resolved; the public adapter contract remains insufficiently documented.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    Plugin[Plugin custom tab] --> Register[registerQuickToolsAdapter]
    Register --> Registry[Per-tab adapter registry]
    QuickTools[Quick-tools UI] --> Registry
    Registry -->|capture/restore selection| Plugin
    Registry -->|execute action| Plugin
    Registry -->|tab switch, overlay, busy state| Cancel[Cancel pending work]

    Save[Save commands] --> SaveEvent[Custom-tab save event]
    SaveEvent -->|respondWith promise| PluginSave[Plugin persistence]
    PluginSave -->|success| Workspace[Workspace save notifications]

    Restore[Restored plugin URI] --> ProviderCheck[Filesystem provider check]
    ProviderCheck -->|missing| PluginLoad[Wait for initial plugin load]
    PluginLoad --> Provider[Resolve provider and load file]

Loading

_{Reviews (4) · Last reviewed commit: "fix: plugin based file system intializat..."}

[bajrangCoder]

Slow provider startup can delete recovery data

waitForInitialPluginLoad() resolves when the 15-second plugin-load race finishes, even though a timed-out plugin continues loading in the background. If its filesystem provider registers after that timeout, fsOperation(this.uri) is still undefined here and .exists() throws. The catch path removes the restored tab, and destruction can delete its cached unsaved content. Keep the tab pending until the provider registers, or fail without removing the tab/cache.