The fundamental principle of story-based work planning is that the story is an atomic unit of end value; stories may be groups into larger units that represent broader goals or divided into smaller tasks for planning convenience, but the defining aspect of the story is that it is the smallest unit of work providing independent end-value.
It’s true that, especially with Scrum and similar processes with timeboxed work cycles, teams tend to end up using “stories” that aren’t real user stories, but units of work (which may not even have started as real user stories, as instead of reserving a timeslice for support [refactoring, general infrastructure, and other useful for velocity but not directly targeting specific user needs tasks] work, the same disfunction leads teams to arbitrarily declare that all work must be called stories whether or not it is) arbitrarily carved up to fit the cycle timebox and the team’s [or some decision-maker’s] arbitrary preference for the number of work items per cycle.
I would argue that this is because sprints are a software development process antipattern in and of themselves, are particularly in tension with user-story-based work organization, and lower the resistance to a number of other antipatterns of the general description of applying classic top-down non-agile project management within a framework of “agile” buzzwords.