docs: clarify sflr-exchange-rate meta direction and add input arity

[thedavidmeister]

Summary

The sflr-exchange-rate authoring meta description had two gaps:

#104 (direction ambiguity): "Returns the current exchange rate of FLR to SFLR." doesn't state which token is the numerator. The runtime returns getSharesByPooledFlr(1e18) — sFLR-per-FLR. An author reading it as FLR-per-sFLR would invert their math.

#95 (input count): ftso-current-price-usd says "Accepts 2 inputs" and ftso-current-price-pair says "Accepts 3 inputs". sflr-exchange-rate said nothing, leaving tooling consumers without a consistent in-meta arity signal.

New description: "Returns the current sFLR per FLR exchange rate self-reported by the Sceptre staked FLR contract, i.e. how many sFLR shares correspond to 1 FLR. A value less than 1 means 1 FLR yields fewer than 1 sFLR share. Accepts 0 inputs."

SUB_PARSER_PARSE_META is unaffected — it is built from word names only (bloom filter / fingerprint), not descriptions.

Note: PR #130 adds testAuthoringMetaV2Content which pins the old description. Once this PR merges, that test's sflr-exchange-rate assertion must be updated to the new string before PR #130 can merge.

Closes #95
Closes #104

Co-Authored-By: Claude noreply@anthropic.com

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 35 minutes and 31 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 6d2b5e08-d292-4d95-857f-ce868aaa63cb

📥 Commits

Reviewing files that changed from the base of the PR and between cb20d03 and 107a0b3.

⛔ Files ignored due to path filters (1)

• src/generated/FlareFtsoWords.pointers.sol is excluded by !**/generated/**

📒 Files selected for processing (3)

• meta/FlareFtsoSubParserAuthoringMeta.rain.meta
• meta/FlareFtsoWords.rain.meta
• src/lib/parse/LibFlareFtsoSubParser.sol

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/issue-95-104-sflr-meta-description

---

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 and usage tips.}

[thedavidmeister]

🤖 ai:vetter
Reviewed 107a0b3: ready — Meta description corrected to sFLR-per-FLR with explicit input arity; binary artifacts and hashes re
cost 142 — doc string change plus codegen-checked regenerated artifacts