docs(evidence): re-verify AI Answer Readiness finding 4473a99a9bc9 on current main and live (2026-08-20)

[nish3451]

What

Re-verification of dogfood finding 4473a99a9bc9 ("AI Answer Readiness: preferred source pages are unclear") against current origin/main (0540cf9) and the live deployment, per the finding's established closeout pattern (source check + live measurement, no code change when the declaration already holds).

Verdict

Finding stays closed. The preferred-source declaration is in place, guarded, and live:

• public/llms.txt + public/offer.md carry the ## Answer Readiness: Preferred Source Pages section with all eight controlled questions mapped to exactly one served page; price questions (q2, q7) map to /pricing.
• The served live bytes are byte-identical to source; offer.md mirrors llms.txt.
• npm run check passes; full npm test suite: 126 tests, 0 failures, including the "every controlled question maps to a preferred source page" subtest.
• No commit since the 2026-08-15 re-verification (50c6b39) touched the declaration files or the Answer Readiness guard block.

Deploy-lag note (not a regression of this finding)

PR #227's 2026-08-15 controlled re-run (q5/google and q7/google found, "Missing: pricing" gone) is merged on main but not yet deployed: release-state-tinystudio-io.json pins b4d80f1 (2026-08-17), and live /audit still embeds the 2026-08-12 evidence record. The Answer Readiness declaration itself is live and correct. Next fleet-release tick ships current main and live /audit matches source.

Files

• docs/evidence/ai-answer-readiness-2026-08-09.md — appended 2026-08-20 re-verification receipt.
• .lane/reports/lane1-ai-answer-readiness-reverify-2026-08-20.md — lane report.

[chatgpt-codex-connector]

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 50 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: 394601cd-6fc0-4a75-9d52-306a7ef47196

📥 Commits

Reviewing files that changed from the base of the PR and between b4d70fb and d932acc.

📒 Files selected for processing (2)

• .lane/reports/lane1-ai-answer-readiness-reverify-2026-08-20.md
• docs/evidence/ai-answer-readiness-2026-08-09.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/settings/billing.

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