3 Commits

Include renames

Author	SHA1	Message	Date
weichen	367dc207b3	Add the generative-ui plugin, capability gating, and surface projection ... Why: Generative UI U3 - the agent needs a real submission path and the next turn needs to see prior pages: a built-in in-process plugin registers generative-ui.present (exposeAsTool) carrying the catalog (prompt=validation single source) with a schema-repair strategy measured against real MiniMax-M3 deviations; the command bus gains an owner-scoped tool gate so a disabled plugin stops injecting its tool (execution guard remains in surfacesvc); ctxasm projects saved surfaces back into context so the model can revise existing structure; doc-refs are authorized against the owner's real artifacts. Evidence: unit suites green (genui guards/epoch/doc-ref, gate fail-closed, projection content); full go test ./... green; cmdbus/ctxasm also green under AGENT_PG_TEST_DSN; real-model closed loop (env-gated TestRealModelSurfaceLoop) passes: task->spec->save->projection->revise with revision 1->2 and structure change, CNY 0.08 total. Impact: New internal/genui package; additive cmdbus/ctxasm/runmgr/ runtime hooks; no storage or contract changes (U2 layer untouched). Refs: Documents proposal r2 U3; Core PR #25/#26; Backend #143; Dev task feature/generative-ui-u3	2026-10-11 10:38:15 +00:00
weichen	6337cd87f8	Decouple runmgr from cmdbus via view types in CommandSource ... Why: the EXT-14 wiring made runmgr import cmdbus for the CommandSource interface signatures, which adds a new edge backend/runmgr -> backend/cmdbus outside the architecture baseline ratchet; the Dev umbrella lint (lint-architecture) rejects the gitlink bump because of it. The dependency direction was always meant to be inverted: runmgr defines the port, the composition root adapts the bus. Evidence: go build/vet clean; go test ./... 32/32 packages green; grep confirms no internal/cmdbus import left in non-test runmgr files; Dev-side lint re-run scheduled on the gitlink bump PR. Impact: runmgr.CommandTool/CommandRequest/CommandResponse are local view types; app.busAdapter now converts cmdbus types at the boundary (Entrance still fixed to agent by runmgr). No behavior change; the runmgr tests speak the view types instead of cmdbus ones. Refs: Dev umbrella make test failure 'architecture: new dependency edges backend/runmgr backend/cmdbus'; proposal 2026-10-09-ext-g1-b1-b3 (EXT-14); Backend #114.	2026-10-09 16:31:43 +00:00
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