I Found a Bug in Apple's Fsck_hfs

I wish I could read the prompt for this article rather than the LLM fluff it generated.

There's a TL;DR at the top, then I'd think it gets to the article but no, there's another TL;DR and it reads like some weird prose clickbait.

Then the setup section is just, overly confident LLM-ish stuff like:

> The error was perfectly reproducible. Same node number, every time. Even on a freshly formatted volume with barely any data. That ruled out progressive data corruption and pointed to something deterministic.

I just can't.