The acp-agent cordis configs loaded the fork backend but bound only one dsh-tool-subagent (to spawn), so the comment's claim that a multi-child scenario could exercise both transports was false — fork was loaded but unreachable by the model. Register a second dsh-tool-subagent bound to fork with a distinct toolName (subagent_fork), matching the coding-agent demo, in both cordis.yml (record/demo) and cordis.snapshot.yml (replay). Snapshot goldens are unchanged (the transcript does not capture the available-tool list).
3.3 KiB
3.3 KiB