Issue #236 closed: Bundled OpenAPI spec is stale: scheduled-tasks, storages, and database-envs endpoints are missing

What

docs/coolify-openapi.yaml no longer reflects the API surface the client actually uses. Endpoints called by src/lib/coolify-client.ts that are absent from the bundled spec:

• /{applications|services}/{uuid}/scheduled-tasks* (all of them — the spec only documents database backup schedules)
• storages endpoints used by the storages tool
• /databases/{uuid}/envs*

This matters because the spec doubles as the ground truth for "does Coolify support X" decisions — e.g. determining whether a scheduled-task trigger endpoint exists (it doesn't, but proving that required grepping the client too), and for keeping search_docs / gotchas docs honest.

There's an openapi-drift.yml CI workflow — it evidently isn't catching this direction of drift (client-uses-endpoint-not-in-spec). Worth checking what it actually compares.

Suggested fix

1. Refresh docs/coolify-openapi.yaml from the current Coolify release.
2. Extend the drift check to fail when coolify-client.ts calls a path not present in the spec (a simple route-string extraction against the spec's path list would do).

Acceptance

• Spec contains every path the client calls.
• CI fails if a future client method references an unspecced path.