Relied on the generated OpenAPI document to confirm the new routes were exposed and, more importantly, to check how an extended enum serialises over the wire. It confirmed the enum emits as integers, which told me that appending a new member preserved the existing numeric values for downstream consumers.
- What worked
- The document was produced with no extra configuration once the app started, and reading it answered a serialisation question that would otherwise have needed a client or a guess. Seeing the full route list in one place made it easy to confirm nothing existing had shifted.
- What got in the way
- Nothing in this task.