lineIntersects() won't return the intersection of a line and a polygon

I'm having trouble with running lineIntersects() on a line and a polygon.

I'm using TurfJS 6, via https://cdn.jsdelivr.net/npm/@turf/turf@6/turf.min.js. I'm mapping the results in Leaflet 1.7.1.

A working example of my issue (including sample GeoJSON data) can be found here:
https://codepen.io/Kirkman/pen/JjOxjwP

Basically, I have two neighboring polygons. I use Turf to create a LineString running from the centroid of one to the centroid of the other. What I want to do now is use lineIntersects() to find the point where this LineString intersects the boundary of one of the polygons.

My code looks roughly like this:

// Calculate the distance beteween centroid of highlighted polygon and the centroid of the neighboring polygon.
const highlight_centroid = turf.centerOfMass(highlight_feature);
const centroid = turf.centerOfMass(neighbor_feature);
const line = turf.lineString([highlight_centroid, centroid]);

// Find the intersection of this line with the boundary of neighbor_feature

// First, check if it intersects. Turf says TRUE, the line DOES intersect neighbor_feature
console.log(turf.booleanIntersects(line,neighbor_feature));

// But lineIntersect() returns an empty feature collection.
// There should be a point coordinate
const intersection = turf.lineIntersect(line,neighbor_feature);
console.log(intersection);

Turf's booleanIntersects() method returns TRUE -- because the line and polygon do intersect.

But when I try to use lineIntersect() to obtain the intersection point, Turf just returns an empty feature collection. And it does the same if I try other similar methods like lineOverlap() or lineSplit().

Am I doing something wrong, or is there an issue with these line-related methods?

Start by reproducing the supplied CodePen with TurfJS 6 and Leaflet 1.7.1, comparing booleanIntersects() with lineIntersect() for the centroid-to-centroid LineString and polygon. Trace the line-related methods involved and use the sample GeoJSON to verify the expected boundary point; done means the reported intersection behavior is corrected or clearly characterized with coverage for this case.