fix(fileBrowser): exclude non-selectable system utility tiles from batch selection operations

[AuDevTist1C]

📌 Summary

This pull request introduces explicit safeguards across the file browser template and interaction handlers to isolate non-selectable system utility tiles (e.g., "Add a storage" prompts and "Select document" system actions) from batch selection modes and multi-item operations.

---

🔎 Problem & Context

In the file browser component, system utility notifications and action triggers reside in the exact same DOM list container (.tile:not(.selection-header)) alongside standard user files and directories. Previously, enabling selection mode or performing batch actions (such as toggling all checkboxes or clicking across items) would inadvertently select these utility items.

Because these utility tiles lack valid file path URLs or context data expected by batch action handlers, including them in the selection pool resulted in runtime exceptions and unexpected behaviors during batch operations (e.g., bulk moving, deleting, or archive operations).

---

🛠️ Key Changes

1. Handlebar Template Update (src/pages/fileBrowser/list.hbs):

   • Extended the list item template contract to render a data-not-selectable HTML dataset attribute whenever the item context defines {{#notSelectable}}.

2. System Utility Tile Configuration (src/pages/fileBrowser/fileBrowser.js):

   • Updated the metadata payload for system utility tiles—specifically the "Add a storage" action (strings["add a storage"]) and the "Select document" document picker action—to pass notSelectable: true during initialization.

3. Selection Handler Guards (src/pages/fileBrowser/fileBrowser.js):

   • Selection Mode Initialization: Updated list item iterations during selection mode activation to check for item.dataset.notSelectable != null and bypass checkbox creation/injection for utility tiles.
   • Touch & Click Delegation: Guarded click handlers in selection mode by evaluating $el2?.dataset.notSelectable != null and returning early. This prevents utility item state toggling, checkbox interaction, and invalid URL accumulation within the selectedItems tracking set.

---

🧪 Verification & Testing Steps

1. Open the File Browser view.
2. Enter Selection Mode.
3. Verify that the "Add a storage" and "Select document" tiles do not display active selection checkboxes and cannot be toggled.
4. Select all items in the list and perform batch actions (delete, copy); verify that no runtime errors occur and utility tiles remain unselected.

---

📂 File Changes Breakdown

• src/pages/fileBrowser/fileBrowser.js: Added guards checking dataset.notSelectable in selection initialization and click handlers, and flagged utility folders with notSelectable: true.
• src/pages/fileBrowser/list.hbs: Added the conditional {{#notSelectable}}data-not-selectable{{/notSelectable}} attribute definition to template rendered items.

_{(PR name and description are AI generated (Gemini 3.6 Flash))}

[greptile-apps]

Greptile Summary

This PR prevents file-browser system utility tiles from participating in batch selection.

• Marks “Add a storage” and “Select document” tiles as non-selectable.
• Renders the marker as a data attribute in the list template.
• Skips marked tiles during checkbox creation and selection-mode click handling.

Confidence Score: 5/5

The PR appears safe to merge with no actionable selection-path regressions identified.

The utility-tile metadata reaches the rendered DOM, both direct selection paths skip marked tiles, and select-all only processes tiles that received checkboxes.

Important Files Changed

Filename	Overview
src/pages/fileBrowser/fileBrowser.js	Adds and consistently enforces non-selectable metadata for utility tiles across individual and select-all interaction paths.
src/pages/fileBrowser/list.hbs	Emits the data attribute consumed by the new selection guards.

_{Reviews (1): Last reviewed commit: "fix: introduce non-selectable item handl..." | Re-trigger Greptile}