Update docs for coordinator drop and Slack/Teams direct messages

connector/microsoft-teams.mdx

@@ -13,6 +13,7 @@ Once connected, you can:
 - **Start investigations with Ask PlayerZero** — Select a project, choose a workflow or playbook, and provide your question. PlayerZero creates a Player thread and responds in the Teams thread.
 - **Approve workflow stage transitions** — When a Player thread needs approval to move to the next workflow stage, an interactive approval card appears in Teams with options to approve immediately or approve with a message and playbook.
 - **Receive notifications in channels** — Get workflow stage approval requests, Player thread summaries, and other notifications delivered to your team's channels.
+- **Get direct questions as messages** — When a Player thread has a collaboration question for a specific person, PlayerZero can deliver it as a direct message so the right teammate can answer without leaving Teams.
 - **Open in Chat** — Link an existing Player thread to a Teams channel from the PlayerZero UI, so you can continue a conversation in Teams.
 - **Reply in threads** — Continue a conversation with a Player thread by replying in the Teams thread. Messages in the Teams thread are forwarded to the Player thread, and its responses appear in the Teams thread.
 
@@ -47,6 +48,8 @@ The approval card includes:
 
 After approval, a confirmation message is posted to the thread so the team can see who approved and any notes they included.
 
+If the request has already been handled — for example, approved from another channel or from PlayerZero — the card updates in place to show that the request is no longer pending, so no one approves the same transition twice.
+
 ## Open in Chat
 
 You can link any Player thread to a Teams channel directly from the PlayerZero UI.
@@ -62,6 +65,7 @@ PlayerZero delivers notifications to Teams channels based on your project and wo
 - **Workflow stage approval requests** when a Player thread needs human approval to continue
 - **Player thread response summaries** posted to Teams threads where investigations were started
 - **Notifications from monitor-initiated Player threads** when a monitor triggers a new investigation and delivers results to a configured channel
+- **Direct questions delivered as messages** when a Player thread has a collaboration question for a specific person and direct messages are enabled for the project
 
 Notification routing is configured per project and per workflow stage in **Settings**. See [Notification Configuration](#notification-configuration) for details.
 
@@ -98,6 +102,11 @@ Once Teams is connected, you can configure where notifications are delivered at
 - Optionally restrict notifications to business hours based on your team's timezone
 - Notifications generated outside business hours are held and delivered when business hours resume
 
+**Direct messages:**
+- Turn on **Send direct messages** for a project to deliver direct questions to individual teammates as Teams messages, alongside the channel notifications above
+- Choose what is sent as a direct message with the scope setting: **All questions**, **Direct questions only**, or **Workflow approval questions only**
+- Configure it at **Organization settings → Collaboration → Teams**, then select the project, turn on **Send direct messages**, and click **Save**
+
 ## Get Started
 
 👉 [AI Player overview](/features/ai-player)

connector/slack.mdx

@@ -15,6 +15,7 @@ Once connected, you can:
 - **Use the `/ask_playerzero` command** — Type `/ask_playerzero` in any channel to open the Ask PlayerZero modal without needing to right-click a message
 - **Open in Chat** — Link an existing PlayerZero session to a Slack channel from the PlayerZero UI, so you can continue a conversation in Slack
 - **Receive notifications in channels** — Get workflow stage approval requests, Player thread summaries, and other notifications delivered to your team's channels
+- **Get direct questions as DMs** — When a Player thread has a collaboration question for a specific person, PlayerZero can deliver it as a direct message so the right teammate can answer without leaving Slack
 
 ## Ask PlayerZero
 
@@ -66,6 +67,8 @@ The notification includes:
 
 After approval, a confirmation message is posted to the thread so the team can see who approved and any notes they included.
 
+If the request has already been handled — for example, approved from another channel or from PlayerZero — the card updates in place to show that the request is no longer pending, so no one approves the same transition twice.
+
 ## Open in Chat
 
 You can link any Player thread to a Slack channel directly from the PlayerZero UI.
@@ -145,6 +148,11 @@ Once Slack is connected, you can configure where notifications are delivered at
 - Optionally restrict notifications to business hours based on your team's timezone
 - Notifications generated outside business hours are held and delivered when business hours resume
 
+**Direct messages:**
+- Turn on **Send direct messages** for a project to deliver direct questions to individual teammates as Slack DMs, alongside the channel notifications above
+- Choose what is sent as a direct message with the scope setting: **All questions**, **Direct questions only**, or **Workflow approval questions only**
+- Configure it at **Organization settings → Collaboration → Slack**, then select the project, turn on **Send direct messages**, and click **Save**
+
 ## Get Started
 
 👉 [AI Player overview](/features/ai-player)

features/ai-player.mdx

@@ -20,7 +20,7 @@ A PlayerZero **channel** is a shared workspace built around a single objective,
 
 - **Channel** — the shared workspace and objective that threads collaborate within. Context, branches, and referenced files are shared across the channel.
 - **Thread** — an individual agent conversation. A thread can run in Agent Mode or Hive Mode and keeps its own history, context, and sandbox.
-- **Coordinator** — keeps threads aligned with the channel's objective, relays context between them, and tracks overall progress.
+- **Controlling thread** — the most recent thread in the channel manages transitions to new stages and tracks overall progress toward the channel's objective.
 
 The side panel lists every thread in the channel, **grouped by workflow**, so you can see all the work in progress at a glance. Teammate threads created in [Hive Mode](/features/hive-mode) appear here as first-class entries alongside the threads you start yourself.
 
@@ -32,7 +32,7 @@ Threads in a channel are not isolated. When you start a new thread, it inherits
 
 - **Inherited context** — A new thread carries the channel's objective and plan, a record of the threads that came before it, and the files those threads referenced.
 - **Inherited branches** — Starting a new thread from an existing one (using ⌘K or **New Thread**) carries over the repositories and branches the source thread was working on.
-- **Thread-to-thread messaging** — Threads can send context and findings to one another, and the coordinator relays updates so work flows across the channel.
+- **Thread-to-thread messaging** — Threads can send context and findings to one another, so updates flow across the channel as the work proceeds.
 
 A handoff from one thread to another keeps the history it depends on, whether the work moves from investigation to fix or from one team to another.
 

features/hive-mode.mdx

@@ -115,7 +115,7 @@ While agents are working, the **Hive tab** in the side panel shows real-time sta
 - Animated indicators show when agents are **communicating with each other** — exchanging findings, asking follow-up questions, or sharing context
 - Click any agent to see its objective and dependencies
 
-Each specialist agent runs as its own **thread** in the channel. Beyond the Hive tab, these teammate threads appear in the channel's thread roster grouped by workflow, so you can open any one of them directly and follow its full history. The **coordinator** keeps the team aligned with the channel objective and relays context between threads as the work proceeds.
+Each specialist agent runs as its own **thread** in the channel. Beyond the Hive tab, these teammate threads appear in the channel's thread roster grouped by workflow, so you can open any one of them directly and follow its full history. These teammate threads stay aligned with the channel objective and share context with one another as the work proceeds.
 
 In the chat stream, you'll see:
 

features/workflows.mdx

@@ -8,7 +8,7 @@ description: "Define multi-stage pipelines that govern how PlayerZero agents pro
 
 A Workflow is a customizable, multi-stage pipeline that controls how a PlayerZero agent processes work from start to finish. You define the stages, the allowed paths between them, and the rules that control progression.
 
-When a channel enters a workflow, it moves through stages like **Intake & Triage → RCA → Fix → Test → Document & Close**. Each stage will operate across one or more agent threads. Each thread receives workflow-specific instructions, performs its work, and then requests permission to advance. Transitions can be auto-approved or gated behind human review.
+When a channel enters a workflow, it moves through stages like **Intake & Triage → RCA → Fix → Test → Document & Close**. Each stage will operate across one or more agent threads. Each thread receives workflow-specific instructions, performs its work, and then requests permission to advance. The most recent thread in the channel acts as the controlling thread that manages transitions to the next stage. Transitions can be auto-approved or gated behind human review.
 
 ---
 
@@ -32,7 +32,7 @@ A stage is a node in the workflow graph. Each stage has a **name**, **instructio
 
 ### Transitions
 
-Transitions are the allowed paths between stages. Each transition includes a target stage and conditions describing when the agent should take that path. Transitions are validated at runtime — the agent can only move to stages explicitly defined as valid next steps.
+Transitions are the allowed paths between stages. Each transition includes a target stage and conditions describing when the agent should take that path. Transitions are validated at runtime — the agent can only move to stages explicitly defined as valid next steps. The channel sidebar surfaces these as the **Possible next stages** for the current thread.
 
 ### Approvals
 

how-playerzero-works.mdx

@@ -17,7 +17,7 @@ PlayerZero organizes work into channels and threads, with workflows defining the
 
 - **Channel** — a shared workspace built around a single objective. Threads collaborate inside a channel and share its context, branches, and referenced files.
 - **Thread** — an individual agent conversation, with its own context and sandbox. A thread is what older material may call a "Player."
-- **Coordinator** — keeps the threads in a channel aligned with the objective, relays context between them, and tracks overall progress.
+- **Controlling thread** — the most recent thread in a channel manages transitions to new stages and tracks overall progress toward the objective.
 - **Workflow** — a multi-stage process a thread moves through, such as triage, investigation, fix, and review. A project can run several workflows. See [Workflows](/features/workflows).
 
 Two capabilities make this work as a team: