Connect Schedule UI to native deployments

[heimanba]

What changed

• complete native deployment lifecycle support for Qoder and Claude
• add server REST endpoints for listing, creating, pausing, resuming, running, and deleting deployments
• connect the WebUI Schedule center to the real server API
• persist provider ownership and serialize deployment store mutations
• preserve current prompt/playbook and supported cron presets when opening Schedule
• update the committed OpenAPI contract and generated WebUI types

Why

The Schedule UI previously displayed static data and did not reach provider deployment services. The server also lacked a deployment API surface. During review, failed provider actions, provider switching, concurrent writes, and stale remote records were found to desynchronize config, state, and remote resources.

Impact

Users configured with Qoder or Claude can now create and manage native scheduled deployments end to end from the WebUI. Individual unavailable deployments degrade gracefully without blocking the entire list.

Validation

• repository push verification profile passed
• all workspace typechecks passed
• architecture dependency and semantic checks passed
• SDK: 601 tests passed
• WebUI: 126 tests passed
• Server: 67 tests passed
• real Qoder create → list → run → delete smoke test passed