test(behaviour): add code dispatch trigger scenarios (bash routing)

[ifireball]

What is missing

Behaviour tests cover triage dispatch triggers partially, but code has no behaviour scenarios that verify dispatch triggers fire the correct agent run on the current bash router in reusable-dispatch.yml.

We need this baseline before porting code's trigger logic to harness CEL expressions.

What should happen

One vertical PR adds Godog scenarios for code dispatch triggers:

• Triggers: ready-to-code label, /fs-code
• Uses bash route job only (no CEL, no harness-dispatch)
• Agent runs via dummy runtime; assert outcome (e.g. behaviour-results.json or expected side effect)
• Requires behaviour framework (PR #1982)

Merge criterion

make behaviour-test green with new code trigger scenarios.

Blocks

Port code to harness CEL trigger (#2897).

Related

Part of epic #2888. Does not block the custom-agent harness-dispatch issue (#2889).

[fullsend-ai-triage]

🤖 Triage · ⚠️ Cancelled · Started 8:33 AM UTC · Ended 8:34 AM UTC
Commit: 9f4f2b6 · View workflow run →

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:35 AM UTC · Completed 8:37 AM UTC
Commit: 9f4f2b6 · View workflow run →

[fullsend-ai-triage]

Triage Summary

This issue requests adding Godog behaviour test scenarios for code dispatch triggers using the current bash router in reusable-dispatch.yml. The scope is well-defined: cover ready-to-code label and /fs-code triggers, use dummy runtime, assert outcomes via behaviour-results.json.

Prerequisite

This issue explicitly depends on the behaviour test framework introduced in PR #1982, which is still open and unmerged. No behaviour test scenarios can be written until that framework lands. Marking as blocked on that PR.

Context

This is part of epic #2888 (per-repo harness CEL dispatch) and is a prerequisite for #2897 (porting code to harness CEL triggers). The sequencing is: framework (#1982) → bash routing tests (this issue) → CEL port (#2897).

Once PR #1982 merges, this issue will be unblocked and ready for implementation. The merge criterion is clear: make behaviour-test green with the new code trigger scenarios.

Blocked by:

• ci(e2e): add Gherkin behaviour tests with dummy runtime #1982

---

Labels: Adding blocked label since the issue depends on unmerged PR #1982; adding testing label for test-focused work; existing labels (component/e2e, type/feature, agent/code, component/dispatch) are correct.