Read a JavaScript stack trace back to its input

Requirements: Node.js 22 or later. Recorded and tested with Node.js 22.22.1.
No npm install, third-party dependencies, network calls, or input writes.

From this directory:
  node run.mjs with-cause       (expected exit status 1)
  node run.mjs without-cause    (expected exit status 1)
  node run.mjs fixed            (expected exit status 0)
  node --test importer.test.mjs (9 passing tests)

records.bad.json deliberately contains invalid JSON: a trailing comma.
records.fixed.json differs only by removal of that comma.
The importer reads and parses records; it does not save them to a database.

The CLI explicitly prints the wrapper stack and, when it is an Error,
its one underlying cause. It is an example printer, not a general logger.
Exact parser wording, file paths, line numbers and async frames can vary
by runtime and source version. Tests do not assert the entire stack string.

This is a constructed teaching example. A suggested network retry in the
article is a hypothesis to examine, not a recorded AI response or incident.
