docs(evidence): re-verify the 2026-08-12 AI-search re-run (PR #128) is landed and live (2026-08-21, lane 1) - #286
Conversation
…s landed and live (2026-08-21, lane 1) PR #128's fresh 2026-08-12 AI-search captures (DuckDuckGo q1/q2/q5, Bing q1/q5/q7 — all Wrong or Absent) are no longer stranded: they landed on main via PR #211 (merge a654ab4) and are the record the live /audit evidence panel renders today. Re-verified against current main and the live site; receipt only, no fixture or code change. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 8 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?Wait for the limit to reset, then comment 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (2)
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 |
What this does
Re-verifies the backlog item "The 2026-08-12 AI-search controlled re-run is
stranded in CONFLICTING unowned PR #128". Receipt only — no fixture, code,
or live-site change.
Findings (2026-08-21)
a654ab4,2026-08-15): the six fresh runs (DuckDuckGo q1/q2/q5, Bing q1/q5/q7 —
4
wrong, 2absent) are byte-identical to PR evidence(ai-search): controlled entity-and-offer re-run on 2026-08-12 (Bing, DuckDuckGo) #128's head fixture.testedOn 2026-08-12, 15 runs: 10 wrong, 3 absent, 2 not-tested) — the strandedre-run is what's live today.
Foundtransition was fabricated; the triage closeout (2026-08-18)recorded the same disposition.
Files
docs/evidence/ai-search/2026-08-21-pr128-reverify.md— re-verify receipt.lane/reports/verify-ai-search-rerun-pr128-2026-08-21.md— lane reportHonest limits
No new engine capture was run. Main's fixture has since advanced via PR #227
(2026-08-15 re-run, two
foundtransitions) but the live panel still servesthe 2026-08-12 record — a deploy lag observed, not altered, here. No
ranking/visibility/lead/revenue outcome is claimed.