fix(dashboard): unblock the install step and point Home at it

[izadoesdev]

Release of three staging commits (cherry-picked with -x from 83618f1, f7e356c, 979eff4).

Why: across the last 30 days of signups (153 users, Postgres joined to ClickHouse), users whose site received data came back 24h–8 days after signup 60% of the time; users with a site but no data, or no site, came back 9% of the time. Samples are small and this is correlation. Since the current onboarding shipped on Oct 5, 40 users created a site and 21 went live. Most installs happened outside the onboarding Connect step.

• fix(dashboard): let new users connect their app while Databunny reads the site. The checklist kept "Connect your app" pending, with the text "Ready once the brief is", for as long as the optional AI site read ran. Connect is now active as soon as the site exists and sits above the read row, so focus goes straight to it. ConnectApp already explains that the prompt improves once the brief lands. Until a site exists, the card only shows the website form, with no list of pending rows.
• fix(dashboard): name the manual install option in Connect. "Or install it yourself" becomes "Or add the script tag or SDK yourself". The agent-first layout stays: the agent prompt is the path most people pick (18 users vs 6 for the script tag over 30 days). The E2E selector is updated.
• feat(dashboard): prompt Home to install tracking until a site has data. Users with no site most often ended on Home (median 20s), where every stat read zero. Home now shows a single prompt above the stats until any site has page views: "Install tracking on {domain}" linking to the site's install gate, or "Add your website" opening the existing dialog.

Verification: dashboard tsc clean, dashboard unit tests 207 pass, Biome clean, commit hooks pass. These have not been rendered in a browser locally; I didn't start the dev server. The Dashboard Playwright CI jobs cover onboarding and website setup.

---

Summary by cubic

Unblocks the onboarding Connect step so new users can install tracking while the AI site read runs, and prompts Home to steer users without data toward the install step. This targets retention: over the last 30 days, users whose site received data returned 60% of the time vs 9% for those without (small samples, correlation only).

Changes

• Connect is active as soon as a site exists and is listed above the site-read row; until a site exists, the checklist shows only the website form.
• The manual install option is renamed to "Or add the script tag or SDK yourself", and the E2E selector is updated.
• Home shows a single prompt — "Install tracking on {domain}" or "Add your website" — above the stats until any site has ever had data.

^{Written for commit 93adfc4. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
dashboard	Ready	Preview	Oct 8, 2026 11:24pm UTC
databuddy-status	Ready	Preview	Oct 8, 2026 11:24pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
documentation	Skipped		Oct 8, 2026 11:24pm UTC

[unkey-deploy]

The latest updates on your projects. Learn more about Unkey Deploy

Name	Status	Preview	Inspect	Updated (UTC)
links (preview)	Ready	Visit Preview	Inspect	Oct 8, 2026 11:24pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 99201e46-32af-473f-913f-b0e99bf35460

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Observability score · 31

poor · unchanged against main · no regression

1 instrumented · 0 partial · 8 dark

Fix first (3)

• POST /api/test/e2e/session apps/dashboard/app/api/test/e2e/session/route.ts:172: wide-event, context, structured-errors, audit
• GET /api/auth/:all* apps/dashboard/app/api/auth/[...all]/route.ts:60: wide-event, context, audit
• POST /api/auth/:all* apps/dashboard/app/api/auth/[...all]/route.ts:64: wide-event, context, audit

_{evlog map v0.8.0 · how the score works · what each check expects}

[greptile-apps]

Confidence Score: 4/5

[Medium impact] Reorders onboarding steps and adjusts setup flow messaging.

The array-access requirement must be satisfied before merging; Home also has a non-blocking issue that can bring back the install prompt for an already active workspace.

Findings

1.  Install prompt returns unnecessarily ▶
2.  Array access breaks team style ▶

Summary

This PR makes Connect available while site research runs, puts it ahead of the research row, and simplifies the checklist before website creation. It also names the manual install choices and adds a setup prompt to Home.

• Home's prompt can return when an older tracked site has no recent views and another site has never received data.
• The new first-item lookup needs to follow the repository's required array-access style.
• izadoesdev explicitly states that hiding the remaining checklist rows before website creation is intentional.

_{Reviews (1) · Last reviewed commit: "feat(dashboard): prompt Home to install ..." · Reviewed by Greptile}