Multiple bug fixes.

CLAUDE.md

@@ -298,10 +298,10 @@ All generation routes use the background job queue. Frontend polls:
 Image retrieval is handled server-side by the `_make_finalize()` callback; there are no separate client-facing finalize routes.
 
 ### Utilities
-- `POST /set_default_checkpoint` — save default checkpoint to session
-- `GET /get_missing_{characters,outfits,actions,scenes}` — AJAX: list items without cover images
+- `POST /set_default_checkpoint` — save default checkpoint to session and persist to `comfy_workflow.json`
+- `GET /get_missing_{characters,outfits,actions,scenes,styles,detailers,looks,checkpoints}` — AJAX: list items without cover images (sorted by display name)
 - `POST /generate_missing` — batch generate covers for all characters missing one (uses job queue)
-- `POST /clear_all_covers` / `clear_all_{outfit,action,scene}_covers`
+- `POST /clear_all_covers` / `clear_all_{outfit,action,scene,style,detailer,look,checkpoint}_covers`
 - `GET /gallery` — global image gallery browsing `static/uploads/`
 - `GET/POST /settings` — LLM provider configuration
 - `POST /resource/<category>/<slug>/delete` — soft (JSON only) or hard (JSON + safetensors) delete
@@ -321,6 +321,11 @@ Image retrieval is handled server-side by the `_make_finalize()` callback; there
 - Context processors inject `all_checkpoints`, `default_checkpoint_path`, and `COMFYUI_WS_URL` into every template.
 - **No `{% block head %}` exists** in layout.html — do not try to use it.
 - Generation is async: JS submits the form via AJAX (`X-Requested-With: XMLHttpRequest`), receives a `{"job_id": ...}` response, then polls `/api/queue/<job_id>/status` every ~1.5 seconds until `status == "done"`. The server-side worker handles all ComfyUI polling and image saving via the `_make_finalize()` callback. There are no client-facing finalize HTTP routes.
+- **Batch generation** (library pages): Uses a two-phase pattern:
+  1. **Queue phase**: All jobs are submitted upfront via sequential fetch calls, collecting job IDs
+  2. **Poll phase**: All jobs are polled concurrently via `Promise.all()`, updating UI as each completes
+  3. **Progress tracking**: Displays currently processing items in real-time using a `Set` to track active jobs
+  4. **Sorting**: All batch operations sort items by display `name` (not `filename`) for better UX
 
 ---