Use trust-based commercial licensing copy

[justin808]

Summary

• Update the React on Rails Pro page to use ShakaCode Trust-Based Commercial Licensing wording.
• Update generated docs injection copy from the old friendly-license wording to the trust-based commercial licensing term.
• Add tests that assert the new terminology, private-business-value positioning, and React on Rails Pro EULA distinction.

Why

Issue #138 asks reactonrails.com to use ShakaCode Trust-Based Commercial Licensing consistently and avoid public Honest License branding. This keeps evaluation/learning language clear while preserving the product-specific legal terms for React on Rails Pro.

Closes #138

Test plan

• npm run sync:docs
• npm run prepare:docs
• npm run install:site
• .agents/bin/validate
• node --test scripts/prepare-docs.test.mjs

Codex Decision Log

• Non-blocking: npm run prepare:docs regenerated prototypes/docusaurus/sidebars.ts from upstream.
  • Decision: Do not commit that generated sidebar drift in this PR.
  • Why: Use Trust-Based Commercial Licensing on reactonrails.com #138 is scoped to site-owned licensing copy and prepare-docs injection/tests; sidebar drift is unrelated generated navigation churn.
  • Review later: Handle generated sidebar refresh in the navigation/migration-guide lane or an upstream docs sync PR if needed.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 13 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

Run ID: 4e90125a-ae81-436f-a4ab-ed17c88612c7

📥 Commits

Reviewing files that changed from the base of the PR and between e39bb81 and ed43c74.

📒 Files selected for processing (3)

• prototypes/docusaurus/src/pages/pro.tsx
• scripts/prepare-docs.mjs
• scripts/prepare-docs.test.mjs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/docs/issue-138-trust-based-licensing

---

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

[greptile-apps]

Greptile Summary

This PR updates React on Rails Pro licensing copy across the site and generated docs.

• Rewords the Pro page around ShakaCode Trust-Based Commercial Licensing.
• Renames the Pro docs notice injection helper.
• Updates generated docs homepage licensing text.
• Adds tests for the new terminology and old-term removal.

Confidence Score: 4/5

The docs-generation path needs a small fix before merging.

• Existing wrapped legacy notices can remain beside the new notice.
• A README without a matching licensing heading can skip the new homepage section.
• The static page copy changes do not introduce a runtime risk.

scripts/prepare-docs.mjs

Important Files Changed

Filename	Overview
prototypes/docusaurus/src/pages/pro.tsx	Static Pro page copy now uses trust-based commercial licensing language.
scripts/prepare-docs.mjs	Docs injection now emits trust-based licensing copy, but the replacement paths can miss stale or absent source sections.
scripts/prepare-docs.test.mjs	Tests assert the new terminology, but they do not cover legacy notice replacement edge cases.

_{Reviews (1): Last reviewed commit: "Use trust-based licensing copy" | Re-trigger Greptile}

[github-actions]

Cloudflare preview deployed.

• Branch: pr-145
• URL: https://c14d0230.reactonrails-com.pages.dev

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 14fe165ff4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d7978570ac

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[justin808]

Codex closeout evidence for current head ed43c74f2bac8f88ad1cdd10b646dc2b51c82eaa:

• Local validation: node --test scripts/prepare-docs.test.mjs; npm run prepare:docs; .agents/bin/validate passed. Docusaurus emitted the existing broken-link/broken-anchor warnings, but exited 0.
• Local smoke: built /pro/, /docs/pro/, and /docs/ contain ShakaCode Trust-Based Commercial Licensing, private-business-value wording, and React on Rails Pro EULA wording; legacy Honest/Friendly wording is absent.
• Hosted checks: CodeRabbit, build, and deploy all pass.
• Hosted preview smoke: https://c14d0230.reactonrails-com.pages.dev/pro/, /docs/pro/, and /docs/ returned OK with the expected licensing copy and no legacy Honest/Friendly wording.
• Review threads: Greptile/Codex threads resolved after fixes for multi-line legacy notices, missing homepage insertion, existing Pro Trust-Based section normalization, and compact legacy homepage headings.
• Merge state: CLEAN; review decision APPROVED.

Final state with merge_authority=ask: ready-no-merge-authority.