fix(cli): gate init AI hand-off on actual install, fix profile flag

The "let my AI set it up" hand-off was gated on what the user selected, not
what installed, so a failed skills install still offered it and claimed the
getting-started skill was ready. Gate it on actual installs and describe only
the tooling that landed. Also fix an inverted profile flag in the next-steps
message that printed `--profile undefined` when no profile was set.

Author: ericallam

packages/cli-v3/src/commands/init.ts

@@ -173,14 +173,21 @@ async function _initCommand(dir: string, options: InitCommandOptions) {
 
     const selectedTooling = isCancel(tooling) ? [] : tooling;
 
+    // Track what actually installed (not just what was selected), so the AI hand-off is
+    // only offered, and only described, in terms of tooling that really landed.
+    let installedSkills = false;
+    let installedMcp = false;
+
     // Skills are auth-free and bundled in the CLI. The user opted in here, so install
     // straight away (no extra confirm). If they declined, still mark the prompt seen so
     // `trigger dev` doesn't ask about skills a second time.
     if (selectedTooling.includes("skills")) {
       log.step("Installing the Trigger.dev agent skills");
-      const [skillsError] = await tryCatch(installSkillsFromInit());
+      const [skillsError, installed] = await tryCatch(installSkillsFromInit());
       if (skillsError) {
         log.warn(`Skipped agent skills: ${skillsError.message}`);
+      } else {
+        installedSkills = installed === true;
       }
     } else {
       await tryCatch(markSkillsPromptSeen());
@@ -202,12 +209,14 @@ async function _initCommand(dir: string, options: InitCommandOptions) {
         outro(`Failed to install MCP server: ${installError.message}`);
         return;
       }
+
+      installedMcp = true;
     }
 
-    // Vibe path: once AI tooling is set up, the user can hand scaffolding to their
-    // assistant (the getting-started skill + MCP) instead of the CLI. Only offered when
-    // they installed something that can drive it.
-    if (selectedTooling.length > 0) {
+    // Vibe path: once AI tooling is actually installed, the user can hand scaffolding to
+    // their assistant instead of the CLI. Only offered when something landed, and the
+    // hand-off message names only the tooling that did.
+    if (installedSkills || installedMcp) {
       const setupChoice = await select({
         message: "How do you want to set up your project?",
         options: [
@@ -219,14 +228,16 @@ async function _initCommand(dir: string, options: InitCommandOptions) {
           {
             value: "ai",
             label: "Let my AI assistant set it up",
-            hint: "use the getting-started skill and MCP server to bootstrap",
+            hint: "hand off and let your assistant bootstrap the project",
           },
         ],
       });
 
       if (!isCancel(setupChoice) && setupChoice === "ai") {
         outro(
-          "Your AI tooling is ready. Ask your assistant to set up Trigger.dev and it will use the getting-started skill to add the SDK, config, and your first task."
+          installedSkills
+            ? "Your AI tooling is ready. Ask your assistant to set up Trigger.dev and it will use the getting-started skill to add the SDK, config, and your first task."
+            : "The MCP server is installed. Ask your assistant to set up Trigger.dev using the MCP server."
         );
         return;
       }
@@ -334,7 +345,7 @@ async function _initCommand(dir: string, options: InitCommandOptions) {
   log.info("Next steps:");
   log.info(
     `   1. To start developing, run ${chalk.green(
-      `npx trigger.dev@${cliTag} dev${options.profile ? "" : ` --profile ${options.profile}`}`
+      `npx trigger.dev@${cliTag} dev${options.profile ? ` --profile ${options.profile}` : ""}`
     )} in your project directory`
   );
   log.info(`   2. Visit your ${projectDashboard} to view your newly created tasks.`);