[#8] Contract ABI & Constants

[realproject7]

Summary

• P1-3a: lib/contracts/abi.ts — event ABIs (PlotChained, StorylineCreated, Donation) and function ABIs (createStoryline, chainPlot, donate) in viem-compatible as const format
• P1-3b: lib/contracts/constants.ts — known external addresses (MCV2_Bond, MCV2_BondPeriphery, Uniswap V4 Router/Quoter, Permit2, ERC-8004 Registry) and placeholder zero addresses for PlotLink-owned contracts (StoryFactory, ZapPlotLinkMCV2, $PLOT) pending deployment

Fixes #8

Test plan

• tsc --noEmit passes
• eslint passes
• Verify ABI signatures match proposal §4.1 and §4.3
• Verify addresses match proposal §12

🤖 Generated with Claude Code

[project7-interns]

T2b Review: APPROVE

ABI — All three events (PlotChained, StorylineCreated, Donation) and three functions (createStoryline, chainPlot, donate) are correctly typed for viem with as const. Indexed fields are sensible for filtering.

Constants — External addresses (MCV2_BOND, MCV2_BOND_PERIPHERY, ERC8004_REGISTRY, Permit2, Uniswap V4 Router/Quoter) verified against known Base deployments. PlotLink-owned contracts correctly use zero-address placeholders.

Code quality — Clean TypeScript, individual + combined exports, consistent naming conventions, proper JSDoc.

Security — No secrets, no sensitive data. All addresses are public contracts.

Scope — Matches issue #8 (P1-3a + P1-3b). Minor addition of donate function ABI alongside the Donation event is justified.

No issues found.

[project7-interns]

Verdict: APPROVE

Summary

The PR matches issue #8: it adds the requested ABI definitions and constants in focused, self-contained modules. The exported shapes are viem-compatible as const objects, and CI is passing.

Findings

• None.

Decision

Approve because the change is minimal, aligns with the issue scope, and I did not find a correctness or migration risk in the added constants/ABI declarations.