Docs: canonical conductor.client.ai paths for agent clients

AgentScheduleClient naming (ScheduleClient alias noted), the
OrkesClients.get_agent_client()/get_agent_schedule_client() factories, and
the AgentApiClient transport home; hello_world_schedule example builds via
the factory. Verified live: example fired 5 scheduled executions to
COMPLETED against the v0.4.0 JAR.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: Kowser

docs/agents/advanced.md

@@ -126,10 +126,15 @@ 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 `ScheduleClient`). Both sync and async forms
+`stream_sse`, and `.schedules` (the `AgentScheduleClient`). Both sync and async forms
 exist. Most users call `runtime.run/start/deploy` instead, 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_agent_schedule_client()` for the cron
+lifecycle). `AgentClient` composes that transport and adds the agent-level surface.
+
 ## Structured output
 
 Pass `output_type=` a Pydantic model (or dataclass) to get a typed, validated result.

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` | `() -> ScheduleClient` | Shared schedule client |
+| `schedules_client` | `() -> AgentScheduleClient` | 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,9 @@ 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`, ...
 
-`ScheduleClient` (via `runtime.schedules_client()` or `runtime.client.schedules`):
+`AgentScheduleClient` (alias `ScheduleClient`; canonical home
+`conductor.client.ai` — via `runtime.schedules_client()`, `runtime.client.schedules`,
+or `OrkesClients.get_agent_schedule_client()`):
 
 | Method | Signature |
 |---|---|
@@ -280,11 +282,13 @@ 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) | `-> ScheduleClient` | |
+| `schedules` (property) | `-> AgentScheduleClient` | |
 | `close` | `() -> None` (async) | |
 
 Lower-level endpoint methods (`start_agent`, `deploy_agent`, `compile_agent`) are also
-available.
+available. The raw transport behind them is `conductor.client.ai.AgentApiClient`
+(build one with `OrkesClients.get_agent_client()`); `AgentClient` composes it and
+keeps the agent-level conveniences.
 
 ## Config and credentials
 

examples/agents/hello_world_schedule.py

@@ -27,7 +27,6 @@
 from conductor.client.orkes_clients import OrkesClients
 
 from conductor.ai.agents.schedule import Schedule
-from conductor.ai.agents.schedule.client import ScheduleClient
 
 CONDUCTOR_API = "http://localhost:8080/api"
 
@@ -108,12 +107,10 @@ def main() -> None:
     # 1. Register the workflow that the schedule will fire.
     register_hello_world_workflow(agent_name)
 
-    # 2. Build the agentspan ScheduleClient against the scheduler-enabled
+    # 2. Build the agent schedule client against the scheduler-enabled
     #    Conductor instance.
     clients = OrkesClients(configuration=Configuration(base_url="http://localhost:8080"))
-    sched_client = ScheduleClient(
-        clients.get_scheduler_client(), clients.get_workflow_client()
-    )
+    sched_client = clients.get_agent_schedule_client()
 
     # 3. Declarative deploy: one schedule, fires every 2 seconds.
     #    Quartz 6-field cron: 'sec min hour day month day-of-week'.