Declare the schedule lifecycle as abstractmethods on SchedulerClient

pause/resume/delete/run_now/preview_next/reconcile join the ABC as bare
@AbstractMethod declarations, same style as the endpoint methods — the
lifecycle is part of the SchedulerClient contract again, with the
implementation on OrkesSchedulerClient. get_scheduler_client() returns to
the -> SchedulerClient annotation. Guard test now pins abstract-on-ABC /
concrete-on-Orkes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Kowser

CHANGELOG.md

@@ -11,7 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Canonical metrics mode: opt-in harmonized metric surface via `WORKER_CANONICAL_METRICS=true` -- [details](METRICS.md#detailed-technical-notes--unreleased)
 - `MetricsSettings` gains `clean_directory` and `clean_dead_pids` for opt-in stale `.db` file cleanup (both default to `False`)
-- `OrkesSchedulerClient` now carries the schedule lifecycle operations itself: `pause(reason=)`, `resume`, `delete`, `run_now`, `preview_next`, `reconcile` (declarative tri-state sync) — with typed errors (`ScheduleNotFound`, `InvalidCronExpression`, ...). `pause_schedule` gains an optional `reason=` (stored by OSS Conductor servers; ignored by Orkes servers)
+- `SchedulerClient` now carries the schedule lifecycle operations itself: `pause(reason=)`, `resume`, `delete`, `run_now`, `preview_next`, `reconcile` (declarative tri-state sync) — with typed errors (`ScheduleNotFound`, `InvalidCronExpression`, ...). `pause_schedule` gains an optional `reason=` (stored by OSS Conductor servers; ignored by Orkes servers)
 
 ### Changed
 
@@ -23,7 +23,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Removed
 
-- **Breaking:** `AgentScheduleClient` (alias `ScheduleClient`) and `OrkesClients.get_agent_schedule_client()` are removed with no compatibility shim — `OrkesSchedulerClient` (via `OrkesClients.get_scheduler_client()`) is the one schedule client and carries the full lifecycle itself. Replace `AgentScheduleClient(scheduler_client, workflow_client)` constructions with `get_scheduler_client()`; `runtime.schedules_client()` and `AgentClient.schedules` now return that client directly (same methods, same shared instance)
+- **Breaking:** `AgentScheduleClient` (alias `ScheduleClient`) and `OrkesClients.get_agent_schedule_client()` are removed with no compatibility shim — `SchedulerClient` (via `OrkesClients.get_scheduler_client()`) is the one schedule client and carries the full lifecycle itself. Replace `AgentScheduleClient(scheduler_client, workflow_client)` constructions with `get_scheduler_client()`; `runtime.schedules_client()` and `AgentClient.schedules` now return that client directly (same methods, same shared instance)
 
 ### Fixed
 

docs/SCHEDULE.md

@@ -43,7 +43,7 @@ Operations for controlling schedule execution state.
 
 ## Schedule Lifecycle Helpers
 
-Beyond the endpoint methods above, `OrkesSchedulerClient` carries higher-level lifecycle
+Beyond the endpoint methods above, `SchedulerClient` carries higher-level lifecycle
 operations (shared with the agents layer). They raise typed errors
 (`ScheduleNotFound`, `InvalidCronExpression`, `ScheduleNameConflict` from
 `conductor.client.ai.schedule_errors`) instead of raw `ApiException`.

docs/agents/advanced.md

@@ -127,7 +127,7 @@ with AgentRuntime() as runtime:
 Key methods: `run`/`run_async`, `start`/`start_async`, `deploy`/`deploy_async`,
 `schedule(agent, schedules)`, `get_status`, `respond`, `stop`, `signal`,
 `stream_sse`, and `.schedules` (the schedule lifecycle — `pause`/`resume`/`delete`/
-`run_now`/`preview_next`/`reconcile`, now carried by `OrkesSchedulerClient` itself). Both
+`run_now`/`preview_next`/`reconcile`, now carried by `SchedulerClient` itself). Both
 sync and async forms exist. Most users call `runtime.run/start/deploy` instead,
 which add local-worker management on top of this client.
 

docs/agents/api-reference.md

@@ -46,7 +46,7 @@ Context manager (sync and async: `with` / `async with`).
 | `signal` | `(execution_id, message) -> None` | Inject persistent context |
 | `shutdown` | `() -> None` | Stop all workers |
 | `client` (property) | `-> AgentClient` | Control-plane client |
-| `schedules_client` | `() -> OrkesSchedulerClient` | Shared schedule client |
+| `schedules_client` | `() -> SchedulerClient` | Shared schedule client |
 
 Async variants exist for status/respond/approve/reject/send/stop/shutdown
 (`*_async`). Module-level wrappers using a singleton runtime: `run`, `run_async`,
@@ -190,7 +190,7 @@ start_at=None, end_at=None, description=None)` — `cron` is a 5- or 6-field exp
 `ScheduleInfo` (read model) fields include `name`, `short_name`, `agent`, `cron`,
 `timezone`, `input`, `paused`, `catchup`, `next_run`, `create_time`, `update_time`, ...
 
-The schedule lifecycle lives on `OrkesSchedulerClient` itself (via
+The schedule lifecycle lives on `SchedulerClient` itself (via
 `runtime.schedules_client()`, `runtime.client.schedules`, or
 `OrkesClients.get_scheduler_client()`):
 
@@ -284,7 +284,7 @@ The control-plane client (formerly `AgentHttpClient`, alias kept). Reach it via
 | `stop` | `(execution_id) -> None` | |
 | `signal` | `(execution_id, message) -> None` | |
 | `stream_sse` | `(execution_id) -> AsyncIterator[dict]` | |
-| `schedules` (property) | `-> OrkesSchedulerClient` | |
+| `schedules` (property) | `-> SchedulerClient` | |
 | `close` | `() -> None` (async) | |
 
 Lower-level endpoint methods (`start_agent`, `deploy_agent`, `compile_agent`) are also

e2e/test_suite21_scheduling.py

@@ -33,7 +33,7 @@
     ScheduleNameConflict,
 )
 from conductor.client.ai.schedule import _from_workflow_schedule
-from conductor.client.orkes.orkes_scheduler_client import OrkesSchedulerClient
+from conductor.client.scheduler_client import SchedulerClient
 
 pytestmark = [pytest.mark.e2e]
 
@@ -125,12 +125,12 @@ def agent_name(conductor_clients) -> Iterator[str]:
 
 
 @pytest.fixture()
-def schedule_client(conductor_clients) -> OrkesSchedulerClient:
+def schedule_client(conductor_clients) -> SchedulerClient:
     return conductor_clients.get_scheduler_client()
 
 
 @pytest.fixture(autouse=True)
-def clean_schedules(schedule_client: OrkesSchedulerClient, agent_name: str):
+def clean_schedules(schedule_client: SchedulerClient, agent_name: str):
     """Purge any leftover schedules for this agent before each test."""
     schedule_client.reconcile(agent_name, [])
     yield

src/conductor/ai/agents/runtime/http_client.py

@@ -203,13 +203,13 @@ def _workflow_client(self) -> Any:
 
     @property
     def schedules(self) -> Any:
-        """Cron schedule lifecycle client (:class:`OrkesSchedulerClient`).
+        """Cron schedule lifecycle client (:class:`SchedulerClient`).
 
         Exposes ``get_schedule/save_schedule/get_all_schedules`` plus the
         lifecycle methods ``pause/resume/delete/run_now/preview_next/
         reconcile``. When bound to a runtime, this is the *same*
-        :class:`OrkesSchedulerClient` instance the runtime uses — there is
-        one shared schedule surface, not two.
+        :class:`SchedulerClient` instance the runtime uses — there is one
+        shared schedule surface, not two.
         """
         if self._runtime is not None:
             return self._runtime.schedules_client()

src/conductor/ai/agents/runtime/runtime.py

@@ -2231,7 +2231,7 @@ def client(self) -> Any:
         return self._http
 
     def schedules_client(self) -> Any:
-        """Return the shared :class:`OrkesSchedulerClient` for this runtime.
+        """Return the shared :class:`SchedulerClient` for this runtime.
 
         Delegates to :attr:`client` so the runtime and the control-plane
         client expose the *same* schedule surface (one instance, not two).

src/conductor/client/ai/schedule.py

@@ -9,7 +9,7 @@
 prefixed wire name plus server-computed fields like ``next_run``.
 
 The private helpers below (payload mapping, wire-name prefixing, typed error
-translation) are shared by ``OrkesSchedulerClient``'s schedule-lifecycle
+translation) are shared by ``SchedulerClient``'s schedule-lifecycle
 methods and the module-level ``schedules.*`` API. The native
 ``get_schedule``/``save_schedule``/``get_all_schedules`` endpoint methods are
 the source of truth for reads/writes/lists; the ``ScheduleInfo`` view exists

src/conductor/client/orkes_clients.py

@@ -43,10 +43,7 @@ def get_authorization_client(self) -> AuthorizationClient:
     def get_metadata_client(self) -> MetadataClient:
         return OrkesMetadataClient(self.configuration)
 
-    def get_scheduler_client(self) -> OrkesSchedulerClient:
-        # Annotated with the concrete class: the schedule-lifecycle methods
-        # (pause/resume/delete/run_now/preview_next/reconcile) live on
-        # OrkesSchedulerClient, not on the SchedulerClient endpoint ABC.
+    def get_scheduler_client(self) -> SchedulerClient:
         return OrkesSchedulerClient(self.configuration)
 
     def get_secret_client(self) -> SecretClient:

src/conductor/client/scheduler_client.py

@@ -75,3 +75,32 @@ def get_scheduler_tags(self, name: str) -> List[MetadataTag]:
     @abstractmethod
     def delete_scheduler_tags(self, tags: List[MetadataTag], name: str) -> List[MetadataTag]:
         pass
+
+    @abstractmethod
+    def pause(self, wire_name: str, reason: Optional[str] = None) -> None:
+        pass
+
+    @abstractmethod
+    def resume(self, wire_name: str) -> None:
+        pass
+
+    @abstractmethod
+    def delete(self, wire_name: str) -> None:
+        pass
+
+    @abstractmethod
+    def preview_next(self,
+                     cron: str,
+                     n: int = 5,
+                     start_at: Optional[int] = None,
+                     end_at: Optional[int] = None,
+                     ) -> List[int]:
+        pass
+
+    @abstractmethod
+    def run_now(self, info: "ScheduleInfo") -> str:  # noqa: F821
+        pass
+
+    @abstractmethod
+    def reconcile(self, agent_name: str, desired: Optional[List["Schedule"]]) -> None:  # noqa: F821
+        pass