fix: production scraper ignores structured extractor selected by qualification

[chubes4]

Problem

The same flow source produces contradictory extractor outcomes between qualification and production execution.

For Extra Chill Events flow 96 (https://www.29thstreetballroom.com/):

• wp extrachill venues requalify-flow 96 returned qualified_structured with 55 events.
• Immediate production job 801596 materialized one vision_flyer packet instead.
• The AI rejected that packet as empty / placeholder / un-dated junk.
• No structured Squarespace events reached the pipeline.

The source was originally paused for extraction_gap; DME v0.53.1 added Squarespace summary-event extraction and qualification now proves the source is extractable. The live universal_web_scraper path is not honoring the successful structured extractor/arbitration result.

Expected

Production flow execution and qualification should select the same reusable structured extractor for the same source and handler configuration. Vision fallback must not preempt a structured extractor that returns valid events.

Evidence

• Production DME version: 0.53.1
• Qualifier version: 0.56.0
• Flow: 96
• Job: 801596
• Qualification event count: 55
• Production source type: vision_flyer
• Production result: agent_skipped - source-rejected

Do not add a domain-specific exception for 29th Street Ballroom; fix generic extractor arbitration/parity.

[chubes4]

Additional production parity evidence from bounded after filing:

• Flow , St. Mazie: qualification returned 5 structured events; production returned 0 packets in job .
• Flow , Beat Kitchen: qualification returned 101 structured events; production returned 0 packets in job .

This is therefore not limited to Squarespace/vision arbitration. WordPress generic sources can also qualify through while the production handler emits nothing. The owning fix should align the test/qualification extractor chain with the actual runtime chain across supported platforms.

[chubes4]

Correction with complete evidence (the prior shell-stripped comment lost inline identifiers):

• Flow 847, St. Mazie: qualification returned 5 structured events; production universal_web_scraper returned 0 packets in job 801837.
• Flow 845, Beat Kitchen: qualification returned 101 structured events; production universal_web_scraper returned 0 packets in job 801838.

This is not limited to Squarespace/vision arbitration. WordPress generic sources can also qualify through TestEventScraper while the production handler emits nothing. The owning fix should align the test/qualification extractor chain with the actual EventImportStep runtime chain across supported platforms.

[chubes4]

Evidence correction: the St. Mazie and Beat Kitchen zero-packet run-sync results are not independently conclusive because their original async jobs were still processing and may already have claimed those identifiers. Beat Kitchen has since touched 69 venue events, confirming the runtime path did process structured items. Please disregard those two zero-packet rows as parity repros.

The original 29th Street repro remains valid and isolated: qualification returned 55 structured events, while terminal production job 801596 explicitly emitted one vision_flyer packet and rejected it as junk.