[MissHarah]

• escalate_claim already guards with ClaimStatus::Pending check; this commit hardens the surrounding code that was preventing compilation:
  • Add policy_engine() private helper (was called but undefined)
  • Add get_product() to IPolicyEngine cross-contract client trait
  • Add InvalidClaimAmount (=33) and DisputeReasonTooLong (=34) to Error enum
  • Fix dispute_claim event: use caller.clone() instead of undefined claimant
• Fix test.rs: remove ~370 duplicate lines (lines 724-1092 were an accidental copy-paste of lines 360-726), fix two stacked attribute pairs
• Add four targeted tests for issue [security] ClaimsProcessor does not validate escalation claim status is Pending #628:
  • rejected_claim_cannot_be_escalated
  • disputed_claim_cannot_be_escalated
  • escalated_claim_cannot_be_escalated_again
  • partially_paid_claim_cannot_be_escalated All four assert NotEscalatable (governance-dao.rs: no voting power tracking — anyone can vote multiple times in a single proposal #17) for non-Pending status
    Closes [security] ClaimsProcessor does not validate escalation claim status is Pending #628
    Closes [bug] PolicyEngine does not validate coverage_min > 0 #629

[drips-wave]

@MissHarah Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits