data(cpu): recover 210 CPUs the earlier batches skipped on naming mismatches

[Seungpyo1007]

What

210 records / 240 fields (process_node 205, l3_cache_mb 35). CPU process_node coverage 56% → 61%, l3_cache_mb 54% → 55%.

Why these were missed, not missing

After #132–#135 merged, 1,737 CPUs still had no process_node — and several whole families sat at 0% filled (A-Series 213/213, Ryzen 125/125, Core 2 124/124, Opteron 103/103, Atom 78/78). That looked like absent data. It wasn't; it was three naming mismatches:

1. Model codes are not always digit-first. The table parser required a leading digit, so Core 2's E6600/Q6600 and Atom's N270/Z530 were discarded before any matching happened.
2. The Atom page has no wikitext tables at all — 244 {{cpulist}} templates — and had only ever been run through the table parser.
3. The Opteron page has a bare model-number column and no branding column, so nothing matched a family regex. The family name now comes from the page itself (that page lists only Opterons), with identity still carried by the cross-check.

Correctness

1,610 rows parsed → 1,053 matched a record → 885 passed the cross-check → 210 still had a gap to fill. Same rules as the merged batches: base clock within 0.05 GHz, TDP within 1 W, L3 must be a real cache capacity and must not equal the row's own TDP.

Spot-checked against known parts, all correct:

record	filled	correct for
i5-680, i5-660, i3-530	32 nm	Clarkdale
i7-4770R, i5-4670R	22 nm	Haswell
i7-5775R	14 nm	Broadwell
Atom 330, D410, D425	45 nm	Diamondville/Pineview
Atom D2500, D2550	32 nm	Cedarview
Opteron 1385, 2382, 8378	L3 6 MB	Shanghai

Older families were left empty on purpose. Core 2 E-series, Atom N270 and early Opteron rows did not pass the cross-check, so nothing was written for them rather than guessed — which is why no 65 nm or 130 nm values appear here at all.

All 4 source pages HTTP-verified; every record cites the page it came from. python -m app.validate → Data validation passed. Dump refreshed for the 210 changed pages only.

Closes #1

[TechEngineBot]

🔎 Data verification — Tier 0 (offline existence/trust)

Scored by app.verify; posted by TechEngineBot. Informational only — the structural gate (app.validate) is separate and authoritative for merge.

Changed records in this PR

210 record(s) scored.

%%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
    title Verification bands — all records
    "Green" : 210
    "Yellow" : 0
    "Red" : 0

Loading

Category	Distribution	Total	🟢	🟡	🔴	🟢 %
cpu	🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩	210	210	0	0	100.0%
All	🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩	210	210	0	0	100.0%

Full-dataset baseline

105742 record(s) scored.

%%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
    title Verification bands — all records
    "Green" : 14778
    "Yellow" : 89175
    "Red" : 1789

Loading

Category	Distribution	Total	🟢	🟡	🔴	🟢 %
brand	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨	207	24	183	0	11.6%
soc	🟩🟨🟨🟨🟨🟨🟥🟥🟥🟥🟥🟥	2104	123	804	1177	5.8%
smartphone	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	93396	11602	81206	588	12.4%
tablet	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	3455	174	3266	15	5.0%
watch	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	433	11	415	7	2.5%
pda	🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	140	27	112	1	19.3%
gpu	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨	2030	245	1785	0	12.1%
cpu	🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟥	3977	2572	1404	1	64.7%
All	🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	105742	14778	89175	1789	14.0%

Hard violations (forced red):

Count	Check
1	!boost_ge_base

_{green = authoritative source + complete + consistent · yellow = plausible, needs confirmation · red = sparse/weak source or a hard contradiction. Promotion to verified runs in the scheduled verify-network workflow.}

[TechEngineBot]

TechEngine change review: PASS

• PR: data(cpu): recover 210 CPUs the earlier batches skipped on naming mismatches #137
• Ref: data/cpu-specs-batch6
• Commit: 911da47
• Requested by: @Seungpyo1007
• Run: https://github.com/GetTechAPI/TechEngine/actions/runs/30506490227

Check	Result
python -m app.validate	PASS
python integrity_check.py TechAPI/data --strict	PASS

Changed data

Category	Added	Modified	Deleted	Added verified	Added unverified	Added Kaggle-sourced
brand	0	0	0	0	0	0
soc	0	0	0	0	0	0
smartphone	0	0	0	0	0	0
tablet	0	0	0	0	0	0
watch	0	0	0	0	0	0
pda	0	0	0	0	0	0
gpu	0	0	0	0	0	0
cpu	0	0	0	0	0	0

Changed record examples

• No data file changes detected.

Heuristic review

• Heuristic warnings: none found.

[TechEngineBot]

TechEngine validation stats: PASS

• PR: data(cpu): recover 210 CPUs the earlier batches skipped on naming mismatches #137
• Ref: data/cpu-specs-batch6
• Commit: 911da47
• Run: https://github.com/GetTechAPI/TechEngine/actions/runs/30506490227

Data summary

Category	Total	Verified	Unverified	Missing verified	Tracked	Verified % of tracked
brand	207	10	197	0	207	4.8%
soc	2104	123	1981	0	2104	5.8%
smartphone	93396	8453	84943	0	93396	9.1%
tablet	3455	174	3281	0	3455	5.0%
watch	433	11	422	0	433	2.5%
pda	140	27	113	0	140	19.3%
gpu	2030	244	1786	0	2030	12.0%
cpu	3977	986	2991	0	3977	24.8%
all	105742	10028	95714	0	105742	9.5%

Warning

Tracked verified coverage is below 50% for watch 2.5% (11/433), brand 4.8% (10/207), tablet 5.0% (174/3455), soc 5.8% (123/2104), smartphone 9.1% (8453/93396), all 9.5% (10028/105742), gpu 12.0% (244/2030), pda 19.3% (27/140), and 1 more.
Tracked coverage excludes records missing the verified field; see the Missing verified column for those records.
This does not fail validation. Keep imported records verified: false until manual audit, but treat this as follow-up verification work before relying on the affected categories as curated data.

Validation notes

• Full advisory outlier listings are suppressed on successful runs because they are dataset-wide and mostly stable between PRs.
• Failure runs still include a detailed log excerpt for debugging.

Key output:

## app.validate
## integrity_check.py --strict
loaded CPU=3977 GPU=2030
✅ integrity gate: no hard anomalies.

Integrity section	Flagged lines
structural	0
CPU name/tier consistency (desktop mainstream only)	0
CPU single>multi (cinebench/geekbench — should be multi>=single)	0
CPU era-vs-score outliers	8
CPU cross-source ratio outliers (possible wrong-variant)	152
GPU cross-source ratio outliers + sanity	18