S6: docs — AgentScheduleClient removal (no backward compatibility)

CHANGELOG Deprecated → Removed (breaking, with migration); drop the
deprecated-shim paragraphs from the agents docs; AgentClient.schedules and
runtime.schedules_client() documented as returning SchedulerClient.

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

Author: Kowser

CHANGELOG.md

@@ -21,9 +21,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Breaking (scoped):** schedule client objects no longer expose the mapped `get`/`save`/`list_for_agent` wrappers — `SchedulerClient`'s native methods are the source of truth: `get(wire)` → `get_schedule(wire)`, `save(schedule, agent)` → `save_schedule(SaveScheduleRequest)`, `list_for_agent(agent)` → `get_all_schedules(workflow_name=agent)`. The module-level `schedules.list/get/save` functions (and their `ScheduleInfo` returns) are unchanged
 - `get_schedule` returns a typed `WorkflowSchedule` (or `None` for missing schedules) instead of a raw camelCase dict, matching its declared annotation and [docs/SCHEDULE.md](docs/SCHEDULE.md); dict-consumers should switch to attribute access or `to_dict()`
 
-### Deprecated
+### Removed
 
-- `AgentScheduleClient`/`ScheduleClient` and `OrkesClients.get_agent_schedule_client()` — fully functional delegation shims over `SchedulerClient`; use `get_scheduler_client()`. Removal planned for the next major release
+- **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 `SchedulerClient` directly (same methods, same shared instance)
 
 ### Fixed
 

docs/agents/advanced.md

@@ -134,8 +134,7 @@ which add local-worker management on top of this client.
 The raw `/agent/*` HTTP transport behind this client is
 `conductor.client.ai.AgentApiClient` — also reachable without the agents layer via
 `OrkesClients.get_agent_client()` (and `get_scheduler_client()` for the cron
-lifecycle; `get_agent_schedule_client()` is deprecated). `AgentClient` composes that
-transport and adds the agent-level surface.
+lifecycle). `AgentClient` composes that transport and adds the agent-level surface.
 
 ## Structured output
 

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` | `() -> SchedulerClient` | Shared schedule client (a deprecated `AgentScheduleClient` shim) |
+| `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`,
@@ -207,10 +207,6 @@ WorkflowSchedule | None`, `save_schedule(SaveScheduleRequest)`,
 `get_all_schedules(workflow_name=...) -> list[WorkflowSchedule]`. The mapped
 `ScheduleInfo` view is returned by the module-level `schedules.list/get`.
 
-`AgentScheduleClient` (alias `ScheduleClient`; `conductor.client.ai`) and
-`OrkesClients.get_agent_schedule_client()` are **deprecated** delegation shims,
-kept for backward compatibility and planned for removal in the next major release.
-
 Errors: `ScheduleError`, `ScheduleNameConflict`, `ScheduleNotFound`,
 `InvalidCronExpression`.
 
@@ -288,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) | `-> AgentScheduleClient` | |
+| `schedules` (property) | `-> SchedulerClient` | |
 | `close` | `() -> None` (async) | |
 
 Lower-level endpoint methods (`start_agent`, `deploy_agent`, `compile_agent`) are also