[TheBlackSide243]

Description

Several photos per item, with what each one shows, plus accessory sections and photos that are never cropped.

• Several photos per item. An item can have up to 10 photos (MAX_ITEM_PHOTOS).
  • Each photo can be labelled front, back, detail or other.
  • The labels live in a new item_photo_views table. It is keyed by the photo's file, so a label follows the photo when it becomes or stops being the cover.
  • Nothing is added to clothing_items.
  • The gallery shows the labels, and a card shows the back on hover.
  • The photo manager can add, reorder, label, delete and set the cover. Changing the cover is refused (409) while a photo is still being processed.
• Background removal on every photo.
  • Each photo has its own job on the image worker, with its own state and backup: item_images.status, original_image_path and processing_started_at, added by migration a4c6e8f0b2d3.
  • Uploads, the item's "Remove background" button and the bulk action clean all the photos, not only the cover.
  • Each photo can be redone or restored on its own.
  • The single-item removal now runs in the image worker instead of the API process. Before, it kept a second copy of the segmentation model in the API's memory.
• Garments shown whole. Item photos use a shared garment-fit class (contain, centred) instead of object-cover. Trouser legs, sleeves and long dresses are no longer cut off.
• Accessories and categories.
  • New types: ring, necklace, watch, bracelet and earrings.
  • A category filter on the wardrobe page: tops, bottoms, outerwear, shoes, accessories and others.
  • A category breakdown in analytics.
• Palette. A softer palette with category, success, warning and info tokens.
• Image worker resources.
  • rembg's CPU threads are capped with BG_REMOVAL_THREADS, default 2.
  • The model is freed after BG_REMOVAL_IDLE_SECONDS without photos, default 600.

Depends on #277 and #278. Both are merged into this branch, so the diff includes them until they land. Review those two first.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• CI/CD or build changes

Checklist

• I have read the CONTRIBUTING guide
• My code follows the project's coding style
• I have added tests that prove my fix/feature works
• New and existing tests pass locally
• I have updated documentation as needed
• My changes don't introduce new warnings or errors

Testing

• Backend (on top of current main plus feat: remove the background while uploading #277 and feat: more accurate background removal for clothes #278):
  • ruff check and ruff format --check;
  • the migration heads check;
  • the full pytest suite.
• Frontend:
  • npm run lint, i18n:check and tsc --noEmit;
  • vitest.
• By hand on my own instance (Docker Compose on TrueNAS):
  • an item with front and back photos;
  • background removal on every photo, then restoring one;
  • changing the cover and deleting one photo;
  • a ring tagged as an accessory;
  • full-length trousers shown without cropping.

Test Environment

• Docker Compose
• Kubernetes
• Local development

🤖 Generated with Claude Code

[sourcery-ai]

Sorry @TheBlackSide243, your pull request is larger than the review limit of 150,000 diff characters