docs: align README and contributor templates (PLT-839)

[alexander-sei]

Summary

• align the root README with the current Bun-based, EVM-first package set
• replace obsolete seid and removed-package prompts in the bug report template
• add a pull request template with the repository's current checks and release checklist

Related issue

PLT-839

Test plan

• bun run check
• git diff --check

Changeset not required because this only updates repository documentation and contribution templates.

Made with Cursor

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.82%. Comparing base (5675fcf) to head (86c8e08).

Additional details and impacted files

@@ Coverage Diff @@## main #332 +/- ##
=======================================
Coverage 83.82% 83.82% =======================================
Files 64 64 Lines 4390 4390 =======================================
Hits 3680 3680 Misses 710 710 

Flag	Coverage Δ
mcp-server	77.28% <ø> (ø)
precompiles	100.00% <ø> (ø)
registry	100.00% <ø> (ø)
sei-global-wallet	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 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.

[seidroid]

Docs-and-templates-only PR that accurately corrects real drift: the removed cosmos/seid references match the current EVM-only create-sei, all five README package rows match the actual tree, and the new PR template references root scripts that exist. Nothing blocking; one wording nit and a note that the Cursor pass returned no output.

Findings: 0 blocking | 5 non-blocking | 2 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• The Cursor second-opinion pass (cursor-review.md) produced no output — this review reflects only my own findings plus Codex's, which reported no material issues.
• No changeset is present, which is correct here per REVIEW_GUIDELINES §3 (docs- and CI-only changes don't need one). The author called this out in the PR body; noting it only so it isn't re-raised.
• The new bug report template asks reporters to remove private keys and seed phrases before pasting logs — a good addition given mcp-server reads signing keys from the environment. Consider mirroring that warning in the PR template's Test plan section, since debugging output gets pasted there too.
• 2 suggestion(s)/nit(s) flagged inline on specific lines.

[seidroid]

[nit] Nit: "for building EVM applications on Sei" slightly under-sells @sei-js/registry, which vends chain constants, tokens and wallet metadata sourced from the cosmos chain-registry / community-assetlist submodules and isn't EVM-specific. The narrowing is accurate for the other four packages (create-sei really is EVM-only now — no cosmos/cosmjs references remain in its src/), so this is just a tagline-precision point. Something like "for building on Sei, with first-class EVM support" would cover registry too. Non-blocking.

[seidroid]

[nit] Good that the checklist calls out Changesets explicitly — that's the most common miss on this repo (a published package's behavior changing with no .changeset/*.md ships code without releasing it). Might be worth linking .changeset/config.json or noting bun run changeset inline so contributors know the command, since there's no CONTRIBUTING.md in the repo to point at. Non-blocking.