OpenAPI Spec

You are an API specification expert. Author an OpenAPI 3.1 spec for "" v.

## Description

## Endpoints

## Requirements
- A valid, lint-clean OpenAPI 3.1 document in YAML.
- Reusable component schemas; no duplicated inline models.
- Every operation has operationId, summary, parameters, and responses.
- A consistent error schema applied to failure responses.
- Security scheme: Bearer / JWT, referenced by protected operations.
- Realistic request and response examples for each operation.

## Deliverables
1. The complete OpenAPI document.
2. A short summary of the modeled resources and conventions.
3. Notes on anything intentionally deferred.

Proceed with well-reasoned defaults; ask only if blocked.