If you still have a copy of the file with bad links, or can recreate the problem, I’d really appreciate a copy of the file. It would be perfect for helping me find and fix the bug. This sort of test-case file is perfect.
A test case file just needs to make the bug and only the bug stand out like a sore thumb. So if you can make a copy of the project and do something to make the page stand out (call it THE BUG PAGE or something) and make the one stack with the problem bright red.
Or better yet, just delete everything that isn’t the bug. It’s hard to get the wrong page when there’s only one page. LOL 
I’ll use this test-case to help find the bug. Then when I think I’ve fixed it, I’ll run the test project again and if the problem is gone, I’ll know it’s fixed.
Anyway, if you can share the project using a Dropbox link (or whatever sharing service you like) then I’ll download it and add it to the Stacks bug tracker. If the project needs any 3rd party stacks (pretty much every project does) then you’ll need to share your RW environment. Here’s how:
https://yourhead.zendesk.com/hc/en-us/articles/360033849994-Sharing-Your-Project-and-Add-ons
If the bug is gone and you can’t make it happen again or you just don’t have time to help, completely I understand. But these sorts of test-case projects are invaluable to me, so I have to at least ask. 
If you do have time, please post a link here, on our Slack channel (preferred), or send an email to our support folks (there’s a link at the bottom of every page of our site).
Thanks,
Isaiah