Feature set 132.

[jackfperryjr]

Games get artwork — a full logo and a square thumbnail

Games were the one catalogue entity with no picture. They now carry two, and both are editable, uploadable and served.

Two crops, not two sizes. The full logo is the wide lockup with the title text; the thumbnail is the square emblem, artwork alone. Resizing one into the other doesn't work — the full lockup is mostly text, which is illegible and badly proportioned wherever a square is wanted. So they're separate columns, and clients pick by shape rather than by resolution.

imageUrl	full logo → games/{id}.webp
thumbnailUrl	square emblem → thumb/games/{id}.webp

Keys follow the bucket layout already in use, so thumb/games/7.webp sits beside gen/monsters/12.webp.

No generated slot

Generation selects monsters and characters only. Art parked at gen/games/{id}.webp would be promoted by nothing and served by nothing, so the API refuses that combination outright rather than accepting an upload into a dead column.

Enforcing it turned the upload endpoint's flat Resources and Slots lists into a per-resource map — characters and monsters take original|generated, games take original|thumbnail. My first pass was a shared list plus an if (resource == "games" && slot == "generated") exception; that was going to rot at the next shape, so it's a map now.

The dashboard had the same problem in three places: the art panel, the zoom modal, and the create-form's hidden inputs all assumed exactly two fixed slots. Slots are now per tab, and a tab marks which one the table thumbnail should prefer — the square one for games, the generated one for everything else, which preserves existing behaviour.

Migration

One clean AddGameImages adding three nullable columns. The AddGameImage from the previous round never shipped, so it's regenerated rather than stacked. Migrations apply on startup, so the deploy handles the schema.

Notes

• 324/324 pass, dotnet format clean.
• X-2 and XIII-2 have no game rows. The catalogue is I–XVI; uploads are addressed by row id, so those need creating in the dashboard first. They'd land at ids 17/18.
• Adding those two would also make "all 16 mainline titles" wrong in the README. Left alone deliberately — that's a catalogue-scope decision, not part of this change.

🤖 Generated with Claude Code