Fix royalty ABI: correct parameter order and return values

[realproject7]

Summary

• Fix getRoyaltyInfo ABI: inputs changed from (token, beneficiary) to (wallet, reserveToken), outputs from single uint256 to (balance, claimed)
• Fix claimRoyalties ABI: pass reserve token address (PLOT_TOKEN) instead of storyline token
• Update ClaimRoyalties.tsx: swap args to getRoyaltyInfo(beneficiary, PLOT_TOKEN), destructure [balance] from tuple return, call claimRoyalties(PLOT_TOKEN)

Fixes #261

Test plan

• Writer dashboard shows non-zero royalties after trades occur
• Claim button successfully claims royalties
• getRoyaltyInfo called with (writerAddress, PLOT_TOKEN) — verified in contract call
• npm run typecheck passes

🤖 Generated with Claude Code

[project7-interns]

APPROVE

ABI fix is correct and minimal:

1. getRoyaltyInfo: Inputs reordered to (wallet, reserveToken), outputs now tuple (balance, claimed). Call site correctly swaps to (beneficiary, PLOT_TOKEN) and destructures [balance].

2. claimRoyalties: Now takes PLOT_TOKEN (reserve token) instead of tokenAddress (storyline token). Matches the actual MCV2_Royalty contract signature.

3. Query key: Still uses [tokenAddress, beneficiary] which is correct — PLOT_TOKEN is a constant so doesn't affect cache invalidation; the key properly varies by storyline context and wallet.

No issues found.

[project7-interns]

Verdict: APPROVE

Summary

The PR fixes the ABI mismatch and updates the dashboard call sites to use the reserve-token-based royalty contract interface. The change is tightly scoped to the royalty read/claim path.

Findings

• [info] No blocking issues found.

Decision

Approve. lib/price.ts now matches the contract signature, and ClaimRoyalties.tsx calls/destructures the royalty methods with the correct argument order and return values. CI was still pending when reviewed.