Feat/abi package

[ericbsantana]

Summary

• New workspace package packages/abi/ published as @protokoll-eth/abi on npm
• Three ABIs (monadVrfAdapterAbi, monadVrfVerifierAbi, iRandomnessAdapterAbi) generated by @wagmi/cli from forge artifacts
• Versioned deployment addresses + chain metadata (activeDeployment, getDeployment, monadTestnet)
• publish-abi.yml workflow publishes on v* tag pushes with npm provenance

What's in the package

Export	What it is
monadVrfAdapterAbi	Full ABI of MonadVRFAdapter (request/fulfill, views, events, errors).
monadVrfVerifierAbi	ABI of MonadVRFVerifier.verifyProof.
iRandomnessAdapterAbi	Consumer-side fulfillRandomness(bytes32, bytes32) interface.
monadTestnet	Chain metadata: chainId, rpc, explorer, requestFee, requestFeeWei.
deployments	Versioned deployment list. active: true marks the live one.
activeDeployment	Shortcut for the entry with active: true. Currently v0.4.0.
getDeployment(version)	Look up a specific historical deployment.

Why @wagmi/cli over hand-coded ABIs

src/abis.ts is generated from packages/protokoll/out/*.json, not hand-written. The publish workflow runs forge build then wagmi generate and git diff --exit-code on src/abis.ts so a contract change without a regenerated ABI fails CI rather than shipping stale types.

Setup required before first publish

• Register the @protokoll-eth org/scope on npm (free)
• Tag v0.4.0 to trigger the publish workflow