Half of our revalidatePath calls name a layout, and a streaming campaign header is the reason

A census of cache invalidation in one Next.js app: 46 revalidatePath calls across 62 Server Actions, zero revalidateTag, 24 actions that invalidate nothing on purpose, and one action that invalidates the same path in both its try and its catch.