fix(verify): use source chipset year for late SoC placeholders

[Seungpyo1007]

Finding

The remaining soc_not_after_device near misses are dominated by SoC-side placeholder dates, not a need for a wider year tolerance. In the 2026-09-23 TechAPI scores.jsonl snapshot, 472 yellow records with score 65–74 and a T1/T2 host carry the flag; 471 reference a YYYY-01-01 SoC date. The SoC raw_chipset field contains a structured, earlier chipset year for 417 of them (for example, Snapdragon 680: normalized 2025, raw 2021; Snapdragon 210: normalized 2018, raw 2014). Their device dates agree with that source year under the existing two-year placeholder tolerance.

Change

When building the SoC release-date lookup, use the year embedded in the SoC's raw_chipset text only if it follows the import's name, YYYY, ... format and is earlier than a normalized January 1 placeholder. Keep exact dates, absent or unstructured raw text, and the existing two-year tolerance unchanged. This preserves flags for a 2015 device referencing Snapdragon 8s Gen 3 (2024) and a 2023 device referencing a day-precise 2024 Dimensity release.

Estimated impact

Replaying the current scorer against those 472 records resolves the flag for 417. Of those, 413 move from yellow to green; four already score green against current files but remain yellow in the stale scores cache. The other 55 remain flagged, primarily where raw_chipset has no year, and need data-side review. No TechAPI files were modified.

Verification

• python -m pytest tests/verify/test_common_soc_dates.py tests/verify/test_signals.py -q --confcutdir=tests/verify — 22 passed.
• python -m ruff check app/verify/common.py tests/verify/test_common_soc_dates.py — passed.
• python -m mypy app/verify/common.py — passed.

[Seungpyo1007]

Refs GetTechAPI/TechAPI#1 (verify-layer near-miss investigation: soc_not_after_device false placeholder-date signal, 472-record sample -> 413 newly green).