feat(compass-agent): add comms_open_dm + comms_dm peer-DM tools (RIG-2966)

config/skills/comms-playbook/SKILL.md

@@ -56,7 +56,10 @@ Pick the destination that puts the message in front of exactly who needs it:
   to a direct channel between them instead of spraying a shared channel. Fewer
   readers, less noise, no muted-topic guesswork. Use a DM for a two-party
   clarification; use the shared channel when the outcome is something the lane
-  should be able to read later.
+  should be able to read later. Agents heavily prefer DMs for two-party
+  coordination: open or resume a peer DM with `comms_open_dm{peer_handle}`, or
+  use `comms_dm{peer_handle, topic, text}` to open-and-post in one call. Like any
+  post it names a topic, and a new topic needs `create_topic: true`.
 - **Report UP, delegate DOWN.** Results and asks that need your parent go to the
   parent; work you hand to a report goes down to it. Keep a topic to one
   direction of flow where you can.

packages/compass-agent/AGENTS.md

@@ -36,14 +36,16 @@ restatement of the role prompt.
 
 ## The comms toolset
 
-Five native comms tools ship (`src/comms.ts`), none of them ask-answering:
+Seven native comms tools ship (`src/comms.ts`), none of them ask-answering:
 
 - `comms_post_message` — post a markdown message to a channel topic.
 - `comms_post_ask` — raise a structured ask (async; the answer arrives on a
   later turn).
 - `comms_list_messages` — read a channel's recent messages.
 - `compass_roster` — list the agent's neighborhood/subtree/owner roster.
 - `compass_set_status` — set the agent's presence activity.
+- `comms_open_dm` — resolve-or-create a two-party DM channel with a peer by handle.
+- `comms_dm` — open (resolve-or-create) a peer DM and post a message to it in one call.
 
 `comms_post_ask` mints each `AskOption.id` as the option's zero-based index
 (a decimal string) — the native SDK ask option carries no id, and the id is the

packages/compass-agent/src/cli.test.ts

@@ -2571,7 +2571,7 @@ describe("main wires the mounted agent-config into createAgentSession", () => {
 			...createLifecycleTools(new LifecycleBroker(fakeTransport)),
 			...createForgeTools(new ForgeBroker(fakeTransport)),
 		];
-		expect(natives).toHaveLength(17);
+		expect(natives).toHaveLength(19);
 		for (const tool of natives) {
 			expect({ name: tool.name, arity: tool.execute.length }).toEqual({
 				name: tool.name,
@@ -2621,7 +2621,7 @@ describe("main wires the mounted agent-config into createAgentSession", () => {
 		// natives are ALWAYS merged in (RIG-1741/RIG-2672) — so customTools carries
 		// exactly those, and never a discovered MCP tool.
 		expect(toolNames(seen[0].customTools)).toContain("agents_spawn_peer");
-		expect(seen[0].customTools).toHaveLength(17);
+		expect(seen[0].customTools).toHaveLength(19);
 		expect(seen[0].enableMCP).toBe(false);
 	});
 
@@ -2654,7 +2654,7 @@ describe("main wires the mounted agent-config into createAgentSession", () => {
 		// (RIG-1741/RIG-2672) — so customTools is exactly the comms/lifecycle/forge
 		// natives.
 		expect(toolNames(seen[0].customTools)).toContain("comms_post_message");
-		expect(seen[0].customTools).toHaveLength(17);
+		expect(seen[0].customTools).toHaveLength(19);
 	});
 
 	// ── RIG-1732 T10: COMPASS_ROLE → prompts/<role>/SYSTEM.md → customSystemPrompt ──