HTML to Structured JSON Parser

You are an expert HTML parser engineer specializing in robust data extraction from inconsistent markup.

# Task
Write a complete parser that extracts structured data from messy real-world HTML and returns clean JSON matching the user's schema. The parser must handle:

- Inconsistent markup (missing closing tags, nested wrappers, irregular nesting)
- Inline scripts, comments, and extraneous elements
- Multiple selector strategies (ID, class, data attributes, text content matching)
- Type coercion: strings to numbers, date parsing, boolean normalization
- Null for genuinely absent fields (never guess or fabricate data)

# Input HTML
```html
{{html-input}}
```

# Target Schema
```json
{{target-schema}}
```

# Requirements

## Parser Function
- Use a robust HTML parsing library (BeautifulSoup for Python, cheerio/jsdom for Node.js, Nokogiri for Ruby)
- Implement fallback selection logic: try primary selector, then alternates
- Strip whitespace, decode HTML entities
- Coerce types explicitly with error handling:
  - Numbers: parse and validate numeric strings, handle currency symbols and separators
  - Dates: support common formats (ISO 8601, MM/DD/YYYY, etc.), return ISO strings or null
  - Booleans: map "true"/"yes"/"1" and equivalents
- Return `null` for missing fields; do not infer or substitute defaults
- Handle collections: extract arrays when the schema expects them

## Validation Function
Write a separate validation function that:
- Accepts the parsed JSON and the schema
- Checks each record against schema constraints (required fields, types, formats)
- Returns a detailed report: `{ valid: boolean, errors: [{ record_index, field, issue, value }] }`
- Reports type mismatches, missing required fields, format violations

# Deliverables

1. **Parser function** with clear function signature and inline comments explaining selector logic and type coercion
2. **Validation function** with schema checking logic
3. **Example usage** showing both functions called on the input HTML, with error output if validation fails
4. **Dependencies** list (libraries required)

# Output Format
Provide clean, production-ready code with:
- Function docstrings
- Error handling (try/catch or equivalent)
- Type hints/annotations where the language supports them
- A brief comment explaining any non-obvious selector or coercion strategy

Choose the language and libraries best suited to {{language-or-auto}}, or automatically select the most appropriate stack if "auto" is specified.