Produce an evidence-driven pre-match research report for Turkiye vs France in UEFA Nations League League A Group A1, scheduled for September 25, 2026. The purpose is to estimate independent fair probabilities for a paper-trading decision, not to repeat market consensus.

Investigate all items in the Required output contract above. Pay special attention to the effect of venue and crowd in Turkiye; each side's current manager and tactical changes; post-tournament rest and squad rotation; availability and expected minutes of high-impact attackers, creators, defenders, and goalkeeper; Turkiye's ability to progress or counter through France's press; France's chance creation against a compact or aggressive block; set-piece mismatches; and how an early goal, a scoreless first half, or Turkiye scoring first would change the expected match state.

Estimate fair probabilities for: Turkiye win, draw, France win after 90 minutes plus stoppage time; France win by more than 1.5 goals; France win by more than 2.5 goals; total goals over 1.5, 2.5, 3.5, 4.5, and 5.5; each team over 0.5, 1.5, and 2.5 goals; both teams to score; first-half Turkiye win, draw, and France win; first-half totals over 0.5 and 1.5; and each team to score first. Explain dependencies between markets rather than presenting them as independent bets.

For the price comparison only, use this timestamped snapshot: France win 0.71 bid / 0.72 ask; draw 0.17 / 0.18; Turkiye win 0.11 / 0.12; France by more than 1.5 goals 0.48 / 0.49; total over 2.5 goals 0.68 / 0.69; total over 3.5 goals 0.46 / 0.47; France over 1.5 team goals 0.72 / 0.74; both teams to score 0.58 / 0.59. Prices may move, so clearly separate the research estimate from this snapshot.

Conclude with the best-supported paper contract only if its conservative probability estimate exceeds the executable price by enough to cover spread, fees, model uncertainty, and a safety margin. Otherwise conclude NO BET. Include a pre-match invalidation checklist and identify which live observations could justify closing an existing position, without claiming that a live exit will be available.

Required output contract: Each panel must return a structured report with:

1. as_of_utc and data_cutoff_utc.
2. Confirmed and probable lineups, injuries, suspensions, minutes restrictions, manager changes, rest, travel, venue, and weather. Label every item as confirmed, probable, disputed, or unknown.
3. Team strength based on recent competitive matches, adjusted for opponent quality and venue. Separate underlying performance from final results.
4. Expected goals for each team (lambda_home, lambda_away) with a plausible low/base/high range and the assumptions used.
5. Fair probabilities for every requested market before inspecting the supplied market price.
6. Tactical matchup: formations, pressing, buildup, transition threat, set pieces, attack channels, defensive weaknesses, and likely game states.
7. Corners analysis: last 10 relevant competitive matches for each team, corners for and against, median and mean, home/away split, opponent-strength caveats, crossing and blocked-shot tendencies, and expected corner range. Corners are explanatory evidence only unless a tradeable corners contract exists.
8. At least three pieces of evidence against the leading thesis and the conditions that would invalidate it.
9. Source table with URL, publisher, publication/retrieval time, statistic used, sample window, and whether the source is primary. Do not invent unavailable data. Prefer official federation, UEFA, team, lineup, and recognized statistical sources.
10. Final JSON-compatible summary containing fair_probabilities, confidence, uncertainty_reasons, best_supported_contract, and no_bet_reasons.

The report must not treat bookmaker or prediction-market prices as proof of true probability. Produce independent fair probabilities first, then compare them with the supplied executable bid/ask snapshot. Do not recommend a trade when the evidence is stale, key lineups are unresolved, sources conflict materially, the estimated edge is smaller than uncertainty plus fees/spread, or executable depth cannot be verified.