docs(evidence): re-verify the /specimen in-content conversion CTA on current main and live (2026-08-20, lane 1)

[nish3451]

Closes review item 94ec723c9e — "[unreviewed-by-opus] The /specimen proof
page contains no in-content conversion CTA — the page the homepage routes".

Finding

The item is already resolved on current origin/main (92d55c3) and
live: PR #155 (b81281f, merged 2026-08-13) added the in-content .band
conversion CTA to /specimen — <a class="cta" href="/#start">Request the appraisal</a> between the report and the footer, with a >=44px tap target
(padding:16px 24px) and a regression guard in scripts/check-site.mjs
(the "Specimen in-content conversion CTA" block, lines 2020-2047).

This lane's work is the re-verification closeout on the current head, so the
item cannot be re-opened by tracker drift.

Verified

• public/specimen.html lines 134-139: .band block with /#start CTA and
  no-guarantees note, before the footer.
• public/index.html line 250: homepage "Read the specimen" routes to
  /specimen.
• git merge-base --is-ancestor b81281f origin/main → true.
• npm run check passes (exit 0).
• Live 2026-08-20: https://tinystudio.io/specimen → 200, serves
  class="band" and class="cta" href="/#start"; "Request the appraisal"
  appears twice (nav + band).

Changes

• docs/evidence/specimen-in-content-cta-rereverify-2026-08-20-lane1.md
  (re-verification receipt)
• .lane/reports/docs-specimen-in-content-cta-rereverify-2026-08-20-lane1.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: 47 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: ea207550-7d11-4a78-92d9-a2bee8e3e396

📥 Commits

Reviewing files that changed from the base of the PR and between 7b6dd93 and 4e6f2e4.

📒 Files selected for processing (2)

• .lane/reports/docs-specimen-in-content-cta-rereverify-2026-08-20-lane1.md
• docs/evidence/specimen-in-content-cta-rereverify-2026-08-20-lane1.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.}