[Bug]: [wallet_screening]: card.json ui_schema keys do not match skill output

[rosspeili]

Affected Component

Specific Skill (e.g. Wallet Screening)

Skill Name (if applicable)

finance/wallet_screening

Bug Description

skills/finance/wallet_screening/card.json ui_schema.fields reference output paths that do not exist in _generate_report_data() output after recent schema/doc corrections (#165, #173).

Stale keys include:

• summary.address (address is under metadata.wallet_address)
• summary.sanctioned (actual field: summary.sanctioned_entity_match)
• summary.malicious_interactions_count (actual: summary.malicious_interaction_count)
• summary.pnl_eth (actual: financial_analysis.pnl_eth)

Any UI or agent tooling that reads card.json for field binding will show empty or wrong data.

Steps to Reproduce

1. Load skills/finance/wallet_screening/card.json.
2. Compare ui_schema.fields[].key to keys returned by WalletScreeningSkill().execute(...) (see mocked test in tests/skills/finance/test_wallet_screening.py).
3. Observe mismatched paths for address, sanction flag, interaction count, and PnL.

Error Logs

No traceback — silent UI/schema drift. Compare against `skill.py` `_generate_report_data()` return structure.

Environment

main @ 0.3.6
All platforms

[rosspeili]

finance/wallet_screening looks fixed on main after #175 (card.json keys match real output). You can close that part or the whole issue if nothing else is failing.

Suggest widening scope: audit every registry skill that has card.json → check each ui_schema.fields[].key against mocked execute() output (same idea as wallet_screening). Optional: small CI test so this doesn’t drift again.