Update ZAP_PLOTLINK to fixed routing contract

[realproject7]

Summary

• Update ZAP_PLOTLINK mainnet address to 0x7bC192848003ab1Ba286C66AFD0dd8a1729c6b02 (new contract with fixed HUNT/USDC routing)

Fixes #443

Test plan

• Constant updated in lib/contracts/constants.ts
• Frontend quote and mint flows work with new contract address

🤖 Generated with Claude Code

[project7-interns]

T2b Review: plotlink PR #444

APPROVE ✅

• Correct address (0x7bC192848003ab1Ba286C66AFD0dd8a1729c6b02) matches deployed contract
• Only mainnet constant changed, testnet untouched
• Single file, 1-line change — clean and minimal
• Address format is valid checksummed EIP-55

No issues found.

[project7-interns]

Verdict: REQUEST CHANGES

Summary

This constant update is mechanically correct relative to the current deploy note, but it is pointing the frontend at a contract deployment that is not ready to merge yet. The linked contract PR still has blocking review issues, so this address should not be finalized here yet.

Findings

• [high] ZAP_PLOTLINK is being switched to the deployment from plotlink-contracts PR #60 before that contract PR is approved. Since PR #60 still has blocking issues (failed required check and unresolved routing/pool mismatch), merging this constant now would bake in an address that may change on redeploy.
  • File: lib/contracts/constants.ts:40
  • Suggestion: Hold this PR until the contract PR is fixed and the final approved mainnet deployment address is known, then update the constant to that final address.

Decision

Requesting changes because this PR depends on an unresolved contract deployment and should be updated only after the contract PR is corrected and finalized.

[project7-interns]

Verdict: APPROVE

Summary

This frontend PR is now aligned with the latest approved contract deployment state. The constant update is minimal and the checks are green.

Findings

• [resolved] Dependency on unresolved contract deployment is gone.
  • File: lib/contracts/constants.ts:40
  • Suggestion: None. The PR now points at the finalized approved deployment address.

Decision

Approving because the change is correct and appropriately scoped.