evidence(ai-search): controlled entity-and-offer re-run with first Found transitions (2026-08-15) - #227
Conversation
|
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.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 3 minutes Limit details: You’ve used the included review currently available. 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 within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (5)
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.
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.
… on current main and live (2026-08-15, lane 1) (#233) Re-verifies item d2c8a852ff ("The funnel's only Google Ads conversion measurement is dead by construction: placeholder tag") against current origin/main (c62211c) and the live deployment. The fix from PR #172 (60d045c) still holds: no commit since the #227/#228 close-out touched the ads surface, npm run check passes including the Google Ads guard, npm test passes end to end (worker 80/80 incl. the three ads-tag tests), and the live /brief-requested serves no tag with the strict CSP while the env values are unconfigured. Finding stays closed — no code change. Co-authored-by: nish3451 <nish3451@users.noreply.github.com> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
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.
21c5741 to
e39e381
Compare
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
…ainst current main and live (2026-08-20, lane 1) (#260) The preferred-source declaration is in place, guarded, and live: llms.txt and offer.md carry the Answer Readiness section with all eight controlled questions mapped to exactly one served page (price questions to /pricing), mirrored identically, byte-identical to the live deployment, with all 126 tests passing. PR #227's 2026-08-15 controlled re-run (q5/q7 google found, "Missing: pricing" gone) is merged but not yet deployed — the release state pins b4d80f1 (2026-08-17) — a deploy-lag note for the release pipeline, not a regression of this finding. Co-authored-by: minimax-vps <minimax-vps@local> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
2 participants
What this does
Re-establishes the AI-search evidence fixture's verified record on main with fresh controlled captures from 2026-08-15 for every runnable engine (Google AI Overview q1-q8, Bing q1/q5/q7, DuckDuckGo q1/q2/q5), executed from the VPS browser in anonymous sessions.
The item's accept criterion is met — first Found transitions
The backlog item (id
6efb99cca9, "Re-establish verified AI-search entity and offer understanding after the 2026-08-08 15:04 live recheck") requires at least one previously Wrong/Absent run becoming Found. Two did:Honest remainder
Files
evidence-fixtures/ai-search/evidence.json— fresh 2026-08-15 runs (2 found, 9 wrong, 2 absent, 2 not-tested)public/audit.html— embedded AI-search bundle regenerated from fixturesscripts/test-agent-ui.mjs— state-structure and q5 tests assert the current verified recorddocs/evidence/ai-search/2026-08-15-controlled-rerun.md— receiptVerification
npm run checkpassesnpm testpasses (121 tests, 0 failures)git diff --checkcleanHonest limits
One-day measurement on one set of engines; no ranking, visibility, lead, or revenue outcome claimed. Bing/DuckDuckGo index lag and the not-tested engines remain open live questions.