Index all notes

core/constants/aiIndex.ts

@@ -1,4 +1,4 @@
-import type { AIIndexStatus, AIIndexMutationResult } from "@core/types/aiIndex"
+import type { AIIndexStatus, AIIndexMutationResult, AIIndexNoteRow } from "@core/types/aiIndex"
 
 export const AI_INDEX_STATUS_LABELS: Record<AIIndexStatus, string> = {
   indexed: "Indexed",
@@ -49,3 +49,11 @@ export function getAIIndexActionPresentation(status: AIIndexStatus): AIIndexActi
     buttonVariant: "default",
   }
 }
+
+export function isAIIndexStatusActionable(status: AIIndexStatus) {
+  return status !== "indexed"
+}
+
+export function getAIIndexActionableNotes(notes: AIIndexNoteRow[]) {
+  return notes.filter((note) => isAIIndexStatusActionable(note.status))
+}

docs/ai/design/feature-ai-index-page.md

@@ -13,6 +13,7 @@ graph TD
     SP["SettingsPage"] --> TAB["AIIndexTab"]
     TAB --> FILTERS["StatusFilters"]
     TAB --> SEARCH["SearchRow"]
+    TAB --> BULK["Bulk Index Loaded Action"]
     TAB --> LIST["AIIndexList"]
     LIST --> ROW["AIIndexNoteRow"]
     TAB --> HOOK["useAIIndexNotes(status, search, page)"]
@@ -28,6 +29,7 @@ graph TD
 - `SettingsPage` gets a new `AI Index` tab entry.
 - `AIIndexTab` is a standalone settings flow, not a reuse of the notes page controller.
 - `useAIIndexNotes` owns pagination, active filter, loading state, and cache invalidation for this page only.
+- `AIIndexTab` also owns the summary-level bulk action state for the currently loaded result set.
 - `AIIndexList` reuses the virtualization pattern from `NoteList`, but renders dedicated AI-index rows/cards.
 - `AIIndexNoteRow` renders note metadata and per-row actions.
 - A dedicated server-side RPC returns notes together with aggregated index status so filtering and pagination remain correct.
@@ -113,6 +115,7 @@ The `all` filter is the default page state so the Settings tab opens with the fu
 
 - Settings-specific container for:
   - heading / summary
+  - summary-level bulk action button for loaded notes
   - filter pills
   - ordinary search row below the pills
   - list body
@@ -148,6 +151,19 @@ The `all` filter is the default page state so the Settings tab opens with the fu
   - last indexed timestamp
   - note-level action buttons
 
+### Bulk action behavior
+
+- The summary/header area gets one bulk action button beside the existing reset/filter context.
+- The bulk action scopes itself to the currently loaded client list after server-side filter and search have already been applied.
+- It must not fetch additional pages or infer unseen matches from `totalCount`.
+- Eligible rows:
+  - `not_indexed`: invoke `rag-index` with `action: "index"`
+  - `outdated`: invoke `rag-index` with `action: "reindex"`
+  - `indexed`: skip
+- The implementation reuses the existing single-note `rag-index` contract in a client-side loop instead of adding a separate bulk RPC or Edge Function.
+- On web, successful mutations should flow through the same optimistic row-update and exit-animation pipeline already used for per-row actions so filtered rows disappear gracefully.
+- On mobile, successful mutations should reuse the same cache patch + invalidate path already used for per-row actions so cards disappear from filtered views consistently.
+
 ## Design Decisions
 
 ### Dedicated fetch path instead of client-side joining
@@ -165,6 +181,16 @@ The `all` filter is the default page state so the Settings tab opens with the fu
 - Decision: keep `rag-index` for write actions and add a dedicated RPC read path for AI index state.
 - Rationale: existing mutation behavior is already shipped and tested; the missing capability is efficient list aggregation and filtering.
 
+### Bulk action targets loaded notes, not all matching notes
+
+- Decision: the bulk button processes only the currently loaded notes that remain visible after the active filter and active committed search query.
+- Rationale: this matches the mental model already shown in the summary ("Showing X loaded notes out of Y"), avoids hidden work on notes the user cannot currently inspect, and keeps the feature aligned with the paginated/infinite-list architecture on both web and mobile.
+
+### Bulk action stays on the client and reuses the single-note mutation API
+
+- Decision: do not add a backend bulk-index endpoint for this refinement.
+- Rationale: the existing `rag-index` function is explicitly single-note, the AI Index page already owns the loaded list on the client, and reusing the current mutation path is the smallest, safest change for web and mobile parity.
+
 ### Reuse ordinary search semantics without reusing the notes controller
 
 - Decision: reuse the main note-search query construction and UX (`Search` input, debounce, 3-character threshold, FTS-first behavior) inside the dedicated AI Index flow.
@@ -185,6 +211,7 @@ graph TD
     SS --> AIP["AIIndexPanel"]
     AIP --> CHIPS["Filter Chips (Pressable)"]
     AIP --> SINPUT["Search TextInput"]
+    AIP --> BCTA["Bulk Index Loaded Button"]
     AIP --> FL["FlatList"]
     FL --> CARD["AIIndexNoteCard (memo)"]
     AIP --> HOOK["useAIIndexNotes(filter, search)"]
@@ -201,6 +228,7 @@ graph TD
 - Standalone panel component rendered inside a dedicated `flex: 1` AI Index viewport in `SettingsScreen` (not wrapped in the general settings `ScrollView`).
 - Filter row: one horizontally scrolling Pressable-chip rail matching `SettingsTabBar` interaction and sizing.
 - Search TextInput with clear button, debounced at 300ms.
+- Summary row can expose one bulk button near the count/reset affordances when the current loaded list contains `not_indexed` or `outdated` cards.
 - FlatList with `onEndReached` for infinite scroll, `onRefresh` for pull-to-refresh.
 - Loading spinner, empty message, and error + retry states.
 - Summary text ("X notes" or "Showing X of Y notes").

docs/ai/implementation/feature-ai-index-page.md

@@ -59,6 +59,7 @@ ui/web/components/features/settings/
 - Reuse the shared search utilities (`SEARCH_CONFIG`, `buildTsQuery`, language mapping) so AI Index search behaves like the main notes search without reusing the notes controller.
 - Make each AI Index row open the corresponding note in the main notes shell while preserving the originating `Settings -> AI Index` view state for back navigation.
 - Refine the page so it surfaces the user's working context directly: visible count, loaded count, active scope, active search, reset affordances, and clearer empty-state recovery.
+- Add a summary-level `Index loaded notes` action that only processes the currently loaded rows after active filter + active committed search have already narrowed the dataset.
 - Keep the summary chrome intentionally compact so the note list appears on the first screen without requiring an initial scroll.
 - Hide the redundant Settings-section hero for `AI Index` specifically; the left navigation already provides the tab label and description.
 
@@ -73,6 +74,7 @@ ui/web/components/features/settings/
 - Keep the row card-like rather than turning it into a rigid table. The title block should own most of the width, status should live as a compact badge in the metadata line, and action buttons can stay equal-width without stealing title space on desktop or mobile.
 - Because AI Index commonly opens notes in the main workspace after a cold `/settings` load, prefetch the `/` route and prewarm the first main-notes query page while the AI Index tab is already visible.
 - Treat row mutations as optimistic UI updates: if the current filter still includes the note, swap its status/button state immediately; if the mutation moves the note out of the active filter, keep it around just long enough for a short exit animation before removing it from the visible list.
+- Treat the bulk summary action as an orchestrator over the existing row-mutation path rather than a separate backend workflow. It should derive its candidate set from the already loaded list, skip `indexed` rows, and feed each success back through the same row-update pipeline.
 - Keep the underlying `rag-index` source of truth aligned with the optimistic UI by writing a fresh `indexed_at` timestamp during reindex upserts; otherwise `Outdated` notes can stay stale even after a successful reindex.
 - Normalize `rag-index` payloads through `core/rag/indexResult.ts` so semantic non-success responses such as `reason: "too_short"` do not show a false success state in AI Index.
 
@@ -121,6 +123,7 @@ ui/mobile/app/(tabs)/
 - AI Index filter tabs intentionally match the top `SettingsTabBar` interaction model: one horizontal scroll rail, no wrapping, and no extra boxed card around them.
 - The filter rail is visually separated with a divider rather than another surface, so the first useful content stays closer to the top of the screen.
 - Mobile action buttons are stacked vertically inside each AI Index card to keep long labels readable on narrow screens.
+- The mobile bulk action should live in the same summary area as the count/reset affordances so it mirrors the web placement and inherits the same "loaded notes only" mental model.
 
 ## Integration Points
 

docs/ai/planning/feature-ai-index-page.md

@@ -13,6 +13,7 @@ description: Task breakdown for the Settings AI index management page
 - [x] Milestone 3: Row actions refresh list state correctly and tests cover the new flow
 - [x] Milestone 4: AI Index supports ordinary note search semantics below the status tabs
 - [x] Milestone 5: Mobile AI Index page with filters, search, actions, and tests
+- [x] Milestone 6: AI Index supports a summary-level `Index loaded notes` action on web and mobile that respects the current loaded search/filter scope
 
 ## Task Breakdown
 
@@ -60,6 +61,16 @@ description: Task breakdown for the Settings AI index management page
 - [x] Task 4.6: Write unit tests for hook, card, and panel (21 tests)
 - [x] Task 4.7: Pass type-check and lint with zero errors
 
+### Phase 5: Loaded-scope bulk indexing refinement
+
+- [x] Task 5.1: Update feature docs to define the loaded-only bulk indexing semantics
+- [x] Task 5.2: Add a summary-level bulk button to the web AI Index tab in the header area
+- [x] Task 5.3: Reuse existing row mutation semantics so bulk successes update/animate rows correctly on web
+- [x] Task 5.4: Add a matching summary-level bulk button to the mobile AI Index panel
+- [x] Task 5.5: Ensure the bulk action uses only the currently loaded notes after active filter + committed search query
+- [x] Task 5.6: Add web and mobile unit tests for loaded-only bulk indexing behavior
+- [x] Task 5.7: Re-run targeted validation and record outcomes in implementation/testing docs
+
 ## Dependencies
 
 - Existing `rag-index` Edge Function remains the mutation layer.
@@ -84,6 +95,8 @@ Total expected effort: 1 focused implementation cycle with follow-up testing and
   - Mitigation: mirror `NoteList` sizing and scrolling patterns in a dedicated component.
 - Query refresh race after row mutations
   - Mitigation: centralize invalidation in the AI index hook/query key.
+- User confusion about bulk scope when pagination and search are active
+  - Mitigation: label the action as `Index loaded notes`, place it beside the existing loaded-count summary, and keep the implementation scoped to the current loaded list only.
 
 ## Resources Needed
 

docs/ai/requirements/feature-ai-index-page.md

@@ -32,6 +32,7 @@ Users can currently index or delete the AI/RAG index only from inside an individ
   - `Index`
   - `Reindex`
   - `Remove from index`
+- Add a bulk action button near the list summary that indexes only the current loaded result set for the active filter and active search.
 
 ### Secondary goals
 
@@ -46,7 +47,7 @@ Users can currently index or delete the AI/RAG index only from inside an individ
 ### Non-goals
 
 - Replacing the existing per-note `RagIndexPanel` entry points.
-- Bulk actions on multiple notes in MVP.
+- A whole-workspace "index every note" action that ignores pagination, loaded state, or active search results.
 - Editing note content from the AI Index page.
 - ~~Mobile-specific AI Index screen beyond preserving responsive Settings behavior.~~ (Resolved: mobile AI Index screen is now in scope and implemented.)
 - Automatic reindex on note save.
@@ -58,6 +59,7 @@ Users can currently index or delete the AI/RAG index only from inside an individ
 - As a user, I want to filter to `Not indexed` notes so I can decide what should enter the AI index.
 - As a user, I want to reindex an outdated or already indexed note without opening it first.
 - As a user, I want to remove a note from the AI index from the same list view.
+- As a user, I want one bulk button that indexes only the notes currently loaded in the visible AI Index list, so search and filters naturally limit its scope.
 
 ### Status rules
 
@@ -81,6 +83,12 @@ Users can currently index or delete the AI/RAG index only from inside an individ
   - search starts after 3 characters
   - matching should follow the ordinary note search path (`FTS` first, then substring fallback)
 - The default sort order is descending by note `updated_at` so the most recently changed notes are reviewed first.
+- The bulk action must use the same narrowed list the user is looking at:
+  - only notes from the active filter and active committed search query are eligible
+  - only notes already loaded into the current infinite list are eligible
+  - notes on later, not-yet-loaded pages must not be indexed
+  - notes excluded by search must not be indexed
+  - already indexed notes may stay visible in `All notes`, but the bulk action should skip them rather than reprocessing them unless they are `Outdated`
 
 ## Success Criteria
 
@@ -91,6 +99,8 @@ Users can currently index or delete the AI/RAG index only from inside an individ
 - [ ] Search query changes reload AI index data without breaking pagination or virtualization.
 - [ ] Each row shows `title`, computed status, and `last indexed at` when available.
 - [ ] `Index`, `Reindex`, and `Remove from index` actions are available according to row state.
+- [ ] A bulk button is available in the AI Index summary/header area on web and mobile when the current loaded result set contains actionable notes.
+- [ ] The bulk button affects only the currently loaded notes that match the active filter and active committed search query.
 - [ ] After an action completes, the affected row reflects the new status without leaving the page.
 - [ ] `Outdated` status is computed from actual note update time versus latest index time.
 - [ ] The implementation does not directly reuse `NoteCard` or the existing notes/search controller flow.
@@ -103,6 +113,7 @@ Users can currently index or delete the AI/RAG index only from inside an individ
 - Existing `rag-index` Edge Function remains the source of truth for index/delete/reindex actions.
 - Browser-side reads of `note_embeddings` are limited by RLS and are awkward for server-side status filtering at scale.
 - Status filtering must remain performant for large note sets and should not require fetching the full workspace into the browser first.
+- The bulk action should reuse the existing single-note `rag-index` mutation path rather than introducing a whole new backend bulk API for this refinement.
 
 ### Assumptions
 
@@ -121,6 +132,7 @@ The web AI Index page solved the desktop experience. Mobile users on the React N
 - Add an `AI Index` tab to the mobile Settings screen (`ui/mobile/app/(tabs)/settings.tsx`).
 - Reuse the same backend RPC (`get_ai_index_notes`) and Edge Function (`rag-index`) — no new server work.
 - Provide the same filter chips (All / Indexed / Not indexed / Outdated), search input, and per-note actions (Index / Reindex / Update index / Remove index).
+- Provide the same summary-area bulk action on mobile, with identical "loaded notes only" and "respect active search/filter" semantics.
 - Use `FlatList` with pull-to-refresh and infinite scroll (not `react-window` — React Native).
 - Follow mobile UI patterns: `StyleSheet.create`, `useTheme()`, `memo()`, `Toast.show()`.
 
@@ -144,6 +156,7 @@ The web AI Index page solved the desktop experience. Mobile users on the React N
 - [x] Search input filters notes with debounce (300ms, 3-char minimum).
 - [x] Each card shows title, status badge, status description, and action buttons.
 - [x] Actions call `rag-index` and show toast on success/error.
+- [x] A bulk button appears in the summary area and processes only the currently loaded, search-filtered mobile cards that still need indexing.
 - [x] Pull-to-refresh and infinite scroll work correctly.
 - [x] Loading, empty, and error states are handled.
 - [x] 21 unit tests cover the hook, card, and panel components.

docs/ai/testing/feature-ai-index-page.md

@@ -43,6 +43,9 @@ description: Test strategy for the Settings AI index page and its dedicated data
 - [x] Updates row status/buttons optimistically on `All notes` immediately after a successful AI-index mutation
 - [x] Animates rows out of filtered views when a successful mutation changes them out of the active status bucket
 - [x] Treats semantic `rag-index` skips such as `outcome: "skipped", reason: "too_short"` as honest failures and restores `not_indexed`
+- [x] Exposes a summary-level `Index loaded notes` button only when the current loaded result set contains actionable rows
+- [x] Ensures the web bulk action processes only the currently loaded notes from the active filter and active committed search query
+- [x] Ensures the mobile bulk action uses the same loaded-only scope and skips already indexed rows
 
 ## Integration Tests
 
@@ -77,9 +80,12 @@ description: Test strategy for the Settings AI index page and its dedicated data
   - `npm run test:unit:core -- --runTestsByPath core/tests/unit/core-rag-indexResult.test.ts`
   - `npm run test:component -- --spec "cypress/component/features/settings/AIIndexNoteRow.cy.tsx"`
 - Completed:
+  - `npm run test:unit:web -- --runTestsByPath ui/web/tests/unit/components/aiIndexTab.test.tsx` (bulk button visibility, loaded-only scope, search-limited scope)
+  - `cd ui/mobile && npx jest tests/component/aiIndexPanel.test.tsx --no-coverage` (mobile bulk button visibility and loaded-only scope)
   - `npm run type-check`
   - `npm run type-check:tests`
   - `npx eslint ui/web/components/features/settings/AIIndexTab.tsx ui/web/components/features/settings/AIIndexList.tsx ui/web/components/features/settings/AIIndexNoteRow.tsx ui/web/tests/unit/components/aiIndexNoteRow.test.tsx ui/web/tests/unit/components/aiIndexTab.test.tsx`
+  - `cd ui/mobile && npm run validate`
   - Browser QA in local Next dev server via Playwright: desktop auth-skip flow, `Settings -> AI Index`, empty-state flow, row open, browser back return, and mobile viewport snapshot review
 
 ## Manual Testing
@@ -89,6 +95,8 @@ description: Test strategy for the Settings AI index page and its dedicated data
 - Verify timestamps and status badges are understandable
 - Verify opening a note from `Settings -> AI Index`, then using browser back and mobile in-note back to return to the same filtered/scrolled AI Index view
 - Verify the page still feels usable when there are only a few notes and when the current filter/search returns nothing
+- Verify the bulk button does not appear for fully indexed loaded results
+- Verify search limits the bulk action scope so notes outside the committed query are not indexed
 
 ## Performance Testing