CLI: `snapshot-ui` crashes in text output mode — missing `cliTool` for `tap_coordinate` next step

[dpearson2699]

Description

xcodebuildmcp ui-automation snapshot-ui crashes when using the default text output format. The snapshot itself succeeds, but the CLI renderer throws when formatting the "next steps" section because the tap_coordinate tool entry is missing a cliTool mapping.

Version

xcodebuildmcp@2.0.7
node v24.13.0
macOS

Steps to Reproduce

1. Boot a simulator
2. Launch any app
3. Run:

   xcodebuildmcp ui-automation snapshot-ui --simulator-id <UDID>

Expected Behavior

The UI hierarchy prints successfully with suggested next steps.

Actual Behavior

Exit code 1 with:

Error: Next step for tool 'tap_coordinate' is missing cliTool - ensure enrichNextStepsForCli was called
    at formatNextStepForCli (…/next-steps-renderer.js:6:11)
    at renderNextStep (…/next-steps-renderer.js:41:41)
    at …/next-steps-renderer.js:49:62
    at Array.map (<anonymous>)
    at renderNextStepsSection (…/next-steps-renderer.js:49:24)
    at processToolResponse (…/next-steps-renderer.js:60:28)
    at printToolResponse (…/cli/output.js:8:21)
    at Object.handler (…/cli/register-tool-commands.js:120:7)

Workaround

Using --output json bypasses the text renderer and returns the hierarchy successfully:

xcodebuildmcp ui-automation snapshot-ui --simulator-id <UDID> --output json

Root Cause (likely)

In next-steps-renderer.js, formatNextStepForCli expects every next-step tool to have a cliTool property. The tap_coordinate entry returned by snapshot-ui is missing this mapping — it wasn't added in enrichNextStepsForCli.

The fix is likely adding cliTool: "tap" (or the correct CLI command name) to the tap_coordinate tool mapping in the enrichment step.

[dpearson2699]

Local patch (verified working)

The fix is a 3-line change in build/utils/responses/next-steps-renderer.js. Instead of throwing when cliTool is missing, return null and filter it out downstream.

Diff

 function formatNextStepForCli(step) {
   if (!step.cliTool) {
-    throw new Error(
-      `Next step for tool '${step.tool}' is missing cliTool - ensure enrichNextStepsForCli was called`
-    );
+    return null;
   }

 function renderNextStep(step, runtime) {
   const formatted = runtime === "cli" ? formatNextStepForCli(step) : formatNextStepForMcp(step);
+  if (!formatted) {
+    return null;
+  }
   return `${step.label}: ${formatted}`;
 }

 function renderNextStepsSection(steps, runtime) {
   if (steps.length === 0) {
     return "";
   }
   const sorted = [...steps].sort((a, b) => (a.priority ?? 0) - (b.priority ?? 0));
-  const lines = sorted.map((step, index) => `${index + 1}. ${renderNextStep(step, runtime)}`);
+  const lines = sorted.map((step) => renderNextStep(step, runtime)).filter(Boolean);
+  if (lines.length === 0) {
+    return "";
+  }
+  const numbered = lines.map((line, index) => `${index + 1}. ${line}`);
   return `
 
 Next steps:
-${lines.join("\n")}`;
+${numbered.join("\n")}`;

Alternatively, the proper fix would be to add the cliTool mapping for tap_coordinate (likely "tap") in whatever enrichment step populates cliTool on next-step entries — but I didn't trace that far into the source.

Applied locally on v2.0.7, snapshot-ui now works correctly in CLI mode.