Skip to content
This repository was archived by the owner on Sep 28, 2026. It is now read-only.

docs(evidence): re-verify sitemap finding against current main and live #71

Closed
nish3451 wants to merge 5 commits into from
Closed

docs(evidence): re-verify sitemap finding against current main and live #71

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
75b8b15
docs(evidence): re-verify sitemap finding against current main and live
nish3451 Aug 10, 2026
d64397c
Merge branch 'main' into docs/evidence/sitemap-reverify-20260811
nish3451 Aug 10, 2026
719fefc
Merge branch 'main' into docs/evidence/sitemap-reverify-20260811
nish3451 Aug 10, 2026
2d9b4d5
Merge branch 'main' into docs/evidence/sitemap-reverify-20260811
nish3451 Aug 10, 2026
35ab3cb
Merge branch 'main' into docs/evidence/sitemap-reverify-20260811
nish3451 Aug 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions docs/evidence/sitemap-2026-08-09.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,3 +133,41 @@ deployed sitemap lists all five human-facing pages at their clean URLs plus
the two machine-readable mirrors — including the four pages that were
invisible to crawlers before the fix. The receipt now records the closeout on
the current head so the finding cannot be re-opened by tracker drift.

### Closeout re-verification (added 2026-08-11)

Re-verified against the current origin/main head (f9f0b0f, "fix: link Nish's
daily reads from the homepage footer", merged 2026-08-11) after the commits
Comment on lines +139 to +140

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Re-verify against the actual base head

The asserted baseline is already stale for this commit: 86146c1 has parent ce02df9, not f9f0b0f, and that parent includes later commits 1cc7a4e and ce02df9, including changes to public/audit.html and scripts/check-site.mjs. Consequently, the subsequent claims that checks ran “on this head” and that all intervening commits were considered document an older tree rather than the tree receiving this evidence; rerun and record the verification against the actual parent or final head and include the omitted commits.

Useful? React with 👍 / 👎.

Comment on lines +139 to +140

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Re-run the receipt against the actual parent

The re-verification still does not cover the tree on which this commit is based: fresh evidence after the rebase shows that f0b9727 has parent 6a914b6, while this paragraph calls f9f0b0f the current origin/main head and omits the intervening 1cc7a4e, ce02df9, and 6a914b6 commits. In particular, those commits modify public/audit.html and scripts/check-site.mjs, so the claims that the source checks ran “on this head” and that all subsequent page edits were considered remain unsupported; record checks against 6a914b6 or the final head and include the omitted commits.

Useful? React with 👍 / 👎.

Comment on lines +139 to +140

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Re-run verification against the actual parent

Fresh evidence in this revision is that 08e57ba now has parent 6f24bff, but the added receipt still calls f9f0b0f the current origin/main head and later says the source checks ran on “this head.” The omitted intervening commits include 1cc7a4e, which changes both public/audit.html and scripts/check-site.mjs, so the receipt does not establish that the page surface and checker on the actual base were verified; rerun against 6f24bff or the final head and record the intervening commits.

Useful? React with 👍 / 👎.

that landed since the 2026-08-09 closeout — 95d2248 (preferred source pages:
llms.txt/offer.md only), c5e2f2b (de-index the retired Agent Desk), ac05bec
(tap targets: CSS padding only), d74225e/1295f9c/536b3c9 (CI-runner commits,
no public assets), 2e04225 (render-blocking re-verify receipt), 11864a7
(Website Appraisal contract doc), f9f0b0f (footer link). None of them touched
`public/sitemap.xml`, `public/robots.txt`, or the HTML page set — the public
surface is still the same seven files (five human-facing pages, the noindex
`/brief-requested`, and the legacy `/agent-desk`), so no loc belongs in the
sitemap that is not already there. Two fresh checks:

1. Source checks on this head: `npm run test:sitemap` passes (7/7 subtests,
including the "known bad shape" fixtures that prove the checker rejects
every regression it guards) and `npm run check` passes (the "Sitemap
should expose the root Agent Desk URL" guard and every other site check).

2. Fresh live measurement of the deployed site (2026-08-11):
`https://tinystudio.io/sitemap.xml` returns 200 and is **byte-identical**
to `public/sitemap.xml` on this head (clean `diff`); every loc probed over
HTTPS returns 200 — `https://tinystudio.io/`, `/audit`, `/agents`,
`/pricing`, `/specimen` (the five human-facing pages at their clean
extensionless URLs), plus `/offer.md` and `/llms.txt`. `robots.txt` (live)
still carries `Sitemap: https://tinystudio.io/sitemap.xml`, and
`/brief-requested` still serves `<meta name="robots" content="noindex,
nofollow">` while remaining absent from the sitemap, as does legacy
`/agent-desk`.

Same result as the 2026-08-09 closeout: the sitemap covers the complete
indexable surface (five human-facing pages plus the two machine-readable
mirrors), the regression suite and site checks pass on the current head, and
the deployed bytes match the committed file. The round-5 candidate ("Publish
a complete sitemap covering the five human-facing pages") remains fully
delivered — code side (PR #36), CI (`test:sitemap`), and live — and this lane
(2026-08-11) re-confirmed all three and found nothing further to change.
Loading