ThatGuySam d026a5420b fix(scanner): rename plist parser module to avoid CI cycle false positive ... Madge treated the local plist parser module name as a circular dependency during the Netlify build lane after the TypeScript refactor. Rename the local module to plist-parser so the internal file no longer collides with the external plist package name, while keeping parser behavior unchanged. Constraint: Must restore the deploy gate without changing parser semantics Rejected: Disable the circular-dependency check | would hide a useful guard instead of fixing the naming conflict that triggered it Confidence: high Scope-risk: narrow Reversibility: clean Directive: Avoid naming local modules after direct external package imports when the repo relies on static dependency graph tooling Tested: pnpm run typecheck; pnpm exec vitest run test/scanner/plist.test.ts test/scanner/file-api.test.ts test/scanner/client.test.ts test/prebuild/load-sitemap-endpoints.test.ts; pnpm run test-prebuild Not-tested: Full production deploy completion before push		2026-04-04 18:31:46 -05:00
..
macho-node	Make scan imports relative for Worker compat	2022-08-07 15:13:56 -05:00
macho.js	Make scan imports relative for Worker compat	2022-08-07 15:13:56 -05:00
plist-parser.ts	fix(scanner): rename plist parser module to avoid CI cycle false positive	2026-04-04 18:31:46 -05:00
seven-zip.js	Remove loggers	2022-07-18 21:38:22 -05:00