observe: spec test for empty-capture verdict
obs report emits "CPU-bound" for a capture with wall time from the run
meta but no events at all -- no scheduler events, GC, spans, suspends or
memtrace samples. The leftover wall is unknown, not on-CPU. The test sets
only the wall clock and asserts the verdict is not CPU-bound, names the
empty case, and the report drops the "run looks balanced" line. Fails today.