Fix normalizeSelector to validate input type and reject arrays

[konard]

Summary

• Add input type validation to normalizeSelector to prevent downstream querySelectorAll errors
• Return null with a warning for arrays and invalid object types
• Only accept strings and valid Puppeteer text selector objects
• Add comprehensive test coverage for the new validation behavior

Problem

When normalizeSelector received an array input (which should be invalid), it returned the array unchanged instead of throwing an error or returning null. This caused downstream querySelectorAll calls to fail with:

SyntaxError: Failed to execute 'querySelectorAll' on 'Document': '[data-qa="vacancy-serp__vacancy_response"],' is not a valid selector

Solution

Added explicit type validation at the start of normalizeSelector:

• Arrays are now detected and rejected with a warning
• Non-string, non-_isPuppeteerTextSelector objects are rejected
• Valid inputs (strings and Puppeteer text selector objects) continue to work as before

Test plan

• Run npm run test:unit - all 368 tests pass
• Run npm run lint - no new errors
• Added tests for array, number, and invalid object rejection
• Added test for valid Puppeteer text selector object acceptance

Fixes #23

🤖 Generated with Claude Code

[konard]

⚠️ Solution Draft Finished with Errors

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

• Public pricing estimate: $3.432332 USD
• Calculated by Anthropic: $0.000000 USD
• Difference: $-3.432332 (-100.00%)

Note: The session encountered errors during execution, but some work may have been completed. Please review the changes carefully.

📎 Log file uploaded as Gist (518KB)
🔗 View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.