Drop the last stale nothing-released claim from README

[thedavidmeister]

The tag-release aftermath reword ruled on #11 (CodeRabbit thread on README.md:29): the deploy-surface bullet still called the released-suites record "currently empty because nothing is released yet", which sol-v0.1.1 falsified.

This is a cherry-pick of 6d9c0e1 from the cut branch — that commit was pushed to #11 two minutes after the merge landed at 77f6fd5, so it reached the branch but not main. Doc-only: one sentence trimmed, no behaviour, no generated files.

QA

• Discriminating tests: n/a — a one-sentence README trim; no test can discriminate prose. The check that stands in for one: a repo-wide sweep for released-yet / nothing-released / not-released variants over *.md, *.toml, *.sol, *.rs, *.ts, *.json (excluding dependencies) comes back empty after this line and hits this line before it.
• Mutations applied: n/a — docs-only diff, no logic to mutate.
• Oracle: the repo's own release record — src/generated/0_1_1/ is frozen on main and Soldeer holds rain-math-float-deploy 0.1.1 (published 2026-08-22T12:16:51Z by run 32572473272), so "nothing is released yet" is externally false, independent of this diff.
• Category check: the ruled work is the reword the Cut release 0.1.1: version bump + frozen src/generated/0_1_1/ in lockstep #11 thread deferred to tag-release aftermath; covered — the stale sentence, and nothing else (the other stale claims were already dropped in Cut release 0.1.1: version bump + frozen src/generated/0_1_1/ in lockstep #11 itself).

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@thedavidmeister, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ae6e6c29-363b-4cde-b8ba-b2c0f94789a7

📥 Commits

Reviewing files that changed from the base of the PR and between 8f7126e and 4cdc349.

📒 Files selected for processing (1)

• README.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}