chore(data): weekly refresh 2026-09-28

[TechEngineBot]

Weekly data refresh — 2026-09-28

Automated live re-scrape + full-dataset integrity gate + static dump.

Validation

• app.validate (schema/range/slug/FK): passed
• integrity_check.py --strict (cross-source anomaly gate): passed

Verification (Tier 0 existence/trust)

191819 record(s) assessed.

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

Loading

Category	Distribution	Total	🟢	🟡	🔴	🟢 %
brand	🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨	207	122	85	0	58.9%
soc	🟩🟩🟨🟨🟨🟨🟨🟥🟥🟥🟥🟥	2117	284	837	996	13.4%
smartphone	🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	93407	18003	75350	54	19.3%
tablet	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	3459	292	3166	1	8.4%
watch	🟩🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟥	447	94	350	3	21.0%
pda	🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨	140	83	57	0	59.3%
gpu	🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨	2076	1529	547	0	73.7%
cpu	🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨🟥	4512	4300	211	1	95.3%
laptop	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨	1995	107	1888	0	5.4%
monitor	🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨	882	0	882	0	0.0%
software	🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨	42493	366	42127	0	0.9%
website	🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨	40084	7673	32411	0	19.1%
All	🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥	191819	32853	157911	1055	17.1%

Hard violations (forced red):

Count	Check
1	!boost_ge_base

Enrichment summaries

Closes #295

[Seungpyo1007]

Closing without merging: this PR's own diff against its base is empty (the live re-scrape confirmed nothing new to add) - its only value was confirming validate.py + integrity_check.py --strict both pass end-to-end, which they do (this is the first weekly-refresh success in 5+ weeks, after #321 fixed the integrity gate). Its branch is now far behind develop (today's Atom CPU dedup, AMD additions, Intel slug fixes, and tablet/watch dedup all landed after this branch was cut), so rebasing produces 2000+ conflicts for zero net content. Re-running weekly-refresh next Monday will pick up a current base.