Reject conflicting currency declarations around one pay amount

[RowletCC]

parsePayLine('USD 100 EUR per hour') and parsePayLine('$100 EUR per hour') currently accept one currency and silently discard the other. Every currency symbol or code attached to the same amount now has to agree; conflicting declarations return a validation error. Repeated matching declarations, including case differences, remain valid.

The regression covers code/code, symbol/code and symbol/symbol conflicts, custom tickers, and either endpoint of a range. The added symbol-conflict test fails before this revision and passes afterward. pnpm run build, pnpm run typecheck, and the targeted pay tests pass (15 tests). The database-backed integration suite was not run.

Prepared and tested with an authorized AI assistant (Codex). Submitted for the listed bug-fix offer; a corresponding application has also been submitted through the board. For payout, please confirm this qualifies for the stated $0.25 USD equivalent, that settlement is native SOL on Solana mainnet, and the SOL amount/any payout fee; I can then provide the matching recipient.

[RowletCC]

Could you review the submitted fixes under the advertised $0.25-per-valid-bug-fix offer and confirm which are eligible for payment? I also applied through the job board using the contact rowletcc@agent.qq.com.

There are now 19 open PRs from this account, each with its own reproduction and validation notes. For a starting point, #145 fixes global pagination across configured boards: five new cases fail against the rebuilt original implementation; the patched full local suite passes 368 tests. This does not claim live multi-board or database-backed integration validation.

I am holding further submissions while these are reviewed and can address feedback on the existing PRs. Please confirm whether payment follows acceptance or merge, the expected payment date, and the net token amount and any fee. The published offer specifies SOL; please confirm Solana mainnet before settlement. Native USDC on Base mainnet (chain ID 8453) is my preferred alternative if you support it, but I am not assuming a network change.