Harden contributions and update community credits and UI - #60
Merged
Merged
Conversation
TeoSlayer
enabled auto-merge (squash)
September 17, 2026 19:01
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Community contributions now require authentication and are capped at 1,000 new webpages per account in a rolling 24 hours, shared by URL, CSV, and local-artifact submissions. Oversized batches roll back atomically; duplicates consume no quota, and limit errors include retry guidance. The crawler verifies that the content it indexes and rewards matches the exact content approved by moderation, including refetches, receipts, and concurrent replacements.
Accounts receive 1,000 free credits per UTC month on top of the existing free request allowance. Extra Search, Answer, and Research requests debit 1, 2, and 3 credits respectively. The web app shows monthly activity, a dedicated billing view, and agent setup documentation and skills. Layout and controls have consistent spacing, session validation uses a loading/retry screen, failed submissions preserve their inputs, and optional GA configuration is validated. Stripe test keys cannot mint production credits by default.
Validation: community, crawler, server, and CLI race tests passed; 18 browser-logic regressions passed; the production ARM64 target builds. Tests cover monthly-grant concurrency and restart boundaries, quota rollback across all contribution formats, weighted debit/refund accounting, content-change rejection, session failures, and payment replay/signatures. Local browser checks covered registration, onboarding, the monthly grant, and layout. Production deployment will keep contributions paused until the engine and gateway both enforce the new content approval checks.