I was on team “React is a Library” but for the most part that changed when the hooks and context API were added. The addition of those, relatively simple, tools made it possible to not need the additional state management libraries like Redux/MobX etc that, up until then, were necessary add-ons to manage state and data. This made React more of a full Framework in my opinion.
That being said React can still be dropped into a relatively static page to add small bits of interactivity.
So at this point React seems to span both Framework and Library depending on the use case.
My definition of a framework is code which defines the architecture of the rest of your application.
React as practiced in the real world absolutely does this. Theoretically you could plug it in as just the library that does the templating, but I've never seen a real-world codebase for which that appears to be true.
I'm ready to be convinced otherwise!