Skip to content

evidence(ai-search): controlled entity-and-offer re-run with four Found runs (2026-08-20) - #261

Merged
nish3451 merged 16 commits into
mainfrom
docs/ai-search-entity-offer-rereverify-2026-08-20
Aug 21, 2026
Merged

evidence(ai-search): controlled entity-and-offer re-run with four Found runs (2026-08-20)#261
nish3451 merged 16 commits into
mainfrom
docs/ai-search-entity-offer-rereverify-2026-08-20

Conversation

@nish3451

Copy link
Copy Markdown
Collaborator

Closes the item "Re-establish verified AI-search entity and offer understanding after the 2026-08-08 15:04 live recheck" (6efb99cca9) for this cycle.

What this is

A controlled re-run of the AI-search entity-and-offer registry on 2026-08-20 (Google AI Overview q1–q8, Bing q1/q5/q7, DuckDuckGo q1/q2/q5; anonymous VPS Camoufox sessions), replacing the 2026-08-15 captures in evidence-fixtures/ai-search/evidence.json and the embedded /audit bundle.

Result

Four found runs — the item's accept criterion (a previously Wrong/Absent run becomes Found) is met again, with two new transitions:

  • q5/google — found (holds from 08-15): free leak audits + human-reviewed Growth Desk ($2,500/mo), citing tinystudio.io + /pricing
  • q6/google — new wrong → found: "does not publish client work… no logos, no case studies, no testimonials", citing tinystudio.io
  • q7/google — found (holds from 08-15): free audit, $2,500/mo desk, 3-month minimum, citing tinystudio.io + /pricing
  • q8/google — new wrong → found: "No, TinyStudio explicitly states it is not a conversion audit service", citing tinystudio.io (08-15's run opened with "Yes" and was recorded wrong)

Remainder honestly recorded: 6 wrong, 4 absent (Google q2/q3 refused to generate an AI Overview on both load and same-session retry; Bing q5/q7 no AI answer — tinystudio.io organic listing still carries the retired "TinyStudio Agent Desk" title, the same index lag as 08-09/08-12/08-15), 2 not-tested unchanged (ChatGPT, Perplexity).

Files

  • evidence-fixtures/ai-search/evidence.json — fresh 2026-08-20 captures
  • public/audit.html — embedded bundle regenerated (drift guard passes)
  • scripts/test-agent-ui.mjs — q5 wording assertion updated to the current capture
  • docs/evidence/ai-search/2026-08-20-controlled-rerun.md — evidence receipt (new)
  • .lane/reports/docs-ai-search-entity-offer-rereverify-2026-08-20.md — lane report (new)

Verification

npm run check passes · npm test 126/0 · git diff --check clean

Honest boundary

One-day measurement, not a ranking/visibility promise. Bing/DuckDuckGo still answer from other businesses (index lag); ChatGPT/Perplexity remain untested; Google q2/q3 served no AI Overview on this date.

…nd runs (2026-08-20)

Re-run of the controlled AI-search registry on 2026-08-20 replaces the
2026-08-15 captures for every runnable pair. Google now serves four
`found` runs — q5 and q7 hold from 08-15, and q6 (no client work) and
q8 (not a conversion audit service) are new wrong-to-found transitions.
Google q2/q3 returned "Can't generate an AI overview right now" on both
loads and a same-session retry each, recorded `absent`. Bing and
DuckDuckGo still answer from other businesses; their tinystudio.io
organic listings still carry the retired Agent Desk title (index lag).
ChatGPT and Perplexity remain `not-tested` with unchanged reasons.
The embedded audit bundle is regenerated; the q5 wording assertion in
test-agent-ui.mjs follows the current capture. Full suite: 126 tests,
0 failures; checks and git diff --check pass.

Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 20 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.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 06cefab0-bdb8-4391-a322-04a226a411a0

📥 Commits

Reviewing files that changed from the base of the PR and between b2db9d0 and 35b7212.

📒 Files selected for processing (5)
  • .lane/reports/docs-ai-search-entity-offer-rereverify-2026-08-20.md
  • docs/evidence/ai-search/2026-08-20-controlled-rerun.md
  • evidence-fixtures/ai-search/evidence.json
  • public/audit.html
  • scripts/test-agent-ui.mjs

Note

🎁 Summarized by CodeRabbit Free

Your 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/settings/billing.

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

@nish3451
nish3451 merged commit 6c5d1c3 into main Aug 21, 2026
3 checks passed
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