Freshness UX: per-drive index status badge + menu in the volume switcher

Every real drive now carries a small index-freshness dot in the volume switcher,
in two placements: always-visible next to the dropdown trigger (the ACTIVE
drive, beside the SMB light), and per-row inside the dropdown. Four states map
from the backend `VolumeIndexStatus`: gray (not indexed), blue (scanning, pulses
unless reduce-motion), green (fresh), yellow (stale). Clicking the dot opens a
small themed menu — turn on / off, rescan, stop — with a "Last indexed: <date> ·
took <duration>" footer.

- `DriveIndexBadge.svelte`: the dot + popover menu, a focusable `<button>` with
  an `aria-label` and `aria-haspopup` (no `role="img"` — axe rejects it on a
  button). Reuses the existing colored-indicator + `use:tooltip` shape.
- `drive-index-status.ts`: the pure state→color/menu/duration mapping, unit-tested.
- `drive-index-manager.svelte.ts`: a reactive `volumeId → status` map that fetches
  on demand and stays live by SUBSCRIBING to `index-freshness-changed` /
  `index-scan-started` / `index-scan-complete` (subscribe, don't poll). Fetch
  failures degrade to "no badge", never an unhandled rejection. `isDriveRow` is
  the badge-eligibility predicate (real drives only, not favorites/groups).
- `VolumeBreadcrumb.svelte`: renders the badge in both placements and runs the
  per-drive IPC for a picked action. A refused SMB enable/rescan is classified by
  TYPED `SmbIndexGateReason` (never message text): `credentials_needed` routes
  into the direct-connect/login flow, the rest show a friendly toast.
- Copy is i18n-ized under `fileExplorer.navigation.driveIndex.*`.
- Drive-by: reword a `volume_scanner` debug log to `key=value` form so it stops
  tripping `pluralize-noun`.

Author: vdavid

apps/desktop/src-tauri/src/indexing/volume_scanner.rs

@@ -211,7 +211,7 @@ pub(crate) async fn scan_volume_via_trait(
         .map_err(|e| VolumeScanError::WriterSend(e.to_string()))?;
 
     log::info!(
-        "volume_scanner: walk complete for {}: {total_entries} entries, {total_dirs} dirs in {}ms",
+        "volume_scanner: walk complete for {}: entries={total_entries}, dirs={total_dirs} in {}ms",
         root.display(),
         start.elapsed().as_millis()
     );

apps/desktop/src/lib/file-explorer/navigation/CLAUDE.md

@@ -34,6 +34,12 @@ Browser-style back/forward history, path resolution, paged keyboard shortcuts, a
   make it per-pane.
 - **`containingVolumeId` is derived via `resolvePathVolume(currentPath)`, not the `volumeId` prop** (which may be a
   favorite's virtual id), so the active checkmark tracks the real containing volume.
+- **The drive-index freshness badge (`DriveIndexBadge.svelte`) renders only on real DRIVE rows** (`isDriveRow`: not
+  favorites, not the synthetic `network` / `search-results` entries), in two placements (active-drive by the trigger,
+  per-row in the dropdown). State→color/menu mapping is the pure `drive-index-status.ts`; status stays live via the
+  manager's event subscriptions, not polling. The badge is a `<button>` (no `role="img"` — axe rejects it). Refused
+  enable/rescan is classified by typed `SmbIndexGateReason`, never message text. Full contract: DETAILS § Drive index
+  freshness badge.
 - **Favorites: mutate ONLY via the `commands.*` wrappers and ALWAYS strip the `fav-` prefix.** The switcher's
   `LocationInfo.id` is `fav-<favoriteId>`; `removeFavorite` / `renameFavorite` / `reorderFavorites` take the bare id
   (`stripFavoritePrefix`). The favorites group in `volume-grouping.ts` always renders (even empty, for the placeholder),

apps/desktop/src/lib/file-explorer/navigation/DETAILS.md

@@ -30,6 +30,12 @@ Browser-style back/forward history, path resolution, paged keyboard shortcuts, a
   `effectiveVolumes` / `favorites` stay in the component and read `fav.optimisticFavoriteIds`
 - **`eject-predicate.ts`**: Pure `isVolumeEjectable(volume)` used by the eject button gate. Returns true when NSURL says
   ejectable OR the volume has any SMB connection state
+- **`DriveIndexBadge.svelte`**: Per-drive index freshness dot (gray/blue/green/yellow) + its click menu (see § Drive
+  index freshness badge)
+- **`drive-index-status.ts`**: Pure mapping for the badge: `VolumeIndexStatus` → state/color, menu items per state, the
+  "N min, S s" duration formatter (`drive-index-status.test.ts`)
+- **`drive-index-manager.svelte.ts`**: Reactive `volumeId → VolumeIndexStatus` map; fetches on demand and subscribes to
+  the indexing events to stay live. `isDriveRow(volume)` is the badge-eligibility predicate
 - **`navigation-history.test.ts`**: Full unit test coverage of history functions
 - **`path-navigation.test.ts`**: Unit tests for path resolution and timeouts
 - **`keyboard-shortcuts.test.ts`**: Unit tests for shortcut calculations
@@ -316,6 +322,33 @@ row. Tooltip shows `<label> (Max. <N> MB/s)\nNegotiated for this cable, port, an
 `white-space: pre-line`, so `\n` becomes a real line break). The dot is the only visual — no inline text in the chip and
 no extra line under the disk-space bar, by design.
 
+### Drive index freshness badge
+
+Each real drive carries a small index-freshness dot (`DriveIndexBadge.svelte`) in TWO placements: always-visible next to
+the dropdown trigger (reflecting the ACTIVE drive), and per-row inside the dropdown. Both reuse the same colored-dot +
+`use:tooltip` shape as the SMB light and USB-speed ring. The four states map from the backend `VolumeIndexStatus`
+(`commands.getVolumeIndexStatusById`): gray = `disabled` (no live index, `enabled: false` or `freshness: null`), blue =
+`scanning`, green = `fresh`, yellow = `stale`. The mapping, the menu items per state, and the "N min, S s" duration
+formatter are the pure `drive-index-status.ts` (unit-tested). Blue pulses (gated behind `prefers-reduced-motion`).
+
+- **Eligibility is `isDriveRow(volume)`** (in `drive-index-manager.svelte.ts`): every entry except favorites and the
+  synthetic `network` / `search-results` ids. SMB shares (`category: 'network'`, real id) and the local disk (`root`)
+  DO get a badge; the synthetic "Network" group entry does not. The badge is gray for any drive without a registered
+  index, so it's safe to query for every eligible row.
+- **Status stays live by SUBSCRIPTION, not polling** (`drive-index-manager.svelte.ts`): it listens to
+  `index-freshness-changed`, `index-scan-started`, and `index-scan-complete`, refetching the named volume's status on
+  each (the events alone don't carry the last-scan facts). The active-drive badge also refetches when the active drive
+  changes; dropdown rows refetch on open.
+- **The badge is a focusable `<button>`** with an `aria-label` (state ariaLabel + the tooltip text) and
+  `aria-haspopup="menu"`; clicking opens a small themed popover menu (NOT a native menu) anchored to the badge. Menu
+  actions (`enable`/`rescan`/`disable`/`stop`) call back to `VolumeBreadcrumb`'s `handleDriveIndexAction`, which runs
+  the per-drive IPC. ❌ Don't put `role="img"` on the button (axe rejects it; the button role + label already convey it).
+- **Refused enable/rescan is classified by TYPED variant** (`SmbIndexGateReason`), never message text: `credentials_needed`
+  routes into the existing direct-connect/login flow (`handleSubmenuAction`); the others show a friendly toast.
+- **The dropdown-row menu can be clipped by the dropdown's `overflow-y: auto`** (unlike the breadcrumb placement). The
+  breadcrumb badge is the primary surface (D3) and isn't clipped; the row menu is a convenience. If this becomes a
+  problem, switch the row menu to `position: fixed` from `getBoundingClientRect()` like the connection submenu.
+
 ### Dropdown and submenu UI patterns
 
 These patterns emerged during the volume picker implementation and should be followed in future dropdown/submenu work:

apps/desktop/src/lib/file-explorer/navigation/DriveIndexBadge.a11y.test.ts

@@ -0,0 +1,61 @@
+/**
+ * Tier 3 a11y tests for `DriveIndexBadge.svelte`: the focusable, labeled status
+ * dot and its open menu must have no axe violations, in each freshness state.
+ * Mirrors `IndexingStatusIndicator.a11y.test.ts`.
+ */
+import { describe, it, expect } from 'vitest'
+import { mount, flushSync, tick } from 'svelte'
+import DriveIndexBadge from './DriveIndexBadge.svelte'
+import { expectNoA11yViolations } from '$lib/test-a11y'
+import type { Freshness, VolumeIndexStatus } from '$lib/ipc/bindings'
+
+function makeStatus(freshness: Freshness | null, enabled = freshness != null): VolumeIndexStatus {
+  return {
+    volumeId: 'smb-test',
+    enabled,
+    freshness,
+    scanCompletedAt: freshness === 'fresh' ? 1_750_000_000 : null,
+    scanDurationMs: freshness === 'fresh' ? 134_000 : null,
+  }
+}
+
+async function mountBadge(status: VolumeIndexStatus) {
+  const target = document.createElement('div')
+  document.body.appendChild(target)
+  mount(DriveIndexBadge, { target, props: { volumeId: status.volumeId, status, onAction: () => {} } })
+  await tick()
+  return target
+}
+
+describe('DriveIndexBadge a11y', () => {
+  it('the gray (disabled) dot has no violations', async () => {
+    const target = await mountBadge(makeStatus(null, false))
+    expect(target.querySelector('.drive-index-badge')).not.toBeNull()
+    await expectNoA11yViolations(target)
+  })
+
+  it('the blue (scanning) dot has no violations', async () => {
+    const target = await mountBadge(makeStatus('scanning'))
+    await expectNoA11yViolations(target)
+  })
+
+  it('the green (fresh) dot has no violations', async () => {
+    const target = await mountBadge(makeStatus('fresh'))
+    await expectNoA11yViolations(target)
+  })
+
+  it('the yellow (stale) dot has no violations', async () => {
+    const target = await mountBadge(makeStatus('stale'))
+    await expectNoA11yViolations(target)
+  })
+
+  it('the open menu has no violations', async () => {
+    const target = await mountBadge(makeStatus('stale'))
+    const badge = target.querySelector<HTMLButtonElement>('.drive-index-badge')
+    expect(badge).not.toBeNull()
+    badge?.click()
+    flushSync()
+    expect(target.querySelector('.drive-index-menu')).not.toBeNull()
+    await expectNoA11yViolations(target)
+  })
+})