[P23] [Transfer] Учитывать уровень лиги Transfermarkt в анализе трансферов и потенциала

[MostDef2000]

Decision

NEW TASK

Responsible agent

SLF Transfer Analyzer Agent

Author note

Пользователь: "для анализа трансферов и в потенциал добавить расчет лиги с ТМ"

Screenshot/context:
Transfermarkt club card can expose league/tier information, for example:

• League level: Fourth Tier
• country flag / competition context
• contract data near club block

Problem

Transfer analysis and potential evaluation currently do not explicitly account for the player's current league level from Transfermarkt. A player performing in a lower-tier league should not be interpreted the same way as a player with the same raw attributes/value context in a higher-tier league.

Expected behavior

Transfer Analyzer should read/derive league level from Transfermarkt enrichment where available and use it as an additional context factor in:

• transfer analysis;
• player potential estimate;
• valuation/verdict explanation;
• tooltip/details, if relevant.

The logic should not blindly penalize all lower-tier players. League level should be a contextual confidence/modifier signal, not a hard rejection rule.

Scope

Transfer Analyzer only.

Likely relevant areas:

• Transfermarkt enrichment layer;
• transfer details/tooltip parsing;
• potential/valuation calculation;
• transfer verdict text.

Out of scope

• Team Management modules;
• Strategy Data / recommendation engine;
• live parser;
• release files;
• manual version bump;
• changing external API/server data.

First return

DISCUSSION ONLY.

Agent should return:

1. Branch Freshness Check.
2. Identify where TM club/league info is currently parsed or stored.
3. Determine whether League level is already available in cached/enriched TM data.
4. Propose a normalized representation, e.g.:
   • First Tier
   • Second Tier
   • Third Tier
   • Fourth Tier
   • Unknown
5. Propose how league level should affect potential/transfer analysis.
6. State required changed files.
7. State cache/schema/storage impact.
8. State bundle-order/module-registry impact.
9. Acceptance checks.
10. Ask for COMMIT APPROVED before writing.

Acceptance checks

• TM league level is parsed when available from Transfermarkt/club block.
• Example League level: Fourth Tier is recognized as fourth-tier context.
• Potential/transfer explanation includes league-level context when available.
• Missing league level does not break transfer analysis.
• Cached/enriched records remain backward compatible or migration/fallback is documented.
• No Team Management files changed.
• No Strategy Data files changed.
• No release artifacts changed.
• No version bump from module branch.

PM planning

Complexity: M
Risk: medium
Recommended order: 2
Type: Feature
Reason:

• Requires parsing/enrichment review and a bounded scoring/verdict adjustment.
• Risk is medium because it may affect transfer recommendations and valuation confidence, but should be contained to Transfer Analyzer.

Notes

This task should treat league level as a confidence/context feature. Do not invent exact scoring weights without discussion first.