[mlhiter]

Summary

Allow Sealox clients to use release-v5.1 by exposing the public storage-limit configuration endpoint and accepting mysql in database creation requests.
Normalize the alias to release's internal MySQL handling while retaining native MySQL version discovery, legacy ApeCloud requests, account creation, and automatic backups.
Document the compatibility boundary and add regression coverage.

Validation

• Passed: node --test tests/test_sealox_compatibility.cjs (8 tests), pnpm --dir release-v5.1/database typecheck, and git diff --check
• Kubernetes and backup writes mocked; live cluster and browser integration not tested

Sequence Diagram

sequenceDiagram
    participant Client as Sealox
    participant API as Release API
    participant Service as Creation service
    participant K8s as Kubernetes
    Client->>API: GET getClientAppConfig
    API-->>Client: storageMaxSize
    Client->>API: POST databases with type mysql
    API->>Service: Validated creation request
    alt Version omitted
        Service->>K8s: Read ClusterVersions
        K8s-->>Service: Native MySQL versions
    end
    Service->>Service: Normalize internal engine and select template
    Service->>K8s: Apply database, account, and backup resources
    API-->>Client: 201 creating

Loading