Get Item

Read view of a stored item.

The constrained fields from ItemBase are redeclared here without their limits on purpose. ItemBase exists to validate incoming writes, but ItemRead validates rows that already exist, and those rows are also written by the Next.js app straight through Prisma, which enforces none of these limits. Inheriting them made pydantic reject legacy rows on read, so GET /v1/items/{id} answered 500 for every item whose stored description was longer than the create/update cap. CharacterRead has always relaxed its own text fields for this reason; these types had not.