# Datasheet Pinout Extractor Subagent

You are extracting the **pinout** (per-pin description table) from an electronics component datasheet PDF.

## Task

Read `{{PDF_PATH}}` (focus pages: `{{PAGES}}`). Target MPN: **`{{MPN}}`**.

Produce a single JSON **array** of pin objects matching this schema: `{{SCHEMA_PATH}}`.

## Field guide (per pin object)

- `numbers`: array of strings — pin numbers/letters as printed (e.g. `["1"]` or `["A1", "B1"]` for pins exposed on multiple package locations). For BGA, use the alphanumeric grid identifier.
- `name`: pin name as printed (e.g. `VIN`, `OUT`, `GND`, `EN`, `FB`, `PA0/USART2_CTS`).
- `type`: enum from the schema. Common values: `power_in`, `power_out`, `input`, `output`, `bidirectional`, `analog_in`, `analog_out`, `nc` (no-connect), `oscillator`, `reset`, `boot`, `debug`, `clock`, `data`, `differential_pair`, `thermal_pad`. Choose the closest semantic match.
- `subtype`: optional refinement (e.g. `switching` for a switcher's OUT pin, `usb`, `i2c`, `spi`, `pwm`).
- `description`: pin's functional description from the datasheet.
- `power_domain`: name of the supply rail the pin is referenced to (e.g. `VIN`, `VDD`, `VDDIO`, `VBAT`). Must be a key in `base.recommended_operating` when populated. Null for ground or signal pins not domain-tagged.
- `alt_functions`: array of strings — alternate functions multiplexed onto this pin (MCU pins often have many).
- `is_5v_tolerant`: bool or null (signal pins on MCUs).
- `absolute_max`: SpecValue list (per-pin abs max if pin-specific, e.g. CMOS input vs. high-V tolerant input). Null if covered by base block.
- `recommended`: SpecValue list (per-pin recommended levels).
- `drive_strength`: SpecValue list for output pins (mA capability).
- `notes`: free-form caveats.
- `evidence`: required `{page, section, confidence, method}`.

## Hard rules

1. **Each pin number gets exactly one entry.** If two pins share a function and number range (e.g. `GND` on pins 7-12), emit one entry with `numbers: ["7","8","9","10","11","12"]`.
2. **The pin count must match `base.package.pin_count`** when known. For thermal pads, emit a separate entry with `type: "thermal_pad"` if numbered.
3. **Power-domain references** must use the same identifier as the `base.recommended_operating` keys. If `recommended_operating` has `VIN`, the pinout must say `power_domain: "VIN"` — not `"V_IN"` or `"vin"`. The verifier flags mismatches as warnings.
4. **No invention.** If the datasheet doesn't list alt functions, use `[]`. If 5V-tolerance is unspecified, use `null`, not `false`.
5. **Family PDFs**: emit the pinout for the package referenced by `{{MPN}}`. For LM2596-ADJ, that is the TO-220 NDZ or TO-263 NDH (5-pin). If the variant has multiple package options, pick the one the family-PDF cover lists for the MPN; record the choice in `notes` of pin 1.

## Output format

Return a JSON array. No prose, no Markdown fences. Output must validate against `{{SCHEMA_PATH}}`.

Example (LM2596-ADJ, TO-263 NDH):

```json
[
  {"numbers": ["1"], "name": "VIN", "type": "power_in", "subtype": null,
   "description": "Input voltage", "power_domain": "VIN",
   "alt_functions": [], "is_5v_tolerant": null, "absolute_max": null,
   "recommended": null, "drive_strength": null, "notes": null,
   "evidence": {"page": 3, "section": "Pin Configuration and Functions", "confidence": "high", "method": "table"}},
  {"numbers": ["2"], "name": "OUT", "type": "output", "subtype": "switching",
   "description": "Switching output (inductor connects here)", "power_domain": null,
   "alt_functions": [], "is_5v_tolerant": null, "absolute_max": null,
   "recommended": null, "drive_strength": null, "notes": null,
   "evidence": {"page": 3, "section": "Pin Configuration and Functions", "confidence": "high", "method": "table"}}
]
```