feat(webapp,cli,database): track real dev onboarding progress

[ericallam]

Summary

The dev environment "Get set up" panel used to be a static list of CLI commands that only disappeared once your tasks registered, so nothing ever changed after you ran init and people assumed it was stuck. It now tracks real progress: trigger init records the project as initialized, so step 1 checks off, and the panel updates live as the dev server connects and your tasks register.

It also adds a prominent "Copy AI agent prompt" button, presented as a clear alternative ("or") to the manual CLI steps, that copies a ready-to-paste setup prompt pre-filled with your project reference for Claude Code, Cursor, or any coding agent.

Notes

• Adds a Project.initializedAt column (migration 20260811065646_add_project_initialized_at); the CLI init command calls a new project-scoped POST /api/v1/projects/:ref/init best-effort at the end of setup.
• The init scaffold now imports from @trigger.dev/sdk instead of the deprecated /v3 subpath.

Screenshots

[changeset-bot]

🦋 Changeset detected

Latest commit: c14bfa7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 27 packages

Name	Type
trigger.dev	Patch
@internal/dashboard-agent	Patch
@trigger.dev/build	Patch
@trigger.dev/core	Patch
@trigger.dev/python	Patch
@trigger.dev/react-hooks	Patch
@trigger.dev/redis-worker	Patch
@trigger.dev/rsc	Patch
@trigger.dev/schema-to-json	Patch
@trigger.dev/sdk	Patch
@trigger.dev/database	Patch
@trigger.dev/otlp-importer	Patch
@trigger.dev/rbac	Patch
@trigger.dev/sso	Patch
@internal/cache	Patch
@internal/clickhouse	Patch
@internal/llm-model-catalog	Patch
@internal/metrics-pipeline	Patch
@internal/redis	Patch
@internal/replication	Patch
@internal/run-engine	Patch
@internal/run-store	Patch
@internal/schedule-engine	Patch
@internal/testcontainers	Patch
@internal/tracing	Patch
@internal/tsql	Patch
@internal/sdk-compat-tests	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

The change adds project initialization tracking with a nullable database timestamp and an authenticated initialization API. The CLI marks projects initialized after scaffolding and updates generated SDK imports. The web application loads initialization state, receives initialization events through SSE, and shows progress based on project and development-server state. The onboarding UI also adds a copyable AI-agent setup prompt.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	⚠️ Warning	The description explains the main changes and includes screenshots, but it omits the required issue, checklist, testing, and changelog sections.	Add the missing issue reference, checklist, testing steps, and changelog entry using the repository template.

✅ Passed checks (3 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly identifies the primary change: tracking real development onboarding progress across the web app, CLI, and database.

✨ Finishing Touches 💡 2

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/dev-onboarding-state-aware

---

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 map

As of c14bfa7.

18/100 over 414 measured of 430 entry points (base 18, no change)

What this PR changed

route	base	head	now failing
/api/v1/projects/:projectRef/init	new	0	error-classification, request-context

FIX FIRST

• /api/v1/projects/:projectRef/envvars (sensitive) - auth-boundary, request-context
• /auth/sso (sensitive) - auth-boundary, request-context
• /_app/orgs/:organizationSlug/settings/team (sensitive) - error-classification, auth-scope, request-context

AUDIT 3 of 50 sensitive mutations record an actor. 47 without one.
CONTEXT 11 of 414 entry points name a tenant on a failure path. 325 appear only here, 39 of them sensitive, in the JSON rather than the fix list.

What the score is made of

CHECKS
  error-classification  169 applicable,  94 pass,   0 sole, global without it 10
  auth-boundary          62 applicable,  57 pass,   0 sole, global without it 15
  auth-scope             19 applicable,  17 pass,   0 sole, global without it 18
  request-context       414 applicable,  11 pass, 223 sole, global without it 63
  audit-trail            50 applicable,   3 pass,   0 sole, not in the score

The score and findings here are report-only and never gate the merge. Separately, a required test suite keeps this tool's symbol and route lists in sync with the code they name, and can fail a pull request that renames or removes a symbol they reference, or that adds the first route with a segment they anticipate. Each failure names the list to edit. The rules and their reasons: internal-packages/observability-map/README.md.

[pkg-pr-new]

Open in StackBlitz

@trigger.dev/build

npm i https://pkg.pr.new/@trigger.dev/build@c14bfa7

trigger.dev

npm i https://pkg.pr.new/trigger.dev@c14bfa7

@trigger.dev/core

npm i https://pkg.pr.new/@trigger.dev/core@c14bfa7

@trigger.dev/python

npm i https://pkg.pr.new/@trigger.dev/python@c14bfa7

@trigger.dev/react-hooks

npm i https://pkg.pr.new/@trigger.dev/react-hooks@c14bfa7

@trigger.dev/redis-worker

npm i https://pkg.pr.new/@trigger.dev/redis-worker@c14bfa7

@trigger.dev/rsc

npm i https://pkg.pr.new/@trigger.dev/rsc@c14bfa7

@trigger.dev/schema-to-json

npm i https://pkg.pr.new/@trigger.dev/schema-to-json@c14bfa7

@trigger.dev/sdk

npm i https://pkg.pr.new/@trigger.dev/sdk@c14bfa7

commit: c14bfa7