Files
buzz/benchmarks/buzz-dataset/cross-thread-requests
Salman Mohammed 79df468255 Add Buzz benchmark evaluation layers (#6823)
## Summary

- classify every Buzz-native benchmark task as `regression` or
`workflow`
- add metadata-backed `--layer` selection with k=1 regression and k=3
workflow defaults, while preserving explicit `--attempts`/`-k`
- split an unqualified mixed Buzz dataset run into two Harbor jobs so
each layer gets the correct default
- document the layer contract and cover metadata, selection, defaults,
overrides, invalid input, and command construction

---------

Signed-off-by: Salman Mohammed <smohammed@squareup.com>
2026-08-26 17:41:56 -04:00
..
…

cross-thread-requests

The harness posts ALPHA and BETA as separate top-level human mentions in the same channel before the queue flushes. Passing requires two different replies, each anchored to its own triggering event with only its own answer. This is a deliberately hard guard for the cross-thread contamination reported in block/buzz#5839 and the exact reply-target contract in block/buzz#4072.