coverage: Add Fintech scenarios to the Consequential Action Coverage Matrix

[rossbuckley1990-hash]

Summary

Add representative Fintech scenarios to the Consequential Action Coverage Matrix.

Why this matters

Money movement is one of the clearest examples of a consequential AI action. The matrix should visibly cover payment-style operations while remaining fully local and synthetic.

Suggested representative actions

Include safe local simulations for actions such as:

• create payment
• approve invoice
• issue refund
• transfer funds
• update bank details
• release payout

Required checks

For these scenarios, verify:

• missing proof is refused
• action mismatch is refused
• parameter mismatch is refused
• audience mismatch is refused
• expired proof is refused
• replay attempt is refused
• valid proof-bound action executes once
• Receipt or Refusal artifact is emitted

Acceptance criteria

• Fintech appears in the per-domain evidence output.
• Fintech scenario count is non-zero and documented.
• Tests pass.
• Docs clarify that this is deterministic local simulation coverage, not live provider integration or downstream financial finality.