fix(public): disambiguate Tiny Studio identity on every public page and llms.txt - #59
fix(public): disambiguate Tiny Studio identity on every public page and llms.txt#59nish3451 wants to merge 16 commits into
Conversation
…ge and llms.txt PR #29 fixed only the homepage. Google AI Overviews can surface any tinystudio.in page, so the Organization entity on the other 11 public pages and the AI-facing llms.txt now carry the same identity statement: Tiny Studio is the independent product company at tinystudio.in behind Promptly, Drishti, and 0509 and is not affiliated with any other app or studio using the name. Keeps the generator template in prepare-static-site-bundle.mjs in sync with the committed llms.txt.
Extends the brand disambiguation test from homepage-only to the whole public surface: every deployed page's Organization entity must carry the alternateName and the not-affiliated description, and both the committed llms.txt and its generator template must keep the identity statement, so the AI-facing file cannot silently drift back.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (14)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
1 participant
Closes the AI-answer brand confusion item: Google AI answers conflate Tiny Studio / tinystudio.in with unrelated tiny-studio brands.
PR #29 fixed the homepage only. AI Overviews can surface any page, so this extends the disambiguation to the full public surface:
Organizationentity now carriesalternateName(tinystudio.in) and the disambiguating description naming the unique products (Promptly, Drishti, 0509) and stating the non-affiliation with other tiny-studio brands.public/llms.txt— the AI-facing context file — now states the identity and non-affiliation, and its generator template inscripts/prepare-static-site-bundle.mjsstays in sync.scripts/test-public-brand-disambiguation.mjs): every deployed page's Organization node must carry the identity, and both llms.txt and its generator must keep the statement; wired intonpm test/npm run ci.Verified:
npm testpasses end-to-end (0 failures);git diff --checkclean.