I know the Konflux way is to separate build from release, so that a failure at release time is a surprise if you don't look at the warnings that appear at build time.

But for an FBC, which is ONLY meaningful if it's able to be merged into the overall OperatorHub index, WHY would anyone ever want to see a "passing" build with validate-fbc task failures being hidden as a "warning" ? This just hides a problem until GA day when you're surprised that all your green builds are actually not releaseable.

Add to this the fact that the ECP also appears green in the Pipeline Runs UI, and we have TWO ways to hide the truth and make release day more stressful.

So what I'm asking for is that if validate-fbc FAILS it should not throw a WARNING but an ERROR. Otherwise what value is the validation, if not gating?