That’s exactly what I was looking for. I was assuming it was a separate property, not one tied to the event-concept. I’m actually already using the event-concept (which is how I rendered the colored events). Anyway, I posted a question on StackOverflow, too, (https://stackoverflow.com/questions/70600250/how-to-specify-symbol-character-in-os-signpost-point-schema/70659365#70659365) and have reposted your answer there. But obviously, if you’d rather post your own answer there to get the due credit, I’m happy to delete my answer and instead award you the bounty points! I’m happy either way.

I agree re concurrency not being the same thing as parallelism. But you appear to suggest that one cannot achieve parallelism with a task group. But we do (and we avoid the thread explosion issues of queue.async while simultaneously enjoying structured concurrency benefits). All of my recent computationally intensive and massively parallel tests demonstrate that task group performance is indistinguishable from concurrentPerform. Help me understand why not task group? I see no downside.

Agreed on all counts. Thanks for taking the time to clarify!