How would you model a set of related but distinct API response shapes so the compiler forces you to handle every case, including a new one added later?

The illustrated walkthrough is behind sign-in.

Every prompt in the library is public. Any free InterviewOS account unlocks the diagram, the model answer, and the self-check.