@invarn/cli 0.2.3 → 0.2.5

package/dist/sdk.mjs

@@ -8853,6 +8853,15 @@ async function handleAgentRegister(args) {
       lines.push(`Pipeline file written to: ${result.pipelinePath}`);
       lines.push(`Commit and push the file when ready \u2014 the agent can run locally in the meantime.`);
     }
+    if (Array.isArray(result.warnings) && result.warnings.length > 0) {
+      lines.push("");
+      lines.push("\u26A0\uFE0F  Warnings:");
+      for (const w of result.warnings) {
+        lines.push(`  - ${w}`);
+      }
+      lines.push("");
+      lines.push("Consider re-registering with split commands if the chained phases are distinct concepts. See STEP SPLITTING in the registration guidance.");
+    }
     return { content: [{ type: "text", text: lines.join("\n") }] };
   } catch (err) {
     return { content: [{ type: "text", text: `Error: ${err.message}` }], isError: true };
@@ -8867,6 +8876,22 @@ var REGISTRATION_GUIDANCE = [
   "  If it does, read it \u2014 the build steps are already defined there. Base your agent's commands on them.",
   "  Do NOT explore the project structure if a pipeline file already tells you the build commands.",
   "",
+  "STEP SPLITTING \u2014 one concept per command:",
+  "  When you have multiple natural phases (setup, compile, test, package, sign, deploy), SPLIT them into separate commands.",
+  "  Rule of thumb: if your single `run` field contains `&&` joining distinct concepts, that's a signal to split.",
+  "  Example of a BAD single command (distinct phases chained together):",
+  `    run: "printf '...' > local.properties && xcodebuild -scheme iosApp build"`,
+  "  Better as two commands:",
+  `    [{name:"config", run:"printf '...' > local.properties"},`,
+  '     {name:"build",  run:"xcodebuild -scheme iosApp build"}]',
+  "  Why it matters:",
+  "    \u2022 Each command is its own step in the PR check run \u2014 reviewers see exactly which phase broke.",
+  '    \u2022 Failed step name appears in the check summary (e.g. "Build failed at step `build`" is much more useful than a generic "build failed").',
+  "    \u2022 Per-step duration is tracked \u2014 spot slow phases.",
+  "    \u2022 cibuild auto-injects cache steps between commands; one mega-step defeats that.",
+  "    \u2022 Individual steps can be individually retried in future (phase 4 of the roadmap).",
+  "  Shell flow inside ONE command (pipes, variable assignment, short guards) is fine. Splitting is for DISTINCT PHASES, not every line.",
+  "",
   "DESCRIPTION: Write 3 sentences for other AI agents to read.",
   "  1. What this agent does (include specific tools: Gradle, Xcode, pytest, etc.)",
   "  2. When to use it (the trigger condition)",
@@ -9163,9 +9188,11 @@ var TOOL_SPECS = [
       description: z2.string().describe("What this agent does, when to use it, and what it does not do"),
       repository: z2.string().optional().describe('Repository to bind to (e.g. "owner/repo-name"). Required if the org has multiple repos connected. Omit if only one repo.'),
       commands: z2.array(z2.object({
-        name: z2.string().describe('Command name (e.g. "compile")'),
+        name: z2.string().describe('Command name \u2014 short, lowercase, hyphenated, matches the concept (e.g. "config", "compile", "test", "package")'),
         run: z2.string().describe('Shell command to execute (e.g. "./gradlew assembleDebug")')
-      })).describe("List of commands this agent can run"),
+      })).describe(
+        'Ordered list of commands. SPLIT NATURAL PHASES INTO SEPARATE COMMANDS \u2014 one concept per command. If you find yourself chaining distinct phases with `&&` (e.g. write a config file THEN build, or compile THEN archive THEN sign), those belong in separate commands. Each command becomes its own step in the check-run output, gets its own duration, and fails the build with a clear "Failed at step X" summary instead of "build step failed" for an 8-minute merged operation. Example: for "write local.properties from secrets, then xcodebuild", use two commands: [{name:"config", run:"printf ... > local.properties"}, {name:"build", run:"xcodebuild ..."}] \u2014 NOT one command that chains both with `&&`.'
+      ),
       overwrite: z2.boolean().optional().describe("Set true to replace a pipeline file that already exists at .ci/pipelines/agent-<name>.yml in the repo. Use this when re-registering an agent \u2014 e.g. the same repo is connected under another org, or a prior registration was deleted without cleaning up the committed file. Do NOT set this when the existing file is hand-authored YAML unrelated to a prior agent."),
       triggers: z2.array(z2.object({
         push_branch: z2.string().optional().describe('Match push events where the pushed branch matches this pattern (glob). Use "*" for any branch.'),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@invarn/cli",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "Invarn CLI — run builds, check artifacts, and ship from your terminal",
   "type": "module",
   "main": "dist/invarn.cjs",