docs: add project status section to README

[lferrigno]

Summary

Adds a Project Status section at the top of the README stating that Spawned is actively maintained and used in production by ethrex and ethlambda.

It also explains that periods without commits are expected because the core API is stable, and that new features land as those projects need them.

The goal is to answer the "is this project alive?" question upfront, as raised in #172 and #173.

[github-actions]

🤖 Kimi Code Review

I'll review this PR diff focusing on the aspects you mentioned. This appears to be a documentation-only change to the README.md.

Review: PR #174

File: README.md

Lines 10-15: The added "Project Status" section looks good and is a valuable addition for community transparency.

Minor suggestions:

• Line 13: Consider adding https:// protocol to the ethrex GitHub link for consistency with the ethlambda link (which has it). Currently: [ethrex](https://github.com/lambdaclass/ethrex) ✓ — actually this one is fine. The ethlambda link on line 14 also has https://. No issue.

• Line 13-14: The parenthetical descriptions "(Ethereum L1/L2 execution client)" and "(Lean Ethereum consensus client)" are helpful for context.

• Line 16: The phrase "periods without commits are expected (they mean things are working, not that the project is abandoned)" is excellent stakeholder management — proactively addresses a common open source concern.

No Code Issues Found

This is a documentation-only PR with no Rust code changes. There are no:

• Concurrency concerns
• Memory safety issues
• Actor lifecycle problems
• Performance implications
• API changes to review

Verdict

Approve. The addition is well-written, provides useful production-use context, and appropriately sets expectations for maintenance cadence. The links are properly formatted and the tone is professional.

If you want to be maximally thorough, you could verify the ethrex and ethlambda repositories are publicly accessible (they appear to be based on the URLs), but that's outside code review scope.

---

Automated review by Kimi (Moonshot AI) · kimi-k2.6 · custom prompt

[github-actions]

🤖 Claude Code Review

Review of PR #174: docs: add project status section to README

This PR only adds a README section and changes no code, so concurrency, lifecycle and performance don't apply.

• The #roadmap anchor resolves. ## Roadmap exists at README.md:202.
• The section placement and wording are clear and answer the "is this alive?" question up front.
• The claim that the core API is stable could be read as a semver promise. If the crate is still pre-1.0 (0.x), consider softening it to "the core API has been stable in practice". That's optional.
• "Bug reports, questions, and pull requests are welcome and get answered" is a commitment. Make sure the maintainers are happy to keep it.
• Minor style point: the parenthetical in the second paragraph is a bit long. It would read better as its own sentence.

I checked the README anchor only. I didn't verify that ethrex and ethlambda use spawned in production.

LGTM. There are no blocking issues.

---

Automated review by Claude (Anthropic) · sonnet · custom prompt

[github-actions]

🤖 Codex Code Review

Looks good to me.

• The PR only updates documentation in README.md:10.
• I don’t see any code-path changes affecting actor lifecycle, cancellation, message ordering, synchronization, timers, memory safety, or performance.
• The added status section is clear and maintainable, and it doesn’t introduce correctness or concurrency risk.

Minor note:

• README.md:12 mentions “production” and downstream projects; if that statement needs to stay precise over time, consider whether it should be phrased more timelessly or periodically revisited. Not a blocker.

No requested changes.

---

Automated review by OpenAI Codex · gpt-5.4 · custom prompt

[ElFantasma]

Roadmap is not merged into main, actually. Its PR is pending approval.