Builder blocklisting heuristics

If a builder commits a violation like not revealing payloads or not respecting the validator's preferences. We would like to be able to blocklist the builder until we have regained enough trust in them.

Blocklisting can be manual where the operator is responsible to remove the builder from the blocklist. We could also define heuristics in the client to automatically blocklist the builder.

How could we define such heuristics?

No file, test, or entry point is named. Start by reviewing the builder and validator specifications for payload disclosure and validator-preference violations, then determine which violations should trigger manual or automatic blocklisting. Done means the heuristics and blocklist behavior are specified clearly enough to implement.

Written by the indexing model from the issue text.