Get Location

Read view of a stored location.

The constrained fields from LocationBase are redeclared here without their limits on purpose. LocationBase exists to validate incoming writes, but LocationRead 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/locations/{id} answered 500 for every location 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.