revert(daemon): drop the #801 tool-precedence bullet after a live in-thread regression

[Poytr1]

Reverts #801 (commit 29feb9b) on the user's direct order, after a live in-thread regression traced to the tool-precedence bullet it added to the standing collaboration guidance.

The live regression

In a real Slack channel, a turn-taking counting game was started in a thread ("@test @test2 你们轮流报数, 报到30 停" — take turns counting to 30). The test agent (Claude Agent runtime) stopped playing through ordinary thread replies and instead routed every turn through sendMessage, "handing off" each next number to its peer and posting only meta-narration into the thread, e.g.:

Count so far: 1, 2, 3 (@test2) → 4 (me). Handing off for 5

The visible count skipped and duplicated numbers (1 → 4 → 6 → "8****8") instead of a clean 1..30 alternation.

Mechanism

The bullet said AgentConnect's MCP tools are the ONLY channel that reaches other agents and humans. That over-generalizes: the product convention is that current-thread communication is the ordinary reply — sendMessage deliberately has no in-thread form. The bullet taught the model that plain replies reach nobody, so it routed in-thread turns through sendMessage too.

The A/B measurements that validated #801 only exercised the parent-session report-back scenario, never an in-thread conversation — which is exactly how this escaped.

What this restores / costs

• The standing collaboration guidance in packages/daemon/src/session/session-manager.ts is byte-identical to its pre-fix(daemon): lead the collaboration guidance with a tool-precedence rule (#800) #801 form (verified against the parent of 29feb9b).
• The contract test pinning the bullet is removed (it was the only fix(daemon): lead the collaboration guidance with a tool-precedence rule (#800) #801 addition to session-manager.test.ts).
• The Claude Code's built-in SendMessage tool collides with the AgentConnect messaging tool and silently swallows parent reports #800 hazard (built-in SendMessage swallowing parent reports; measured 10/10 delivery with the bullet vs 4/6 without) returns. Follow-ups are tracked on Claude Code's built-in SendMessage tool collides with the AgentConnect messaging tool and silently swallows parent reports #800: a scoped rewrite of the bullet validated against both scenarios, and the mechanism-level fixes with no prompt blast radius.

🤖 Generated with Claude Code

[agentconnect-md-test]

Approved at head f985b0410397ec1271a0ac589fcda727d47c2254. No blocking findings.

The revert is internally consistent: it removes only the over-broad “ONLY channel” precedence guidance and the test that pinned that wording. The resulting collaboration prompt still explicitly instructs agents to use an ordinary reply for the current conversation and states that visible sendMessage calls land at a channel root, matching docs/product-conventions.md. Both touched files are byte-identical to their versions at the parent of #801 (1dccbc26ce432807d2555b531762a2485cf4f0bb), and git diff --check passes.

The known #800 built-in SendMessage collision returns with this revert, but that is an explicit, tracked tradeoff and is non-blocking for this regression fix.

Verification gap: the focused daemon test and daemon typecheck could not run because dependencies are absent and Corepack could not reach registry.npmjs.org (EAI_AGAIN), including after retrying with an isolated cache.

_{sent by review-bot (Codex · gpt-5.6-sol) · open in session}

[agentconnect-md-test]

Approved at synchronized head 44067ce926bfb5c099d78331dfdbc7b33d64e37e. No blocking findings.

The head’s source tree is identical to the previously inspected revision, and the merge-base patch remains limited to removing the over-broad “ONLY channel” precedence guidance plus the test that pinned it (33 deletions across two files). The resulting prompt still explicitly instructs agents to use an ordinary reply in the current conversation and states that visible sendMessage calls land at a channel root, matching docs/product-conventions.md.

The target branch advanced to 3d96c5fa6e040022b0dd3af83d0b74fb8a3327ab; git merge-tree confirms this patch merges cleanly with that base, with no intervening changes to either touched file. git diff --check also passes.

The known #800 built-in SendMessage collision returns as an explicit, tracked, non-blocking tradeoff.

Verification gap: focused daemon tests and typecheck were not rerun because dependencies are absent and the pinned package manager could not be downloaded from registry.npmjs.org (EAI_AGAIN).

_{sent by review-bot (Codex · gpt-5.6-sol) · open in session}