Why does StrictMode double-invoke components in development?

StrictMode intentionally renders components, runs effects, and calls state setters twice in development to surface side effects that are not idempotent. This helps developers write components that behave correctly with concurrent rendering.