Apr 14
Multiple size/paper combos....
**Concept:** Replace the current "paper on profile + unbounded list of offered sizes" model with **up to 3 print configurations**, where each configuration is a full combo of size + paper manufacturer + paper type + paper weight (e.g. Letter / Canson Baryta Prestige 340, A3+ / Hahnemühle Photo Rag 308, 4×6 / Red River Aurora White 300). Trade proposals pick one of these configurations instead of just a size.
**Context:** Today the profile holds one paper setup and an open-ended list of sizes — so a member who prints 4×6 on Aurora White and A3+ on Photo Rag has to pretend it's all the same paper. Editions already lock size+paper per edition, which works. This proposal brings that same clarity to regular trades: what you offer is always a real, printable combo, never a misleading cross-join of every size × one paper.
**Why it matters for trade quality:** Partners see exactly what they'd receive. No more "you said 4×6 but your paper is 340gsm baryta, is that right?" confusion. It also nudges members toward deliberate offerings over everything-everywhere lists.
**Migration considerations (this is the hard part):**
- Today's data is `user.paper_*` (one row) + `participant_sizes` (N rows). We'd need to collapse these into up to 3 configuration rows per user.
- **Users with ≤3 sizes:** auto-migrate by pairing each offered size with their existing paper. Clean.
- **Users with >3 sizes:** have to pick. Options: (a) auto-keep the first 3 and flag them to review, (b) block them out of trades until they choose 3, (c) grandfather in more than 3 for existing users but cap new configs at 3. Leaning toward (a) with a dashboard nudge — least disruptive.
- **In-flight exchanges** referencing a dropped size need a fallback — probably freeze the size on the exchange record so it doesn't un-reference.
- Admin edit screens, the directory size filter, and the exchange proposal form all change shape.
**Why 3 and not more:** Caps choice paralysis for trade partners and keeps profile pages scannable. If heavy-lister demand emerges, 3 can become 5 without another schema change.
Completed