docs(evidence): re-verify retired /agent-desk no longer claims apex root as canonical (2026-08-21, lane 1)

[nish3451]

Item

• 67d184c9a7 — "[unreviewed-by-opus] Stop /agent-desk from claiming the apex root as its canonical — the live legacy surface still…" (truncated at dispatch).

What this lane does

Re-verifies that the retired self-serve /agent-desk surface no longer names the apex root (https://tinystudio.io/) as its <link rel="canonical"> or <meta property="og:url">, on the current origin/main head (92d55c3) and against the live deployment of that head.

No code change is included — the fix lands in PR #229 (commit 798cd71, merged 2026-08-17). This lane adds the receipt for the next re-verify cycle so a future reader can see one evidence doc per verification round.

Source state (92d55c3)

• public/agent-desk.html head carries noindex,nofollow, the retired-framing title/description, and both <link rel="canonical" href="https://tinystudio.io/agent-desk"> and <meta property="og:url" content="https://tinystudio.io/agent-desk">. No apex-root canonical/og:url survives on the legacy page.
• File unchanged since 798cd71; the ten merges between 798cd71 and 92d55c3 touched neighbour files only.
• Regression guard scripts/check-site.mjs "Retired Agent Desk index guard" (lines ~1327–1362) still fails npm run check on any drift of the noindex meta, the retired-framing description, the canonical, or the og:url.

Live state (2026-08-21)

• https://tinystudio.io/agent-desk → 200, noindex, nofollow, canonical https://tinystudio.io/agent-desk, og:url https://tinystudio.io/agent-desk.
• https://tinystudio.io/agent-desk.html → 307 → /agent-desk.
• https://tinystudio.io/ → 200, zero "Agent Desk" string in the served HTML.
• Bytes equality — md5 of public/agent-desk.html on disk (3310f720f1b9234970327ba35c52da94) equals md5 of the wire bytes from curl -sS https://tinystudio.io/agent-desk.

Verification

• node scripts/check-site.mjs → "TinyStudio.io checks passed."
• node --test over six test files → 124 / 124 pass (headings 6, sitemap 7, worker 80, UI 16, contract 8, viewport 4, +3 vs the 2026-08-17 receipt from agent-worker branches merged between 4efeb4d and 92d55c3).
• node scripts/test-narrow-viewport-pages.mjs → "All four owned routes keep document scrollWidth === clientWidth at 240-390px."
• node scripts/test-narrow-viewport.mjs → "All narrow viewports keep the hero mock and its flags inside the viewport."
• git diff --check clean.

Files

• docs/evidence/agent-desk-canonical-apex-rereverify-2026-08-21.md — full re-verification receipt (environment, source check, live check, bytes equality, reproduce, negative test, closeout, non-claims).
• .lane/reports/lane1-agent-desk-canonical-apex-rereverify-2026-08-21.md — lane report.

Relationship to other receipts

• docs/evidence/agent-desk-retired-title-rereverify-2026-08-17.md + .lane/reports/lane1-google-retired-agent-desk-snippet.md — parent finding f41c8af0f8.
• docs/evidence/agent-desk-canonical-apex-rereverify-2026-08-17.md + .lane/reports/fix-agent-desk-canonical-apex-rereverify-lane1-2026-08-17.md — previous same-item re-verify against 4efeb4d.

Non-claim

No Google SERP change is claimed. Google's recrawl and site-name refresh run on Google's timetable; SERP fetches are bot-blocked. The honest claim is the site-side one: the legacy page no longer names the apex root as its canonical or og:url on the current head or on live, the live bytes md5-match the guarded source, the regression guard catches any drift, and no served surface still consolidates the retired "TinyStudio Agent Desk" title onto the homepage URL.

[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: 31 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: 2ba94ad5-aef8-426a-92cf-6ca087cca5e2

📥 Commits

Reviewing files that changed from the base of the PR and between b37d4d6 and 0d4a2d9.

📒 Files selected for processing (2)

• .lane/reports/lane1-agent-desk-canonical-apex-rereverify-2026-08-21.md
• docs/evidence/agent-desk-canonical-apex-rereverify-2026-08-21.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.}