📜 Task breakdown notes:

• T328464: 📜 Add the `GET /entities/items/{item_id}/descriptions` route to our OpenAPI definition
• T328461: 📜 Create `Description` and `Descriptions` ReadModel classes
• T328466: 📜 Implement ItemDescriptionsRetriever using a TermLookup
  • Create an ItemDescriptionsRetriever interface with a getDecriptions( ItemId $itemId ): ?Descriptions; method
  • Rename TermLookupItemLabelsRetriever to TermLookupItemDataRetriever
  • Implement the ItemDescriptionsRetriever interface in the TermLookupItemDataRetriever
• T328462: 📜 Implement `GetItemDescriptions` use case happy path
  • Create and return a success response with the revision metadata and data from the ItemDescriptionsRetriever
• T328468: 📜 Create a `DescriptionsSerializer`
  • Extract from ItemDataSerializer
  • Use it in the ItemDataSerializer once done
• T328463: 📜 Create Route handler (happy path only)
  • Same middlewares as GetItemLabelsRouteHandler
  • Calls json_encode on the serializer result
  • Add e2e tests
• T328469: 📜 Validate request in use case
  • Use the existing ItemIdValidator but create a dedicated use case validator
  • Create UseCaseErrorException (in the UseCases dir )
  • Throw UseCaseErrorException if item id is invalid
    • We decided it was okay to use the ErrorResponse error code constants in the UseCaseException for now as it doesn't cause an onion violation
• T328467: 📜 Catch `UseCaseErrorException` in route handler
  • Update the ErrorResponseToHttpStatus lookup class
    • Rename ErrorResponseToHttpStatus to UseCaseErrorToHttpStatus
    • Rename the lookup() method to lookupErrorResponse()
    • Add a lookupException( UseCaseErrorException $e ): int method
  • Create a new ExceptionJsonPresenter (similar to ErrorJsonPresenter)
  • Add a ResponseFactory::newErrorResponseFromException(Exception $e): Response method that uses the new ExceptionJsonPresenter class and UseCaseErrorToHttpStatus::lookupException() method
  • Add e2e tests
• T328471: 📜 Return appropriate response if the item is a redirect or does not exist
  • Create an ItemRedirectException (in the UseCases dir)
  • Throw ItemRedirectException or UseCaseErrorException in the use case if the item is a redirect or does not exist
  • Catch UseCaseErrorException and ItemRedirectException in the route handler and return appropriate response
  • Add e2e tests
• T328470: 📜 Write spec tests for `GET /entities/items/{item_id}/descriptions`

Outstanding decisions:

• Should UseCaseErrorException and ItemRedirectException extend Exception or LogicException? Should these extend our own base exception class?

looks all good - thank you and well done!