It feels like you've invented some definition of a "framework" that no one else is using. Or why not go deeper and argue against libraries and APIs because they limit your design decisions.
Libraries are code that you call to perform specific tasks. You control the program's structure and execution flow. You're in charge and you call the library when needed.
Frameworks invert the relationship and call into your code and hence dictate the overall structure and execution flow of your application. It's in charge and it calls various customization points that you provide to it at predefined points.
These definitions largely date back to the late 1980s with the introduction of object oriented frameworks (see Designing Reusable Classes from 1988). Further references include:
https://en.wikipedia.org/wiki/Software_framework#Comparison_...
https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a...