docs(deep-agents): customEvents is per run on the skills page; info callout; the orchestrator docstring matches the page

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

Author: blove

apps/website/content/docs/deep-agents/capabilities/skills.mdx

@@ -112,7 +112,7 @@ A custom event is a live signal and is not replayed when a thread is reopened. T
 
 <ExampleCode file="skills.component.ts" region="skills-sources" title="skills.component.ts — the two readers" />
 
-`agent.customEvents()` is a Signal of every custom event received in this session, so the live reader walks it newest first and takes the most recent payload under the event name the graph emits, while `agent.value()` is the agent state the adapter projects from the latest checkpoint, which carries the key even though the run stream does not.
+`agent.customEvents()` holds the custom events of the current run, cleared when a new run starts, so the live reader walks it newest first and takes the most recent payload under the event name the graph emits, while `agent.value()` is the agent state the adapter projects from the latest checkpoint, which carries the key even though the run stream does not.
 
 ### What the agent actually opened
 

apps/website/content/docs/deep-agents/capabilities/subagents.mdx

@@ -35,7 +35,7 @@ Omitting `tools` would inherit the main agent's tools instead, which is the oppo
 
 <ExampleCode file="graph.py" region="orchestrator" title="graph.py — the orchestrator" />
 
-<Callout type="note" title="A third specialist you did not declare">
+<Callout type="info" title="A third specialist you did not declare">
 Unless it is explicitly disabled, `create_deep_agent` inserts a `general-purpose` subagent ahead of the specs you pass, with the main agent's model and tools. The `task` tool description therefore lists three agent types rather than two. The demo does not disable it; the system prompt simply names the two specialists it wants, which is enough to keep the orchestrator on them.
 </Callout>
 

cockpit/deep-agents/subagents/python/src/graph.py

@@ -111,8 +111,9 @@ def lookup_weather(airport: str) -> str:
 def build_subagents_agent():
     """Build the orchestrator.
 
-    Passing `subagents` is what installs `SubAgentMiddleware` and, with it, the
-    `task` tool. The orchestrator gets no lookup tools of its own so it has no
+    `SubAgentMiddleware` and the `task` tool ship by default through the
+    `general-purpose` subagent; passing `subagents` puts these specialists on
+    that tool. The orchestrator gets no lookup tools of its own so it has no
     way to answer without delegating.
     """
     return create_deep_agent(