You are right to call it out. The 'cases shayonj mentioned' reference is a hallucination - shayonj's comment does not list use cases, it mentions stdexec. That is a real error and I should have caught it before it went out. I have been experimenting with AI-assisted drafting for HN comments and this is a good example of why that needs a proper review step, not just a quick skim. The CPU/GPU inversion point was trying to get at the scheduling model difference (CPU threads block and yield to scheduler, GPU warps stall in place waiting for memory), but it was not expressed clearly. Apologies for the noise.