Python: Feature/hosted dwf

[alliscode]

This pull request enhances support for passing conversation history into declarative workflow agents, ensuring that workflows receive the full message context (not just the latest user turn) when triggered via agents. It updates the input initialization logic, executor signatures, and hosting integration to handle lists of Message objects, and adds a regression test to guarantee correct population of System.LastMessageText for compatibility with existing YAML workflows.

[moonbox3]

Python Test Coverage Report •

File	Stmts	Miss	Cover	Missing
packages/core/agent_framework/_workflows
_agent.py	358	71	80%	66, 74–80, 116–117, 210, 271, 284, 351, 362, 364, 424, 430, 447–448, 455, 457, 463, 525–526, 535, 543, 569, 602–604, 606, 608, 610, 615, 620, 674, 704, 721, 760–763, 769, 775, 779–780, 783–789, 793–794, 802, 863, 870, 876–877, 888, 920, 927, 948, 957, 961, 963–965, 972
_runner.py	174	2	98%	309–310
_workflow.py	278	19	93%	91, 270–272, 274–275, 293, 297, 461, 676, 697, 747, 759, 765, 770, 790–792, 843
packages/declarative/agent_framework_declarative/_workflows
_declarative_base.py	462	58	87%	47, 50, 154, 242, 256, 270, 281, 298, 425–426, 433–434, 449, 479, 562–564, 566–568, 570, 573, 580, 606, 632–638, 640–641, 643–651, 672–673, 675–676, 966–969, 993–994, 1001–1002, 1007, 1016–1017, 1023
_executors_control_flow.py	170	6	96%	82, 90, 153, 343–344, 348
packages/foundry_hosting/agent_framework_foundry_hosting
_responses.py	528	118	77%	151–152, 161–162, 166, 171, 185, 209, 235–237, 256–258, 260–262, 264–266, 270–273, 285–291, 301–302, 320–322, 327, 329, 336, 338–339, 341, 343, 349–352, 354–356, 360, 363, 368–374, 377–378, 380–381, 389–394, 466–467, 1112–1114, 1116, 1163–1164, 1166–1167, 1169–1170, 1172–1173, 1178, 1187, 1190–1192, 1194, 1212, 1215, 1250–1254, 1258–1264, 1271–1275, 1281–1287, 1294, 1300, 1303
TOTAL	30502	3560	88%

Python Unit Test Overview

Tests	Skipped	Failures	Errors	Time
6131	30 💤	0 ❌	0 🔥	1m 36s ⏱️

[Copilot]

Pull request overview

This PR improves hosted declarative workflow agents so they receive full conversation context (history + current input) when invoked via agent interfaces, aligning behavior with non-workflow agents and maintaining YAML compatibility via System.LastMessageText.

Changes:

• Foundry hosting now prepends stored conversation history to workflow-agent inputs before invoking WorkflowAgent.run(...).
• Declarative workflow state initialization now accepts list[Message], populating Conversation.* and System.LastMessage* accordingly, and improves PowerFx safety by coercing Enum values.
• Adds a regression test ensuring Workflow.as_agent() populates System.LastMessageText correctly.

Show a summary per file

File	Description
python/packages/foundry_hosting/agent_framework_foundry_hosting/_responses.py	Passes Foundry-stored history + current request messages into workflow agent runs.
python/packages/declarative/agent_framework_declarative/_workflows/_declarative_base.py	Adds list[Message] trigger initialization and Enum-to-primitive coercion for PowerFx symbol conversion.
python/packages/declarative/agent_framework_declarative/_workflows/_executors_control_flow.py	Updates JoinExecutor trigger type to include list[Message] so workflows can be exposed as agents.
python/packages/declarative/tests/test_workflow_factory.py	Adds regression coverage for Workflow.as_agent() and System.LastMessageText.

Copilot's findings

• Files reviewed: 4/4 changed files
• Comments generated: 2

[github-actions]

Automated Code Review

Reviewers: 4 | Confidence: 89% | Result: All clear

Reviewed: Correctness, Security Reliability, Test Coverage, Design Approach

---

Automated review by alliscode's agents

[Copilot]

Copilot's findings

• Files reviewed: 8/8 changed files
• Comments generated: 4

[github-actions]

Automated Code Review

Reviewers: 1 | Confidence: 95%

✓ Design Approach

The patch fixes the immediate continuation bugs, but two parts of the new design still mis-handle multi-turn state. In declarative workflows, the continuation path now replays the entire incoming session history back into already-restored Conversation.* state, so chat history will grow with duplicates on every turn. In foundry hosting, the new unconditional restore-only call can leave WorkflowAgent.pending_requests populated, causing the subsequent user-message call to be interpreted as request responses instead of a fresh turn. Both issues stem from layering new behavior on top of existing stateful abstractions without accounting for what those layers already persist.

---

Automated review by alliscode's agents