Say what the gem is rather than what it came from

[cardmagic]

Changes the README tagline:

Cloudflare Durable Objects, ported to Rails.

to

Self-hosted, distributed Durable Objects in Rails without a daemon using your existing SQL database.

The old line named where the idea came from. The new one names what someone gets: Durable Objects they host themselves, distributed, with no daemon to run and no database to add.

One thing left alone

solid_objects.gemspec carries the same sentence as spec.summary, which is what rubygems.org shows:

spec.summary = "Cloudflare Durable Objects, ported to Rails"

I left it, since changing a published package field is a bigger call than editing a README and was not part of the request. Say the word and I will match it here, or in its own change.

[greptile-apps]

Greptile Summary

The PR replaces the README's origin-focused tagline with a capability-focused description.

• Describes Solid Objects as self-hosted and distributed.
• Highlights use of an existing SQL database and claims no daemon is required.

Confidence Score: 4/5

The documentation claim should be corrected before merging because users can otherwise omit the required worker and leave durable asynchronous work pending indefinitely.

The new tagline says no daemon is needed, while the gem's documented asynchronous features require a continuously running solid_objects start process.

Files Needing Attention: README.md

Important Files Changed

Filename	Overview
README.md	Updates the tagline, but the new unconditional “without a daemon” claim conflicts with the documented worker requirement for asynchronous and scheduled operations.

Prompt To Fix All With AI

### Issue 1
README.md:5
**Daemon-free claim contradicts runtime requirement**

When users rely on this tagline for asynchronous or scheduled operations, the claim that no daemon is needed contradicts the required long-running `solid_objects start` worker, causing durable messages to remain pending indefinitely when that process is omitted.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Say what the gem is rather than what it ..." | Re-trigger Greptile}