fix(public): add in-content conversion CTA to the /specimen proof page - #107
fix(public): add in-content conversion CTA to the /specimen proof page#107nish3451 wants to merge 4 commits into
Conversation
The homepage routes its 'Read the specimen' call-out to /specimen, but the page ended at the Confidentiality section with only the nav CTA to convert. A reader who finishes the sample report had no in-content next step. Add a dark .band (house pattern from /pricing and /agents) after the report with an explicit .cta link to /#start, a no-guarantees note, and a >=44px tap target. Include .band in the specimen reveal-on-scroll selector, update the locked heading outline (new h2), and guard the CTA shape in check-site.mjs so it cannot silently regress.
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 (5)
📝 WalkthroughWalkthroughThe specimen page adds an appraisal CTA band after the confidentiality section. It includes styling, reveal animation support, exact-link validation, tap-target checks, disclaimer checks, and an updated heading hierarchy expectation. ChangesSpecimen CTA
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
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.
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.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
…(PR #22 conflict-locked, superseded by #28) against current GitHub state (2026-08-12) (#152) Closes the review item "Two open PRs carry the same heading-hierarchy fix — PR #22 is conflict-locked and superseded" (review queue, unreviewed-by-grok), re-verified against the current GitHub state on 2026-08-12. Verified facts (2026-08-12): - PR #22 is CLOSED (2026-08-09), never merged, mergeStateStatus: DIRTY (conflict-locked) at close — the item's description was accurate. - The superseding fix PR #28 is MERGED on main (2026-08-09, commit 7be3d8f); sibling duplicate #27 is also CLOSED. - All 53 currently open PRs diff-reviewed: the only literal heading markup anywhere is one hierarchy-preserving h2 on /specimen in PR #107 (with its locked outline updated in scripts/test-heading-hierarchy.mjs) and one standalone h1 in PR #116's new closed-intake page — zero open PR retags an existing heading level, so no open PR duplicates the heading fix. - Main has carried exactly one heading fix since 2026-08-09: the only heading-tag change since the merge is 2ae7504's two hierarchy-preserving homepage FAQ h3s (PR #102, locked outline updated). npm run check passes and npm test passes in full (test:headings 6/6) on current origin/main (ad9cee3). - Site-side verification is current via docs/evidence/heading-hierarchy-2026-08-09.md (PR #74) with the 2026-08-12 re-verify in flight as PR #120. Docs-only change; no code, no deployment.
#155) The homepage routes its 'Read the specimen' call-out to /specimen, but the page ended at the Confidentiality section with only the nav CTA to convert. A reader who finishes the sample report had no in-content next step. Add a dark .band (house pattern from shared.css, as used on /pricing and /agents) after the report with an explicit .cta link to /#start, a no-guarantees note, and a >=44px tap target. Include .band in the specimen reveal-on-scroll selector, update the locked heading outline (new h2), and guard the CTA shape in check-site.mjs so it cannot silently regress. Supersedes the conflict-locked PR #107 (fix/specimen-conversion-cta), which carried the same change set but has been DIRTY against main since 2026-08-11.
|
Closing: superseded by #155 (specimen CTA landed on main). |
…nt main and live (2026-08-14) (#195) The review item "[unreviewed-by-opus] The /specimen proof page contains no in-content conversion CTA" is already fixed: PR #155 (b81281f) landed the .band conversion CTA on /specimen on 2026-08-14, superseding the conflict-locked PR #107. This receipt re-verifies the fix against current origin/main (2088b6b) and the live deployment (release 5c6521a): the band CTA to /#start is on source, guarded by check-site.mjs, served live, and covered by the passing test suite. No code change was needed. Co-authored-by: nish3451 <nish3451@users.noreply.github.com> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
… on current state (#203) #107 closed 2026-08-14 (stale duplicate, conflict-locked since 2026-08-11); #155 merged 2026-08-13 as b81281f and is on current main and live. The specimen.html band hunks are byte-identical as the item states, and no open PR carries the fix — the cluster is fully resolved. Co-authored-by: nish3451 <nish3451@users.noreply.github.com> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
What
The homepage routes its "Read the specimen" call-out to
/specimen, but the proof page ended at the Confidentiality section with only the nav CTA to convert. A reader who finishes the sample report had no in-content next step.Closes the backlog item:
[unreviewed-by-grok] The /specimen proof page contains no in-content conversion CTA — the page the homepage routes.Change
public/specimen.html: dark.bandafter the report (house pattern from/pricingand/agents) with an explicit.ctalink to/#start("Request the appraisal"), a copy line, and the standard no-guarantees note.public/specimen.css: styles the band CTA as a pill with a >=44px hit area (the site's own tap-target standard).public/specimen.js: include.bandin the reveal-on-scroll selector (matches pricing/agents).scripts/check-site.mjs: static source guard so the band, CTA link, note and 44px tap target cannot silently regress (repo convention: every fix carries a guard). Guard proven to fire on a mutated copy.scripts/test-heading-hierarchy.mjs: locked specimen outline updated[1,2,2,2,2,3,2]->[1,2,2,2,2,3,2,2]for the new h2.Verification
npm run check: passednpm test(all suites: headings, sitemap, contract, worker, ui): all passgit diff --check: clean{height: 46, width: 194}, mobile{height: 46, width: 194}.Summary by CodeRabbit
New Features
Tests