feat(conversations): ask_role, ask another role and be woken by its answer #25
Loading…
Reference in a new issue
No description provided.
Delete branch "mc/af9013dc-bb4b-408b-b13d-06a9643fdf34"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
New MCP tool
ask_role(roleId, question)for agents in a conversation. The call returns at once. The question lands in the same person's conversation with the target role (started if none), marked as from the asking role (from_role_id,from_role_kind = 'ask', migration 024, additive). The target agent wakes like for a person's message and is told which role asked. When its turn ends, its reply is posted in the person's chat as before and relayed to each asking role's conversation (kindanswer), which wakes the asker with the answer so the conversation progresses.Design:
person(runs on the person's behalf and sponsorship, ADR 0019);from_role_*records the real speaker, so no table rebuild.ask), so there is no ping-pong.Evidence
vitest run packages/server: 571 passed. eslint and tsc clean (server, web);generate:apiregenerated.Not done
Web UI does not yet label "from " (field is in the API). Slack DM copies show such messages like the person's own.
Rollback / verify
Revert; the columns are additive. After rollout:
ask_rolein a role's tools; asking from one role's chat shows a message in the other's chat and wakes the asker with the answer.feat(conversations): ask_role, a fire-and-forget question to another roleto feat(conversations): ask_role, ask another role and be woken by its answer