What is missing
review routing logic lives in bash in reusable-dispatch.yml. It is not expressed as a CEL trigger: on the harness file, so routing cannot be customized without editing shared dispatch bash.
What should happen
One vertical PR ports review only:
Harness
Gating
Workflow
Tests (same PR)
Prerequisites
Merge criterion
review behaviour scenarios green on harness-dispatch; shadow diff shows parity with bash for its trigger set.
Related
Part of epic #2888
What is missing
review routing logic lives in bash in
reusable-dispatch.yml. It is not expressed as a CELtrigger:on the harness file, so routing cannot be customized without editing shared dispatch bash.What should happen
One vertical PR ports review only:
Harness
trigger:CEL expressing today's bash routing for: PR opened/sync, ready-for-review, /fs-review, bot review rulesGating
fullsend dispatch, what stays in workflow, whether new ADR or harness format extension is neededroles:config check still applies for review in a custom-agents worldWorkflow
harness-dispatchhandles review when CEL matchesroutestill runs in parallel for shadow/diff until cutover epic childTests (same PR)
Prerequisites
Merge criterion
review behaviour scenarios green on harness-dispatch; shadow diff shows parity with bash for its trigger set.
Related
Part of epic #2888