Repository navigation
Homepage: hero receipt copy, example output, single install block, remove curl text - #852
PetrefiedThunder wants to merge 2 commits into
Conversation
…url text, tab border contrast, demo key click event
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: eb81a9090f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <div class="hero-v2-intro"> | ||
| <h1>Let agents retry safely.</h1> | ||
| <p>One accepted request key permits at most one gateway dispatch to the configured upstream tool and at most one debit. Each finalized or reconciled path has a receipt.</p> | ||
| <p>Each action runs once and leaves a receipt.</p> |
There was a problem hiding this comment.
For denied, expired, or over-budget requests, the tool runs zero times, while a delivery_uncertain request may have completed but cannot be proven either way. This unconditional headline therefore contradicts the limits stated later on the page and overstates the actual guarantee; describe the at-most-one configured-upstream dispatch and debit instead.
AGENTS.md reference: AGENTS.md:L62-L71
Useful? React with 👍 / 👎.
| <pre tabindex="0"><code>receipt_id: rcpt_7Kq2mX9 | ||
| Same receipt. The tool did not run again.</code></pre> |
There was a problem hiding this comment.
When an upstream tool performs internal retries or the original dispatch has an ambiguous outcome, replaying the same receipt establishes that the gateway did not dispatch again, not that the tool itself did not run again. The page's own receipt definition also says it does not prove the downstream effect, so this output should retain the gateway-scoped wording rather than presenting an unverifiable tool-side conclusion.
AGENTS.md reference: AGENTS.md:L62-L71
Useful? React with 👍 / 👎.
| // configured at build time; email_click is the primary intake path. | ||
| const allowedEvents = new Set([ | ||
| "booking_click", | ||
| "demo_key_click", |
There was a problem hiding this comment.
The deployment caches analytics.js for seven days, but the homepage still loads it with the existing ?v=home-light-1 token. Returning visitors with the prior script cached will therefore keep the old allowlist and silently reject demo_key_click until expiry; bump the homepage analytics URL when adding this allowlist entry.
Useful? React with 👍 / 👎.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit eb81a90. Configure here.
| max-width: 850px; | ||
| margin-top: 18px; | ||
| overflow: hidden; | ||
| border: 1px solid var(--home-line); |
There was a problem hiding this comment.
Checklist link breaks grid layout
Medium Severity
The How it works checklist lays out each li as a two-column grid with a ::before checkmark, but the last step also has a direct child a. That link becomes its own grid item and drops onto the next row in the 24px marker column, so the proof-page CTA no longer sits in the step text.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit eb81a90. Configure here.
Hero subline restored with boundary line in muted type; example receipt output under hero code block; install block shown once (steps now a checklist); curl text removed, coming soon tab kept with #6b7280 border; demo_key_click event via existing Vercel analytics (verified receipt event not possible on site: verification happens outside the page). Tests: 6 node suites, 78 interface pytest, build OK.
Note
Low Risk
Marketing-site HTML/CSS/JS and analytics allowlist only; no auth, API, or payment paths touched.
Overview
Homepage hero and funnel are tightened: a short lead line (“Each action runs once…”) with the detailed boundary copy moved to muted
hero-v2-boundarytext; the hero code block drops live curl in favor of static example receipt output, while Python quickstart stays the single install path.“How it works” is a five-item checklist that points back to the hero commands instead of a second embedded code panel;
home-key.jsonly fills/copies the hero Python block (duplicate quickstart and curl copy handlers removed). Cache bust bumpshome-key.jstohome-light-3.Analytics:
demo_key_clickis allowlisted inanalytics.jsand wired on Get a demo key viadata-analytics-event. Newtest_analytics.mjsplus updated home-key, contrast, and site interface tests lock the markup and behavior.Reviewed by Cursor Bugbot for commit 15c183d. Bugbot is set up for automated code reviews on this repo. Configure here.