-
Notifications
You must be signed in to change notification settings - Fork 0
docs(evidence): re-verify meta-description finding 18dd05c10709 against current main and live #73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
27f7144
bff2631
b418c5b
eaf5f91
abd56fc
9db16c8
0d19be7
6b69a43
65624d6
59214a6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -134,3 +134,32 @@ all four sibling public pages. Finding 18dd05c10709 ("Missing meta description | |
| on home") remains closed on the code side (PR #21), in CI (`npm run check`), | ||
| and against the deployed site; this lane (2026-08-09) re-confirmed all three | ||
| and found nothing further to change. | ||
|
|
||
| ### Closeout re-verification (added 2026-08-11) | ||
|
|
||
| Re-verified against the current origin/main head (1cc7a4e, "fix(public): point | ||
| appraisal-page canonicals and JSON-LD @ids at the clean /audit URL (#56)") after | ||
| five further commits touched the home page (tap-target sizing, Agent Desk | ||
| de-indexing, AI-answer source declarations, footer link, canonical/JSON-LD | ||
| cleanup) — none of which was allowed to regress the guarantee. Three checks: | ||
|
Comment on lines
+142
to
+144
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The history does not show five commits touching the homepage: between the previous verification and Useful? React with 👍 / 👎. |
||
|
|
||
| 1. `npm run check` on the current working tree: PASS — the "Meta descriptions | ||
| (dogfood)" guard in `scripts/check-site.mjs` confirms each of the five pages | ||
| carries exactly one non-empty description tag in its head, within a | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
If a description tag is moved below Useful? React with 👍 / 👎. |
||
| search-snippet length (≤ 160 chars), distinct per page, and free of the | ||
| forbidden promises. | ||
|
|
||
| 2. Served-bytes check: `src/worker.js` serves `public/index.html` verbatim at | ||
| `/` and `/index.html` through the ASSETS binding (no transformation can | ||
| strip the tag), and `public/index.html` carries exactly one | ||
|
Comment on lines
+152
to
+154
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The deployed routing does not serve the page bytes directly at both paths: the live routing probe recorded in Useful? React with 👍 / 👎. |
||
| `meta name="description"` tag in its head (150 chars). | ||
|
|
||
| 3. Live fetch of `https://tinystudio.io/` (2026-08-11): the deployed home page | ||
| serves exactly one valid, non-empty description: | ||
|
|
||
| > TinyStudio: the free leak audit of high-ticket service homepages. Each fault named in order of what it costs you, with the fix beside it. Six a month. | ||
|
|
||
| Finding 18dd05c10709 ("Missing meta description on home") remains closed on the | ||
| code side (PR #21), in CI (`npm run check`), and against the deployed site; | ||
| this lane (2026-08-11) re-confirmed all three against current main and found | ||
| nothing further to change. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The receipt identifies
1cc7a4eas the currentorigin/mainhead, but this commit is based on6a914b6, which already includesce02df9and6a914b6after that hash. Consequently, the recorded revision does not identify the working tree on which the statednpm run checkresult was obtained, making this evidence entry irreproducible as written; record6a914b6(or explicitly distinguish the tested tree from the older source baseline).Useful? React with 👍 / 👎.