宜博 / h3livestream

POST /api/admin/batch-gen takes {characterId, garmentIds[],
refDanceVideoIds?[]}, expands to one job per garment (cross-producted
with refDanceVideoIds when given, else one random active dance-ref per
garment like the single-generate default), and submits each through
the same submitGeneration() helper the single POST /api/admin/generate
route now uses — so the M.7 dedupe cache (existing characterId+
garmentId combo) is honored per combo, not just per batch.
GET /api/admin/batch-gen/status?batchId= returns that batch's
generationJobs records for progress polling.

admin-batch-gen.html: pick one character, multiple garments, and
optionally pin specific reference dances; submits the batch, polls
status every 3s into a progress table, and lets failed rows be
retried individually via POST /api/admin/generate. Linked from the
other admin pages' nav.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Table + inline edit + add-form pages matching admin.html's existing
conventions, wired to the T3-T5 CRUD API and T2's upload endpoints.
Cross-linked with admin.html and each other in the topbar.

No browser tooling available in this environment to render/click
through these, so admin-pages-flow.test.js exercises the exact API
call sequence each page's JS performs (login -> upload a real file ->
create with the returned URL -> list -> confirm the shape the table
renders), which is where a field-name mismatch would surface.