Invalid filename

Error: Invalid filename
at new module.exports (/Users/arkey/gpt-crawler/node_modules/adm-zip/adm-zip.js:57:19)
at new BayesianNetwork (/Users/arkey/gpt-crawler/node_modules/generative-bayesian-network/bayesian-network.js:24:21)
at new FingerprintGenerator (/Users/arkey/gpt-crawler/node_modules/fingerprint-generator/fingerprint-generator.js:32:44)
at BrowserPool._initializeFingerprinting (/Users/arkey/gpt-crawler/node_modules/@crawlee/browser-pool/browser-pool.js:566:37)
at new BrowserPool (/Users/arkey/gpt-crawler/node_modules/@crawlee/browser-pool/browser-pool.js:254:18)
at new BrowserCrawler (/Users/arkey/gpt-crawler/node_modules/@crawlee/browser/internals/browser-crawler.js:176:28)
at new PlaywrightCrawler (/Users/arkey/gpt-crawler/node_modules/@crawlee/playwright/internals/playwright-crawler.js:99:9)
at crawl (file:///Users/arkey/gpt-crawler/dist/src/core.js:34:25)
at file:///Users/arkey/gpt-crawler/dist/src/main.js:3:7
at ModuleJob.run (node:internal/modules/esm/module_job:218:25)

Start by tracing the crawl entry points in dist/src/main.js and dist/src/core.js, then inspect the BrowserPool fingerprint initialization shown in the stack trace. Reproduce the Invalid filename error and determine which filename reaches adm-zip through generative-bayesian-network. Done means the crawler initializes without this error and the regression is covered by an appropriate test.

Written by the indexing model from the issue text.