docs(compliance): eERC Ecosystem-License v1.1 compliance checklist for all mainnet/L1 deliverables

[akash-mondal]

Tracker: #154

Context

The vendored ava-labs/EncryptedERC code is under the Ava Labs Ecosystem License v1.1 — use limited to Avalanche platforms and non-commercial testing/research inside the Avalanche ecosystem (README.md "License"; contracts/contracts/eerc/VENDOR.md). With the stack now live on mainnet C-Chain (43114), Fuji (43113), and BenzoNet L1 (68420), every deployed target must be confirmed Avalanche-platform-only, and the CLAUDE.md hard rule ("keep all deliverables Fuji/C-Chain/L1 scoped") must be provably upheld.

Scope

• Produce a single compliance checklist covering: every deployed network (all Avalanche-platform), the CCTP source chains (Base / Arbitrum / Optimism / Ethereum are source-burn only into Avalanche — confirm this stays in scope), the app repos (wallet / console / explorer), and any commercial-use considerations.
• Verify upstream attribution is intact (VENDOR.md) and that no deliverable deploys eERC to a non-Avalanche chain.
• Note the mainnet "real value" posture vs. the license's non-commercial testing/research framing, and flag anything needing Ava Labs clarification.

Acceptance criteria

• A checked compliance checklist artifact in docs/ covering all networks + repos + CCTP source chains.
• Explicit confirmation every eERC deployment target is Avalanche-platform-only.
• Any ambiguity (e.g. mainnet real-value vs. non-commercial framing) flagged for follow-up.

Dependencies

• Cross-cutting; informs the external-audit scope and any future non-testnet expansion.