The agent-composer candidates endpoints returned hardcoded empty arrays; node_id
and tenant were ignored. Now:
- workflow variant: previous_node_outputs computed from the draft workflow graph
(WorkflowGraphTopology extracted from agent_v2 validators into
core/workflow/graph_topology.py + new upstream_node_ids BFS). Output
enumeration matches the Node Output Inspector: start variables + recorded
sys.* are static, Agent v2 upstream nodes use their binding's effective
declared outputs, all other kinds infer from the latest draft-run variables
(inferred: true). Entries are emitted in the stored
WorkflowPreviousNodeOutputRef shape (selector/node_id/output/name + display
extras) so a selected candidate writes back into the config verbatim.
human_contacts = the binding's configured node_job items (0522: defined only).
- soul variant (both variants): skills_files / cli_tools(enabled) /
knowledge_datasets (enriched via DatasetService, dangling marked missing for
the placeholder UX) / human_contacts from the agent's current soul config;
dify_tools from BuiltinToolManageService.list_builtin_tools (same source as
the tool selector; daemon outage degrades to an empty list, never a 500).
- per-list cap 200 + response-level truncated flag; all queries tenant-scoped;
empty config returns empty lists.
- controllers pass tenant_id/user_id/node_id (with_current_tenant_id +
with_current_user_id).
Design: Confluence 490012681 §3.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Slash-menu references are stored inline in the plain-string prompt as
{{#<kind>:<id>[|<label>]#}} tokens (kind: skill/file/tool/cli_tool/knowledge/
human/node_output/output). Mentions are pointers into the Agent config lists;
label is a plain-text fallback only — the backend re-resolves by id. The colon
form is invisible to the legacy template parsers, so no syntax collision.
- services/agent/prompt_mentions.py: parse/expand/scrub + per-surface allowlists
+ soul/node-job resolvers (tool ids accept provider|provider_id|plugin_id
qualified aliases).
- composer_validator: enforce §2.4 allowlists at save/validate
(mention_kind_not_allowed, mention_limit_exceeded as stable message codes).
- runtime: both run-request builders expand mentions to canonical names before
sending to the agent backend; node_output expands to its reference name only
(the value stays in the Workflow context block, per design §4.2); a final
scrub pass guarantees no {{#…#}} marker ever reaches the model, while legacy
{{#context#}} / {{#a.b#}} forms pass through untouched.
Design: Confluence 490012681 §2/§4. No DB changes.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
