feat(h2): direct per-parameter SETTINGS comparison in browser_matcher
- Rewrote _d1_h2_settings() with 3-signal weighted formula:
direct_score×0.60 + dict_match×0.30 + ja4_coherence×0.10
when individual SETTINGS cols are available in the DataFrame
- Added _H2_SETTINGS_COLS dict (IDs 1,2,3,4,5,6,8 → column names)
- Fallback to dict_match×0.80 + ja4_coherence×0.20 for backward compat
- Fix view_ai_features_1h: pass 7 individual SETTINGS columns through
base_data CTE (h2_header_table_size, h2_enable_push,
h2_max_concurrent_streams, h2_initial_window_size, h2_max_frame_size,
h2_max_header_list_size, h2_enable_connect_protocol)
- Remove non-existent h2_dict_confidence reference from view SQL
(dict_browser_h2 only exposes browser_family attribute)
- Add 7 new pytest cases: exact match, one wrong setting, forbidden key
penalty, unknown fingerprint with correct settings, fallback path,
CDN proxy neutralisation, full Chrome simulation
- 53/53 bot-detector tests pass
- Update thesis §3.9.2: document direct comparison algorithm + fallback
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
f704541f83