Skip to content

docs(evidence): re-verify q5 ground truth drop of retired Agent Desk (2026-08-14) - #186

Merged
nish3451 merged 2 commits into
mainfrom
docs/q5-ground-truth-reverify-2026-08-14
Aug 14, 2026
Merged

docs(evidence): re-verify q5 ground truth drop of retired Agent Desk (2026-08-14)#186
nish3451 merged 2 commits into
mainfrom
docs/q5-ground-truth-reverify-2026-08-14

Conversation

@nish3451

Copy link
Copy Markdown
Collaborator

What

Re-verification closeout for backlog item a792ca1847 — "[unreviewed-by-opus] Replace the retired "Agent Desk" ground truth in the AI-search controlled questions (q5)".

The replacement already landed on origin/main in ed62202 ("fix(evidence): align AI-search q5 ground truth with the current offer, not the retired Agent Desk", 2026-08-11), merged via PR #43. This PR records the re-verification of that fix against the current head (e9fc96a) and the live deployment, so the item cannot be re-opened by tracker drift.

Evidence

  • docs/evidence/ai-search/2026-08-14-q5-ground-truth-reverify.md — the closeout receipt.
  • .lane/reports/docs-q5-ground-truth-reverify-2026-08-14.md — lane report.

Verified:

  1. Fixture q5 truth reads the current offer ("...the free leak audit of high-ticket service homepages, and the human-reviewed desk that closes what the audit finds."); no "Agent Desk" in any question truth.
  2. public/audit.html embedded bundle is byte-identical to the two fixture files (drift guard, scripts/check-site.mjs lines 751-807).
  3. npm run check → exit 0; npm test → 117 tests, 0 failures; git diff --check clean.
  4. Live /audit, /llms.txt, /offer.md bytes are identical to public/ sources (md5 match); Cloudflare release-state pins deployed SHA at e9fc96a = current head.
  5. Homepage #identity q5 row and the llms.txt/offer.md answer-readiness mapping carry the matching wording.

No captured run was relabelled (9 wrong / 2 not-tested / 0 found from 2026-08-09 stand); no engine was run; nothing here claims an engine's future answer.

…on current main and live (2026-08-14)

The retired Agent Desk ground truth in the AI-search controlled
questions (q5) was already replaced on origin/main (ed62202, merged
via PR #43). This receipt re-verifies the replacement against the
current head (e9fc96a) and the live deployment: the fixture truth,
the audit-page embedded bundle (byte-identical to the fixtures), the
homepage identity row, the llms.txt/offer.md mirror, npm run check
and the 117-test suite all pass, and the served /audit, /llms.txt
and /offer.md bytes match source. No captured run was relabelled.

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.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@coderabbitai

coderabbitai Bot commented Aug 14, 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: 21 minutes

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?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 5e1a6bd5-f020-4cdb-93f0-acfbbf3f577d

📥 Commits

Reviewing files that changed from the base of the PR and between ed50dae and 0a837b9.

📒 Files selected for processing (2)
  • .lane/reports/docs-q5-ground-truth-reverify-2026-08-14.md
  • docs/evidence/ai-search/2026-08-14-q5-ground-truth-reverify.md

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/login.

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

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@nish3451
nish3451 merged commit 60958fc into main Aug 14, 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