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

[ifireball]

What is missing

Behaviour tests cover triage dispatch triggers partially, but prioritize 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 prioritize's trigger logic to harness CEL expressions.

What should happen

One vertical PR adds Godog scenarios for prioritize dispatch triggers:

• Triggers: /fs-prioritize (and schedule if testable)
• 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 prioritize trigger scenarios.

Blocks

Port prioritize to harness CEL trigger (#2901).

Related

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

[fullsend-ai-triage]

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

[fullsend-ai-triage]

Triage Summary

This issue is well-defined and ready to implement once its prerequisite lands.

Blocking dependency: PR #1982 (Gherkin behaviour tests with dummy runtime) is still open. The issue explicitly requires this framework — Godog scenarios, the dummy runtime, and the e2e/behaviour/ infrastructure — before prioritize dispatch trigger scenarios can be added.

Scope is clear:

• Add Godog scenarios for prioritize dispatch triggers (/fs-prioritize, and schedule if testable)
• Target only the bash route job in reusable-dispatch.yml (no CEL, no harness-dispatch)
• Use the dummy runtime for agent runs; assert via behaviour-results.json or expected side effects
• Merge criterion: make behaviour-test green with new scenarios

Relationships:

• Part of epic Epic: ADR 0061 — per-repo harness CEL dispatch #2888 (per-repo harness CEL dispatch)
• Blocks feat(dispatch): port prioritize to harness CEL trigger #2901 (port prioritize to harness CEL trigger)
• Does not block feat(dispatch): add harness-dispatch job with ADR 54 auth, kill switch, and custom-agent behaviour test #2889 (custom-agent harness-dispatch)

Once PR #1982 merges, this issue can proceed immediately.

Blocked by:

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

---

Labels: Adding blocked label since PR #1982 must merge first, and testing label to match the behaviour test convention seen on related issues.