Add EVM compatibility issue template

Author: monty-sei

.github/ISSUE_TEMPLATE/evm_compatibility.md

@@ -0,0 +1,40 @@
+---
+name: EVM compatibility
+about: Report behavior that differs from expected EVM tooling or RPC compatibility
+title: "[EVM-COMPAT] "
+labels: evm-compat, linear
+assignees: ''
+
+---
+
+**Library or tool**
+Which library, connector, RPC method, template, or docs page is involved?
+
+**SeiJS package and version**
+Check your `package.json` for the package name and version.
+
+**Network**
+Mainnet, testnet, devnet, local, or unknown.
+
+**Expected EVM behavior**
+What behavior did you expect from standard EVM tooling?
+
+**Observed Sei behavior**
+What happened instead?
+
+**Minimal reproduction**
+Provide the smallest code sample, command, RPC payload, or repository link that reproduces the issue.
+
+**Error output or transaction hash**
+Paste the relevant error, RPC response, transaction hash, or receipt.
+
+**Classification**
+If known, choose one:
+- SDK gap
+- Network issue
+- Upstream issue
+- Docs issue
+- Intentional divergence
+
+**Additional context**
+Add any other context that may help with triage.

docs/evm-parity/issue-sla.mdx

@@ -12,6 +12,8 @@ The operational target is simple: no open GitHub issue tagged `evm-compat` shoul
 
 Use `evm-compat` for reports where a developer expected standard EVM behavior through viem, wagmi, ethers, wallet connectors, JSON-RPC, or common ERC/token flows.
 
+Use the GitHub issue template named **EVM compatibility** for new reports.
+
 ## Required Triage Fields
 
 Each issue should include: