docs(evidence): re-verify AI answer readiness finding 4473a99a9bc9 against current main and live - #81
Conversation
…ainst current main and live The 2026-08-09 closeout declared the preferred source pages in llms.txt and offer.md but only against the source tree. Re-verified against the current origin/main head (8b42e0a) and the deployed site: the four files that carry the declaration are byte-identical to the closeout commit 95d2248, the check-site.mjs guard is unchanged (only a comment refresh in 1cc7a4e), and a fresh live measurement of https://tinystudio.io/llms.txt and /offer.md finds the section present on both, all seven controlled questions mapped to exactly one served page, both price questions on pricing.html, the mirror identical, and the served bytes byte-identical to source. No live engine run is claimed.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe evidence document adds a 2026-08-11 re-verification of Answer Readiness against current source and the deployed site. It records repository checks, served-page measurements, mappings, sitemap membership, byte identity, and the limitation on live engine-answer claims. ChangesAnswer Readiness verification
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3056a9a192
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| The live section carries all seven controlled questions, each mapped to | ||
| exactly one served page: q1 → `https://tinystudio.io/` (homepage), q2 → | ||
| `https://tinystudio.io/pricing.html`, q3 → `https://tinystudio.io/audit.html`, | ||
| q4 → `https://tinystudio.io/audit.html`, q5 → | ||
| `https://tinystudio.io/` (homepage), q6 → `https://tinystudio.io/audit.html`, | ||
| q7 → `https://tinystudio.io/pricing.html`. Both price questions point at | ||
| `pricing.html`, which owns the price; every mapped page is a served page | ||
| per the live sitemap; and `offer.md` mirrors the identical |
There was a problem hiding this comment.
The claimed live membership is incorrect for five of the seven mappings: public/sitemap.xml contains the clean /audit and /pricing URLs, while the repository's verified live receipt in docs/evidence/internal-links-2026-08-09.md records that every .html form returns 307 to its clean twin. The source guard only passes because it manufactures .html aliases from sitemap entries rather than probing them. Closing the answer-readiness finding on this basis preserves redirecting preferred-source URLs; update the declarations and guard to use the final clean URLs before claiming every mapping is a served sitemap page.
Useful? React with 👍 / 👎.
| cited sources and a strict state — and the tracker cannot re-open the | ||
| declaration itself, because it is now guarded on both sides of the deploy | ||
| boundary. |
There was a problem hiding this comment.
A one-time live byte comparison is a measurement, not a guard on the deployment side. The inspected CI workflow only runs repository tests, a render-blocking browser check, and wrangler deploy --dry-run; nothing continuously compares live /llms.txt and /offer.md with the checked-out source or blocks/reopens on drift. A stale or separately deployed Worker can therefore diverge after this receipt, so stating that the tracker cannot reopen the finding because both sides are guarded overstates the protection.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a04c088e16
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Re-verified against the current origin/main head (8b42e0a, | ||
| "docs(evidence): close out apple touch icon finding 98a7bf8e08fc against | ||
| current main and live (#77)") after thirteen further commits touched main | ||
| since the 2026-08-09 closeout. Four of them touched the public surface or |
There was a problem hiding this comment.
The reviewed commit's first parent is 16efd20, so 8b42e0a is no longer the current-main head against which this receipt lands, and there are fourteen—not thirteen—commits after 95d2248. Even though the omitted commit only changes another evidence document, this makes the re-verification's provenance and stated comparison range inaccurate; update the base hash/count and account for 16efd20 before describing the receipt as verified against current main.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7e79f5511f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Readiness: Preferred Source Pages` section, maps every controlled | ||
| question in the fixture to exactly one served page (sitemap membership, | ||
| either spelling), forces the price questions (q2, q7) to `pricing.html`, | ||
| and fails if `offer.md` mirrors a different page — and the full `npm |
There was a problem hiding this comment.
The inspected checks do not establish this claim: both scripts/check-site.mjs and the named UI subtest only require the matching offer.md line to includes(preferred). If that line retains the preferred URL but adds a second conflicting URL, both checks still pass even though the files no longer carry identical question-to-page mappings. Either compare the parsed URL sets exactly or avoid presenting mirror drift as CI-guarded.
Useful? React with 👍 / 👎.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
1 participant
What this closes
Dogfood finding 4473a99a9bc9 ("AI Answer Readiness: preferred source pages are unclear", audit run 20260808T074205Z-msk2fl3n). The declaration fix landed in PR #42 and was closed out against the source tree on 2026-08-09; this pass re-verifies it against current main and the live deployment, following the same evidence pattern as the other re-verification PRs (#69, #71, #73-#75, #78, #80).
What changed
docs/evidence/ai-answer-readiness-2026-08-09.mdgains a "Closeout re-verification (added 2026-08-11)" section. Nothing else changed: the guarded files are byte-identical to the closeout commit.Verification
npm run checkpasses (Answer Readiness guard: section in both files, every controlled question mapped to exactly one served page, price questions onpricing.html, mirror identical);npm testpasses (90 tests: headings, sitemap, worker 53/53, UI 16/16, contract 8/8);git diff --checkclean.public/llms.txt,public/offer.md,scripts/test-agent-ui.mjs,evidence-fixtures/ai-search/are byte-identical to 95d2248; the onlycheck-site.mjsedit near the guard is a comment refresh in 1cc7a4e.https://tinystudio.io/llms.txt(200, text/plain, CSP) and/offer.md(200, text/markdown, CSP) both carry the section; all seven controlled questions map to exactly one served page; q2/q7 point atpricing.html; the mirror is identical; served bytes are byte-identical to source.No live engine run is claimed — the limitation section records that a controlled re-run remains the honest measure of engine behavior.
Summary by CodeRabbit