docs: translate README into Spanish

[AbdulmalikAlayande]

🎯 Context & Objective

Sorokeep's README is English-only. A Spanish translation broadens reach into the large Latin American Stellar/Soroban developer community.

📝 Implementation Plan

1. Step 1: Create README.es.md with a full translation of README.md (all sections: Why This Exists, Features, Install, Quick Start, Commands, Alerting, How It Works, FAQ, Roadmap, Contributing).
2. Step 2: Keep all code blocks, command names, and flag names untranslated (only prose is translated).
3. Step 3: Add a language switcher line at the top of both README.md and README.es.md linking to each other.

🧪 Test-Driven Development (TDD) Requirements

🚨 IMPORTANT: We enforce strict Test-Driven Development. You must write your tests before implementing the logic.
Your Pull Request will not be accepted without comprehensive tests.

• Setup Test Environment: Create or locate the relevant test file.
• Write Failing Tests First: Based on the Acceptance Criteria, write your tests.
• Implementation: Implement the logic to make the tests pass.
• Edge Cases: Ensure you have tested edge cases and failure modes.

Specific Test Criteria:

• README.es.md covers every section present in README.md — no sections dropped or left in English.
• Reviewed by a native or fluent Spanish speaker before merge (note this in the PR description).

🛠️ Technical Notes

This file will go stale as README.md changes — note in the PR that translation maintenance is an ongoing commitment, not a one-time task, and consider flagging in the PR whether the contributor is willing to maintain it.

📂 Scope — Files You May Touch

Create:

• README.es.md

Edit (only what's described above — don't touch unrelated parts of these files):

• README.md — add the language-switcher line only

Do not touch:

• src/, tests/, README.pt.md, README.zh.md — coordinate switcher links via the language-switcher line only, don't edit the content of other translation files

If your solution seems to require touching something outside this list, stop and comment on the issue before proceeding — the scope may need to change, but that's a maintainer decision.

📚 Learning Resources & References

• Stellar Developers Documentation
• Soroban Smart Contracts Documentation
• Test-Driven Development (TDD) Guide

✅ Acceptance Criteria

• README.es.md covers every section of README.md.
• Reviewed by a native/fluent Spanish speaker before merge.

[nextgenuniversity1-oss]

@nextgenuniversity1-oss has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainers,
I’m interested in taking up this issue. I have experience in Full-stack web development. After reviewing the issue requirements, I believe I can implement a proper solution and follow the project guidelines.
Kindly assign the issue to me.
Thanks.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nextgenuniversity1-oss to this issue.

[ositaemmanuel653-netizen]

@ositaemmanuel653-netizen has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Here's a short application message that's direct and likely to catch the maintainers' attention:

Hi maintainer i'd like to take this on. I have experience contributing to open source and will ensure README.es.md is a complete, high-quality translation while preserving all code blocks and CLI syntax. I'll also add the language switcher, have the translation reviewed by a fluent Spanish speaker, and clearly document the ongoing maintenance commitment in the PR. Looking forward to contributing!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ositaemmanuel653-netizen to this issue.

[drips-wave]

Congratulations, @ositaemmanuel653-netizen! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @ositaemmanuel653-netizen: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[AbdulmalikAlayande]

Closed via PR #666, merged as 7dc567a on main.

The translation was solid and matched the register/conventions of the existing README.pt.md. It was based on a slightly older README (missing Global Options, the contracts command, and the Supported Channels Comparison table); filled those in to meet the "every section" acceptance criterion and added test coverage mirroring the existing Portuguese README tests.

Contributor credit stands for the great majority of the translated content — PR #665 (duplicate submission, same author) closed alongside this.

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @ositaemmanuel653-netizen as part of the Stellar Wave Program's 7th Wave 🥳

Moderator's reason: Points issued via /assess-issue override (AI decision: ESCALATE)

😎 @ositaemmanuel653-netizen: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.