weichen 020926234e Expose commands as in-run tools dispatched through the command bus (EXT-14) ...

Why: RDM's capabilities are rdm.* commands; the agent run has no bridge
to them, so the V0.1 end-to-end goal (full-conversation operation) and
the agent-driven two-trees-one-net access are unreachable (Q4 option A).
Evidence: SELF - red tests first: TestCommandToolsProjected and
TestCommandToolDispatchesThroughBus failed on undefined symbols, then
green; TestCommandToolsFiltering and TestCommandToolDispatchEnvelope
cover projection filtering (risk default low, description falls back to
title, unexposed commands absent) and the full dispatch receipt with
Entrance=agent preserved through CanonicalEntrance; go test ./... 32/32
packages ok.
Impact: agent-command pin cc1ad77 -> 5c6dd0c (library PRs #4/#5: optional
ExposeAsTool field + "agent" entrance). cmdbus gains CommandTool view and
Bus.CommandTools; runmgr gains SetCommandSource with projection into
runCtx.Tools (dedup: registry tools win) and routing in ExecuteTool -
model calls dispatch through the bus with Entrance=agent, Actor/Owner =
conversation owner, ConversationID set; high-danger commands keep the
inline-confirm-card flow via the bus; unregistered source = current
registry behavior. Composition root wires a busAdapter. No
pkg/extension change.
Refs: proposal 2026-10-09-ext-g1-b1-b3 section 2; Agent-Command #4/#5

2026-10-09 16:14:57 +00:00

..

cmdbus_test.go

Scope command audit storage and queries to the requesting owner

2026-10-08 14:02:19 +00:00

cmdbus.go

Expose commands as in-run tools dispatched through the command bus (EXT-14)

2026-10-09 16:14:57 +00:00

command_tools_test.go

Expose commands as in-run tools dispatched through the command bus (EXT-14)

2026-10-09 16:14:57 +00:00

pending_store_test.go

Add the public extension surface and platform services

2026-10-01 10:35:02 +00:00