Hide conditionally excluded jobs from bk build watch

[JoelTowell]

Description

I ran bk build watch against a pipeline with many conditional steps. I found a lot of intentionally skipped steps were noisily logged as broken. After reviewing some documentation, it became clear that broken has a rather idiosyncratic meaning. It seems that it would often mean a job was skipped due to not meeting a conditional branches or if condition.

I think this is undesirable behaviour. If I watch a build, I don't want the output to be polluted with noise about jobs I didn't expect to run in the first place.

Upon inspection, it seems this happens because bk build watch passes the full API build into BuildSummaryWithJobs. This calls renderJobs which does not filter jobs based on their state. From what I can tell, conditionally skipped jobs must be registered as 'broken' before they arrive here. The result is displaying jobs which nobody would reasonably want to 'watch'.

The proposed solution is to filter out 'broken' jobs in bk watch jobs before they are passed into BuildSummaryWithJobs.

I briefly considered an alteration to renderJobs, but bk build view uses it too and should probably still show the full job list.

Changes

• Filter out 'broken' jobs with a helper function.
• Add a unit test to validate behaviour.

Testing

• Tests have run locally (with go test ./...)
• Code is formatted (with go fmt ./...)

Disclosures / Credits

• I'm not particularly conversant with Go. I used AI (Cursor with Grok 4.6) to validate my understanding of behaviour, and to help write the unit test.