Story points are like BMI: They're meant to be accurate enough that, when you aggregate them over a whole bunch of items, you end up with a reasonably reliable

Story points are like BMI: They're meant to be accurate enough that, when you aggregate them over a whole bunch of items, you end up with a reasonably reliable time estimate. But they're a terrible measure of time to complete an individual task. They were never meant to be such a thing in the first place. That's why the canonical Scrum books always say that the PO can use story points to (roughly) estimate completion dates, but the development team should never use them to figure out how many items to accept into the next sprint.