revalidatePath is brute force, revalidateTag is precision

I confused revalidatePath with revalidateTag on a small project and ended up invalidating pages that had nothing to do with the change. Here's the real difference between the two cache granularities in Next.js 16, with a decision checklist.