fix(public): keep /pricing lead-form bare inputs at a 44px tap target

[nish3451]

Closes the mobile-tap-target review item.

PR #194 added a <form class="lead two"> to public/pricing.html with bare <input> elements (no <label> wrapper, relying on aria-label). The existing tap-target rules in public/shared.css apply padding to form.lead.two label, not to bare inputs, so the two /pricing form inputs rendered at 19px tall -- the same regression class PR #70 closed for the home-page footer link in 2026-08-11.

This PR:

• Adds a form.lead.two > input rule to public/shared.css (whole-file + mobile-block), mirroring the label padding with min-height:44px and box-sizing:border-box so the hit area is exactly 44px regardless of font rendering.
• Extends scripts/check-site.mjs tapTargetCss to pin both needles (whole-file + mobile-block) so the regression cannot re-ship silently. Removing the new shared.css needle from the guard causes npm run check to fail with the expected message.
• Appends a 2026-08-20 entry to docs/evidence/tap-targets-2026-08-09.md recording the re-verification.
• Adds .lane/reports/docs-tap-target-rereverify-2026-08-20.md with the full per-page measurement tables.

Verified on d0daea9 with a fresh Playwright 1.62.1 session at 390x844: every standalone interactive element on every served page is now >=44px in both height and width -- including the previously 19px /pricing form inputs, now 44px exactly. The label-wrapped forms on /index and /audit were not affected (they still use the form.lead.two label rule). Only the WCAG-exempt inline text links (.xa1, .xi19, .xp1) remain under 44px, as recorded in the 2026-08-12 receipt. Full npm test suite: 126 tests, 0 failures.

Greptile Summary

The PR raises bare pricing-form inputs to a 44px tap target and records the corresponding verification evidence.

• Adds desktop and mobile direct-child input sizing rules in shared.css.
• Extends the site checker with source needles for the new declarations.
• Documents viewport measurements and regression verification.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking weakness in how the new responsive CSS assertions verify media-block placement.

The CSS change reaches the intended pricing inputs without disrupting wrapped forms, but the added source guard can accept declarations placed outside the intended breakpoint because its media-query capture is overly broad.

Files Needing Attention: scripts/check-site.mjs

Important Files Changed

Filename	Overview
public/shared.css	Correctly scopes 44px sizing to bare direct-child inputs while preserving label-wrapped forms.
scripts/check-site.mjs	Adds the intended needles, but the existing greedy media-block extraction does not reliably enforce their responsive placement.
docs/evidence/tap-targets-2026-08-09.md	Records the tap-target regression, fix, measurements, and verification results.
.lane/reports/docs-tap-target-rereverify-2026-08-20.md	Provides detailed implementation rationale and per-page verification evidence.

Prompt To Fix All With AI

### Issue 1
scripts/check-site.mjs:586
**Mobile CSS guard scans too broadly**

The mobile-block validator searches a greedy capture extending from the first matching media query through the stylesheet’s final brace. Consequently, these new needles still pass when the declarations are moved later in `shared.css` but outside the intended breakpoint, allowing `npm run check` to miss a responsive tap-target regression.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "fix(public): keep /pricing lead-form bar..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[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: 29 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: cea79dc7-b8a5-4e8b-9977-9d431b54830c

📥 Commits

Reviewing files that changed from the base of the PR and between 0540cf9 and f961c28.

📒 Files selected for processing (4)

• .lane/reports/docs-tap-target-rereverify-2026-08-20.md
• docs/evidence/tap-targets-2026-08-09.md
• public/shared.css
• scripts/check-site.mjs

---

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/login.

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Mobile CSS guard scans too broadly

The mobile-block validator searches a greedy capture extending from the first matching media query through the stylesheet’s final brace. Consequently, these new needles still pass when the declarations are moved later in shared.css but outside the intended breakpoint, allowing npm run check to miss a responsive tap-target regression.

Prompt To Fix With AI

This is a comment left during a code review.
Path: scripts/check-site.mjs
Line: 586

Comment:
**Mobile CSS guard scans too broadly**

The mobile-block validator searches a greedy capture extending from the first matching media query through the stylesheet’s final brace. Consequently, these new needles still pass when the declarations are moved later in `shared.css` but outside the intended breakpoint, allowing `npm run check` to miss a responsive tap-target regression.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.