Skip to content

docs: expand book metrics pages with fuller explanations - #42

Merged
BraCR10 merged 1 commit into
developmentfrom
docs/book-metrics-prose
Jul 30, 2026
Merged

docs: expand book metrics pages with fuller explanations#42
BraCR10 merged 1 commit into
developmentfrom
docs/book-metrics-prose

Conversation

@BraCR10

@BraCR10 BraCR10 commented Jul 30, 2026

Copy link
Copy Markdown
Member

Summary

Rewrites book/src/metrics/*.md as narrative prose instead of terse bullet fragments.
Each metric now explains what it measures, how to interpret the number, and the exact
Nostr event kind/tag it's computed from.

Test plan

  • mdbook build succeeds with no warnings

Rewrites the metrics section as narrative prose instead of terse
bullet fragments: what each metric is, how to interpret it, and its
exact Nostr event/tag source, for longevity/liveness, trade
size/consistency, disputes/bond policy, fiat/payment-method/premium,
and the activity grid.
@BraCR10
BraCR10 merged commit d2fb59d into development Jul 30, 2026
3 checks passed
@BraCR10
BraCR10 deleted the docs/book-metrics-prose branch July 30, 2026 13:17
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0dd97c2f-580e-4f46-8de9-7749099d6587

📥 Commits

Reviewing files that changed from the base of the PR and between e1ccb44 and ad8a8ce.

📒 Files selected for processing (7)
  • book/src/installation.md
  • book/src/metrics/README.md
  • book/src/metrics/activity-grid.md
  • book/src/metrics/context-signals.md
  • book/src/metrics/disputes-bond-policy.md
  • book/src/metrics/longevity-liveness.md
  • book/src/metrics/trade-size-consistency.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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant