Add cursor context for EVM

[codchen]

Describe your changes and provide context

Add markdown contexts that are automatically attached whenever an agent works on relevant EVM files.

Testing performed to validate your change

n/a

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Mar 12, 2026, 1:58 PM

[Kbhat1]

Only question (discussing with other folks) is if we want this in a Agents.md vs cursor rules (so that it’s ai tool independent - cursor, Claude code, codex etc)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.39%. Comparing base (04faa6c) to head (dedf4cf).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3013      +/-   ##
==========================================
+ Coverage   58.26%   58.39%   +0.12%     
==========================================
  Files        2072     2109      +37     
  Lines      171414   173946    +2532     
==========================================
+ Hits        99882   101575    +1693     
- Misses      62602    63352     +750     
- Partials     8930     9019      +89     

Flag	Coverage Δ
sei-db	70.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 308 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[masih]

My recommendation is to:

• Use AGENTS.md instead.
• Have one in root of the repo.
• Have specialised MD files in each corresponding root package. then mention them in root.

[masih]

Name this file (annd EVM.md) AGENTS.md? similar to all other files in package level.

Essentially, the file name AGENTS.md in any hierarchy captures the agentic context, where the hierarchy makes it progressively specialised to the context itself.

[masih]

The beauty of convention means less explicit config needed; which fits the fuzzy world of agentic interaction very well (and won't go out of date quickly if we forget to update it):

Suggested change

	# EVM
	For context about EVM on Sei, refer to `x/evm/EVM.md`.
	# EVM RPC
	For EVM RPC specs, refer to `evmrpc/RPC.md`.
	When working within a specific package, always check for and read any AGENTS.md file in that package directory before making changes. These contain domain-specific architecture decisions, conventions, and constraints that supplement this top-level guide.