Add missing [Unreleased] CHANGELOG entries for the A2A stdio transport
feature and the .py path routing fix, both referencing the correct
issue #691 (not #264 which was already closed in v3.0.0).
ISSUES CLOSED: #691
step_mock_popen_success stored mock_proc (Popen's return value) as
context.popen_mock, but call_args is recorded on the mock *replacing*
subprocess.Popen (what patcher.start() returns). Reading call_args from
mock_proc returns None, causing TypeError in the three command-construction
scenarios — behave reports these as "errored" not "failed".
Fix: assign patcher.start() to context.popen_mock so the assertion steps
read call_args from the correct mock. Also remove the redundant
patcher.stop() calls from the assertion Then steps (context.add_cleanup
already handles teardown). Add the required @tdd_issue and @tdd_issue_691
tags to the Connect with .py file path scenario per the TDD bug fix workflow.
ISSUES CLOSED: #691
Issue references corrected from #264 to #691 throughout all documentation.
The A2A stdio transport feature is tracked by issue #691, not #264 (which was
about resource registry tables in v3.0.0).
CHANGELOG.md: Updated issue reference and added .py path routing fix entry under
BDD tests: Added command construction assertions for all three connect scenarios
(module, .py script, executable) to verify subprocess.Popen receives correct args:
- Module paths (cleveragents.X): [python, -m, module]
- .py file paths: [python, file.py]
- Executable paths: [executable_path]
The connect() method in A2aStdioTransport incorrectly routed literal .py
script paths (e.g. "agent.py") through `python -m` which expects Python
module names. Fixed to use `python agent_path` for direct script execution
while keeping module paths (cleveragents.*) via `-m` and executables unchanged.
Also resolved merge conflict markers in CONTRIBUTORS.md and added changelog
entry for the A2A stdio transport feature under [Unreleased]. Added BDD
test coverage entry.
ISSUES CLOSED: #264
HAL9000
freemo