I am storing NextJS outputs in AWS S3 and implemented routing logic in Fastly Compute. Everything works as expected with a minor hitch: if I click the anchor generated by a <Link> element and if the app router smooth transition doesn't activate (unclear on why this happens sometimes and not others), the href correctly has a trailing slash, but the client router intercepts the click on the element and makes a request seemingly for the HTML asset without the trailing slash. This is particularly odd because an index.txt was downloaded for the target page as well (which should preclude the need for the full HTML asset, right?).

In the index.txt for the page containing the <Link> element, I see this:

...,"children":[["$","$L2",null,{"href":"/resources/lorem-ipsum-dolor-sit-amet","children":[ ...

Is this a bug? Shouldn't that have the trailing slash?