feat(public): route founders to reviewed Website Correction by nish3451 · Pull Request #10 · Nishfleet/tinystudio-in

nish3451 · 2026-08-06T08:07:58Z

intended-outcome: Make the managed-service lane visible without confusing it with the product portfolio, and give suitable founders a clear human-reviewed application route.

verify: npm test passes on the clean primary checkout baseline; candidate npm test reaches the existing stateful operator-surface failure at scripts/test-active-operator-surfaces.mjs:143, while the candidate-only public diff is excluded from that check; sgscan reports no new security findings; local browser checks confirm the homepage/contact copy and Website Correction mailto route with zero horizontal overflow at the available viewport.

Scope: public homepage and contact page only. No pricing, legal copy, auth, payments, leads, deploys, migrations, dependencies, or secrets.

Co-Authored-By: Claude noreply@anthropic.com

Summary by CodeRabbit

New Features
- Added information about the Website Correction managed service.
- Introduced eligibility details, human-review expectations, scope guidance, and application links.
- Added Website Correction messaging to the homepage and contact page.
- Expanded contact guidance for submitting Website Correction requests.

intended-outcome: Make the managed-service lane visible without confusing it with the product portfolio, and give suitable founders a clear human-reviewed application route. verify: npm test; local browser checks for homepage/contact copy, mailto route, and zero horizontal overflow at the available viewport; sgscan Co-Authored-By: Claude <noreply@anthropic.com>

greptile-apps

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

coderabbitai · 2026-08-06T08:08:19Z

📝 Walkthrough

Walkthrough

The public homepage and contact page now present The Website Correction as a human-reviewed managed service. They describe eligibility, scope, review, application, and required applicant information.

Changes

Website Correction service

Layer / File(s)	Summary
Homepage service presentation `public/index.html`	The homepage introduces The Website Correction, adds a managed-service navigation item, and provides application details and contact links.
Contact-page intake guidance `public/contact/index.html`	The contact page updates metadata and service copy, adds the Website Correction section, and requests the applicant’s site URL and most important page.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

nish3451/TinyStudio.io#8: Both changes update homepage content in public/index.html.
nish3451/TinyStudio.io#11: Both changes update homepage copy and messaging.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: routing founders to the human-reviewed Website Correction managed service.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch nightly/public-conversion-path

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

coderabbitai

🧹 Nitpick comments (1)

public/index.html (1)
280-291: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use h3 for the first heading inside the managed-service section.

Line 280 defines the section title as h2, but Line 291 uses h4 without an intervening h3. This skips a heading level for assistive-technology navigation. Change the card title to h3, and update the scoped style selector if h4 controls its appearance.
Proposed semantic heading fix
-            <h4>Fit and scope are reviewed by a human first.</h4>
+            <h3>Fit and scope are reviewed by a human first.</h3>
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@public/index.html` around lines 280 - 291, In the managed-service section,
change the “Fit and scope are reviewed by a human first.” heading from h4 to h3
so it follows the existing h2 hierarchy, and update any scoped CSS selector
targeting that heading if needed to preserve its current appearance.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@public/index.html`:
- Around line 280-291: In the managed-service section, change the “Fit and scope
are reviewed by a human first.” heading from h4 to h3 so it follows the existing
h2 hierarchy, and update any scoped CSS selector targeting that heading if
needed to preserve its current appearance.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8c57d43a-51ca-4eb1-ac98-89b33a8e47c7

📥 Commits

Reviewing files that changed from the base of the PR and between 24e516a and 606e889.

📒 Files selected for processing (2)

public/contact/index.html
public/index.html

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 606e8897de

ℹ️ 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".

chatgpt-codex-connector · 2026-08-06T08:11:28Z

+          <div class="section-head">
+            <div>
+              <p class="eyebrow">Managed service</p>
+              <h2 id="managed-service-title">The Website Correction.</h2>


Use the canonical offer name on the application route

When a founder follows this CTA, they apply for “The Website Correction,” but the internal sales and delivery workflow recognizes only the “7-Day Website Revenue Leak Fix Sprint” (scripts/lib/client-scaffold.mjs:7 and PRODUCT.md:3) and emits that different name in subsequent materials. This makes the handoff appear to replace the service the founder requested and conflicts with the current plan's one-offer invariant; use the canonical name publicly or explicitly identify Website Correction as its public alias.

AGENTS.md reference: AGENTS.md:L2-L3

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-08-06T08:11:29Z

+              where the work becomes more operational. There is also one
+              managed service for founders, reviewed by a human: The Website
+              Correction.


Update the homepage's machine-facing descriptions

When the homepage is shared through an Open Graph/Twitter consumer or read from its structured data, the new service remains invisible because the title, meta descriptions, image alt text, and JSON-LD at lines 6–69 still describe Tiny Studio exclusively as Promptly, Drishti, and 0509. The contact page's corresponding metadata was updated in this commit, so leaving the primary entry page stale prevents this new route from appearing in social previews and other machine-facing representations.

Useful? React with 👍 / 👎.

greptile-apps

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

…tract - Keep both contact-page sections: the offer description (PR #10) now points its apply button at the canonical application section (PR #11) so there is one application route with one operator-visible subject. - Tag the two homepage Website Correction CTAs from PR #10 with their registered data-measure-source names (homepage-hero, homepage-service) and route them through /contact/?source=<name>, as the measurement contract requires for any live CTA. - Align the homepage managed-service prose with the application route.

… leave the June-20 bundle (#81) * fix(public): add the tinystudio.in release lane (Cloudflare Pages deploy path repair) The live site has served the 2026-06-20 bundle (07acd07) since June 20 while 17+ public PRs merged to main; the Cloudflare Pages git connection for tiny-studio-3f5 never shows checks/statuses on commits and no deploy workflow or secrets exist in the repo. The fleet Workers token lacks Cloudflare Pages:Edit, so no automation on this box can publish today. Add an in-repo release lane that works the moment a Pages-scoped token is provisioned (documented fail-closed message): - scripts/prepare-public-deploy-bundle.mjs: filtered bundle (public/ minus the snoozed-by-Nish managed-service buyer path from PRs #10/#11; every other merged fix preserved), fail-closed in both directions - scripts/test-public-deploy-bundle.mjs: regression guard, wired into npm test/ci (62 checks) - scripts/publish-public-site.mjs: prepare -> wrangler pages deploy to tiny-studio-3f5 -> live verification - scripts/check-public-live-deploy.mjs: live proof for the deploy-path accept (H2-after-H1 /promptly/support/ #18/#20, JSON-LD /contact/ #19, real 404s #34, homepage portfolio-only #29 + no buyer path) - .github/workflows/deploy-public-site.yml: vps-verify lane on push to main - wrangler 4.120.0 devDependency verify: npm test (603 checks, 0 failures); node scripts/prepare-public-deploy-bundle.mjs; git diff --check * fix(public): attach the source commit to Cloudflare Pages deployments wrangler pages deploy accepts --commit-hash/--commit-message/--commit-dirty for dashboard provenance. The bundle already records source_commit in deploy-manifest.json; pass it through so the Pages dashboard links the deployment to the exact tinystudio-in commit that produced the bundle. verify: node --check scripts/publish-public-site.mjs; node scripts/test-public-deploy-bundle.mjs (62 checks, 0 failures) Co-authored-by: CommandCodeBot <noreply@commandcode.ai> --------- Co-authored-by: CommandCodeBot <noreply@commandcode.ai>

…oozed by design (#88) Grok live-review finding ([unreviewed-by-grok]): the live homepage is missing the entire <section id="managed-service"> block while the merged homepage on main carries it. Verified 2026-08-11: intended, not a regression - the managed-service buyer path (PRs #10/#11) is snoozed-by-Nish 2026-08-08, the release lane strips the section from every publishable bundle, and the live site (still the 2026-06-20 bundle 07acd07) predates PR #10. Encode the verdict in the guards so future reviews find it: - check-public-live-deploy.mjs: assert id="managed-service" and the exact section marker are absent from the live homepage (previously only covered indirectly via the 'Website Correction' phrase); document the disposition - prepare-public-deploy-bundle.mjs: forbid id="managed-service" in the bundle alongside the other snooze markers - docs/measurement/public-conversion-signal.md: record the review disposition with live evidence and the lift condition verify: npm test (623 checks, 0 failures); node scripts/check-public-live-deploy.mjs (new managed-service checks pass; the 6 stale-bundle failures predate this change); git diff --check

greptile-apps Bot reviewed Aug 6, 2026

View reviewed changes

coderabbitai Bot reviewed Aug 6, 2026

View reviewed changes

chatgpt-codex-connector Bot reviewed Aug 6, 2026

View reviewed changes

coderabbitai Bot mentioned this pull request Aug 6, 2026

feat(measurement): add Website Correction conversion signal #11

Merged

nish3451 mentioned this pull request Aug 7, 2026

Fix claim-guard false positives, rename the offer, drop plumbing language #9

Merged

Merge branch 'main' into nightly/public-conversion-path

99653ca

greptile-apps Bot reviewed Aug 7, 2026

View reviewed changes

nish3451 merged commit 01db83e into main Aug 7, 2026
3 checks passed

nish3451 mentioned this pull request Aug 11, 2026

fix(public): repair the tinystudio.in production deploy path #70

Closed

chatgpt-codex-connector Bot mentioned this pull request Aug 11, 2026

fix(ops): guard against duplicate same-fix pull requests #80

Merged

nish3451 mentioned this pull request Aug 11, 2026

fix(public): land the tinystudio.in release lane so the live site can leave the June-20 bundle #81

Merged

nish3451 mentioned this pull request Aug 11, 2026

fix(public): review-dispose the missing managed-service section as the snoozed buyer path #88

Merged

coderabbitai Bot mentioned this pull request Aug 11, 2026

fix(public): name the Website Correction buyer audience in the homepage hero #91

Merged

This was referenced Aug 21, 2026

docs(lane1): reverify trust-page heading-hierarchy item — fixed in PR #74 and now verified live #240

Merged

docs(lane1): re-verify homepage managed-service section absence is the honored snooze #241

Merged

Navigation Menu

Uh oh!

feat(public): route founders to reviewed Website Correction - #10

feat(public): route founders to reviewed Website Correction#10
nish3451 merged 2 commits into
mainfrom
nightly/public-conversion-path

nish3451 commented Aug 6, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

greptile-apps Bot left a comment

Uh oh!

coderabbitai Bot commented Aug 6, 2026 •

edited

Loading

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Aug 6, 2026

Uh oh!

chatgpt-codex-connector Bot Aug 6, 2026

Uh oh!

greptile-apps Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

nish3451 commented Aug 6, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

greptile-apps Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot commented Aug 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Aug 6, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Aug 6, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

nish3451 commented Aug 6, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Aug 6, 2026 •

edited

Loading