[codex] Add builder promotion modal

[riderx]

Summary (AI generated)

• Added a global Capgo Builder promotion modal for signed-in users who have not started native builds.
• Stores weekly dismissal and permanent opt-out in user_metadata.capgo_builder_promotion without a database migration.
• Routes users to the first app's Builds tab, or app creation when no app exists.
• Added PR screenshot asset for review.
• Added a narrow typos exclude for the existing committed missing_indexs migration filename so CI can complete without editing committed migrations.

Motivation (AI generated)

Capgo Builder needs a visible in-app prompt so users discover native cloud builds after login. The modal appears weekly after the primary “Later” action, stops after builder activity is detected, and keeps “Never show this again” available but tucked behind a secondary disclosure.

Business Impact (AI generated)

This should increase awareness and setup of Capgo Builder, improving adoption of native cloud builds and the revenue path around build usage while avoiding repeated prompts for users who already use the feature or opt out.

Screenshot (AI generated)

Test Plan (AI generated)

• typos .
• bun lint
• bun run typecheck:frontend
• bun run build
• Commit hook: bun run cli:typecheck && bun run typecheck:backend && bun run typecheck:frontend
• Headless browser smoke check at http://127.0.0.1:5173/ with 0 runtime errors

Generated with AI

[coderabbitai]

Warning

Review limit reached

@riderx, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 45 minutes and 55 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 30d9456d-1e4d-4296-8c2c-2b0d15592edd

📥 Commits

Reviewing files that changed from the base of the PR and between 5aca18b and 6a5e35c.

⛔ Files ignored due to path filters (1)

• docs/pr/builder-promotion-modal.png is excluded by !**/*.png

📒 Files selected for processing (6)

• .typos.toml
• messages/en.json
• read_replicate/schema_replicate.sql
• src/App.vue
• src/components.d.ts
• src/components/BuilderPromotionModal.vue

---

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

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing codex/builder-promotion-modal (20d75b2) with main (00e3df3)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[42Clownfish]

Reviewed the builder promotion modal flow and the attached UI artifact. No blocker in the implementation itself: the modal is limited to signed-in dashboard/app routes, skips restricted org states, treats build-activity lookup failures as already-active so it fails closed, and persists both weekly dismiss and permanent opt-out in user metadata without adding schema surface. The CTA target also falls back cleanly to app creation when no app exists.\n\nOne merge readiness note: GitHub currently marks this PR as conflicting, so it still needs a rebase/conflict resolution before it can land even though the checks are green.