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
..
client.test.ts	refactor(scanner): type the worker path and align app-test results	2026-04-04 14:58:25 -05:00
file-api.test.ts	refactor(scanner): type plist and file-api helpers	2026-04-04 18:13:32 -05:00
plist.test.ts	fix(scanner): rename plist parser module to avoid CI cycle false positive	2026-04-04 18:31:46 -05:00