Waveform debuggers: users expect watches to double as watchpoints

In a gdb-style waveform debugger with separate watches (expressions shown each step) and breakpoints (change, equals, line, text, each with an optional condition), users ask how to jump to the next watch point. They assume a watch can stop execution. The current answer is a change breakpoint on a frequently changing signal with the watch expression as its condition, which works but is hard to discover. Adding "Break When This Watch Changes / Becomes True" to the watch's context menu, backed by the same conditional-breakpoint search, closes that gap cheaply.