a gallery is a carousel

It always rendered as one — data-carousel, a snap track, two arrows, driven by
carousel.client.js. The entity was the last thing still calling it something
else, and that collided with the site's own Gallery section: two nav rows
reading Gallery and Galleries, meaning a list of objects and a list of
photograph sets.

GalleriesPanel, GalleryPicker and GalleryItems become Carousels*, the endpoint
becomes /fofos-admin/carousels, the block kind becomes carousel and
subject-gallery becomes subject-carousel. The publish allowlist follows the
renamed tables.

What did NOT move: GALLERY_CONFIG at /fofos-admin/gallery, subjects.ts's
base '/gallery', and home_gallery_media. Those are the Gallery section and the
legacy rows, and both are correct.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

web/file-actions.ts

@@ -29,8 +29,8 @@ const relativeTo = (path: string): string | null => {
 
 export const fileActions: FileAction[] = [
   {
-    key: 'fofos-admin:create-gallery',
-    label: 'Create Gallery',
+    key: 'fofos-admin:create-carousel',
+    label: 'Carousel from folder',
     icon: Images,
     /*
       A folder, or any number of files — both are ways of saying "these, in this order".
@@ -76,10 +76,10 @@ export const fileActions: FileAction[] = [
         paths = body.files;
       }
       /*
-        Handed over in the URL, and the Galleries panel does the asking.
+        Handed over in the URL, and the Carousels panel does the asking.
 
         The action has no dialog of its own on purpose: naming a gallery, seeing the slug it will get
-        and watching the items land belongs on the screen that owns galleries, not in a modal over a
+        and watching the items land belongs on the screen that owns carousels, not in a modal over a
         file browser that would then have to explain where the result went.
       */
       // The section is a PATH now, so this names it rather than editing the current query. `create` and
@@ -87,7 +87,7 @@ export const fileActions: FileAction[] = [
       const params = new URLSearchParams();
       params.set('create', entries.length === 1 && entries[0]!.type === 'directory' ? entries[0]!.name : '');
       params.set('from', paths.join('\n'));
-      window.history.pushState({}, '', `${href('galleries')}?${params.toString()}`);
+      window.history.pushState({}, '', `${href('carousels')}?${params.toString()}`);
       // The router listens for this; pushState alone does not notify it.
       window.dispatchEvent(new PopStateEvent('popstate'));
     },