[bamiebot-maker]

Description

In \contracts/remittance_nft/src/lib.rs, \RemittanceNFT::mint\ and \RemittanceNFT::admin_remint\ clamp the stored credit score to [MIN_CREDIT_SCORE, MAX_SCORE]\ ([300, 850]), but previously emitted the raw unclamped \initial_score\ in the \Mint\ and \AdmRemint\ events.

Changes

• Updated \Mint\ event publishing in \RemittanceNFT::mint\ to publish (metadata.score, recipient_commitment)\ instead of (initial_score, recipient_commitment).
• Updated \AdmRemint\ event publishing in \RemittanceNFT::admin_remint\ to publish (metadata.score, recipient_commitment)\ instead of (initial_score, recipient_commitment).
• Added unit test \ est_mint_and_admin_remint_emit_clamped_score_event\ in \contracts/remittance_nft/src/test.rs\ asserting that out-of-bounds initial scores (< 300\ and > 850) emit clamped values (\300\ and \850) in both event payloads.

Closes #2000

[bamiebot-maker]

mc resolved