API schema update — July 14, 2026

The root swagger.json was replaced with the latest development export supplied by the backend team. The API title now identifies the contract as ZennoHosting API (DEV); the documented runtime base URL and OAuth2 security flow are unchanged.

Added endpoints

• Account locale: PUT /v1/account/locale.
• Notifications: feed, read state, unread count, and delivery preferences under /v1/notifications.
• Project operations: list and detail endpoints under /v1/projects/{projectId}/operations.
• Project rename: PATCH /v1/projects/{projectId}/rename.
• VM metrics, resize, and rebuild endpoints.
• Sale renewal cancellation and resumption endpoints.
• Administrative saga inspection, finalization, and forced compensation endpoints under /v1/admin/sagas.

Removed or changed endpoints

• PATCH /v1/projects/{projectId} was replaced by PATCH /v1/projects/{projectId}/rename. Clients must update the request path and use RenameProjectRequest.
• Existing resources received updated request, response, validation, and pagination metadata.

Schema changes

The contract adds notification, operation-tracking, VM metrics/resize/rebuild, resource-count, locale, validation-problem, and saga-administration models. The generic Operation and OperationStatus models were replaced by OperationResponse and ApiOperationStatus. Network, public-IP, and VM paged response model names were normalized.

Security and migration notes

The global OAuth2 requirement is unchanged. Administrative saga endpoints should only be exposed to authorized operational tooling. Clients should regenerate API types, update the project rename path, and review renamed operation and paged-response models before upgrading.