feat(media): pagination

features/media_upload_selection_duplicates.feature

@@ -10,13 +10,16 @@ Feature: Media page, part 2: upload, selection and duplicates
       DashboardShell, per docs/design/routes.md and docs/design/screens/media.md
     And this slice is SPA only: the API from slice A is used unchanged, and no Go code, use case
       or repository changes
+    And this slice is amended by features/media_pagination_screen.feature: "Select all" covers the
+      images of the current page only, the Duplicates tab loads the whole set at size=100 page after
+      page until the loaded count reaches total, and hash lookups send page=1&size=100
     And this slice supersedes these B1 statements: the Upload button, the mobile pinned button and
       "Upload an image" are enabled; the Duplicates tab is enabled and ?filter=duplicates is a
       valid value; "Review duplicates" is enabled; Space on a card toggles selection; the checkbox,
       the "Select all" text and the partial state exist; the B2 states no longer carry
       skip 'pending' in web/visual/states.ts
     And the calls used are POST /v1/media/ (multipart field "file", sent with XMLHttpRequest so
-      that upload progress is reported, with the jwt cookie), GET /v1/media/?hash=<sha256 hex>,
+      that upload progress is reported, with the jwt cookie), GET /v1/media/?hash=<sha256 hex>&page=1&size=100,
       DELETE /v1/media/{id}, POST /v1/media/merge { keep_id, merge_ids } and the list call from
       B1 with filter=duplicates; every other /v1 call goes through useApi
     And 401 and 403 on any of these calls, including the XHR upload, send the user to
@@ -130,7 +133,7 @@ Feature: Media page, part 2: upload, selection and duplicates
     Scenario: A row whose content already exists
       Given the user chooses "floorboards-2.jpg" (2.4 MB, valid)
       When the SHA-256 of the file is computed
-      Then GET /v1/media/?hash=<that hex> is sent before any POST
+      Then GET /v1/media/?hash=<that hex>&page=1&size=100 is sent before any POST
       And when it resolves 200 with the image "floorboards.jpg" (id 12, uploaded 14 Jun 2026 by Inès Duarte)
       Then the row shows "Already in your library", the text `Same as "floorboards.jpg", uploaded 14 Jun 2026 by Inès Duarte.`, and the buttons "Use existing" and "Upload anyway"
       And nothing is sent with POST /v1/media/ for it, and its concurrency slot is released
@@ -146,7 +149,7 @@ Feature: Media page, part 2: upload, selection and duplicates
       And the image "floorboards.jpg" is selected, the bulk bar reads "1 selected", and the page announces "floorboards.jpg selected, 1 selected"
 
     Scenario: Use existing when the image is not in the loaded list
-      Given the existing image is not in the loaded list because of the search, the tab or the 100 limit
+      Given the existing image is not in the loaded list because of the search, the tab or the current page
       When the user activates "Use existing"
       Then the search and the tab reset to All and the image is selected
       And if it is still not loaded the row is dropped without selecting
@@ -275,7 +278,7 @@ Feature: Media page, part 2: upload, selection and duplicates
       When 3 images are selected
       Then that checkbox shows the partial state
       When the user activates it while it is partial
-      Then all 12 loaded images are selected and it shows checked
+      Then all 12 images of the current page are selected and it shows checked (never the other pages)
       When the user activates it while it is checked
       Then the selection is emptied
       And in list view at md width or more the table header checkbox does the same; the mobile card list has no "Select all" row and is selected through its 44 px row checkboxes
@@ -358,13 +361,13 @@ Feature: Media page, part 2: upload, selection and duplicates
     Scenario: The Duplicates tab is enabled
       Given the Default state has loaded
       When the user selects the "Duplicates 2" tab
-      Then the URL gains ?filter=duplicates and the list is requested with filter=duplicates and limit=100
+      Then the URL gains ?filter=duplicates and the list is requested with filter=duplicates at size=100, page 1, 2, ... until the loaded count reaches total
       And the tab is selected, and "Duplicates" carries the info-tinted count of groups
       And opening /media?filter=duplicates lands on the same view, and "Review duplicates" in the detail panel of "floorboards.jpg" is enabled and selects this tab
       And search applies, the sort menu and the view toggle show as on the other tabs, sort is sent with the request, and the view toggle has no effect on the groups view while the grid or list preference stays in the URL
 
     Scenario: Duplicates, groups
-      Given GET /v1/media/?filter=duplicates&sort=newest&limit=100 resolves 200 with ids 5, 6, 7, 9 and 12
+      Given GET /v1/media/?filter=duplicates&sort=newest&page=1&size=100 resolves 200 with ids 5, 6, 7, 9 and 12
       When the user opens the Duplicates tab
       Then the images are grouped by sha256 into 2 bordered cards stacked with a 16 px gap, the group with the oldest suggested copy first
       And group 1 has the header "Group 1" over "3 identical images · 2.4 MB each · 3600 × 2400", and group 2 has "Group 2" over "2 identical images · 3.1 MB each · 3600 × 2400"