@mutagent/cli 0.2.139 → 0.2.140

package/dist/bin/cli.js

@@ -22071,8 +22071,9 @@ The same token reads this workspace's reports: \`mutagent reports list --json\`
 \`mutagent reports show <id> --json\` work in a sandbox with no key. Review and
 retract need a signed-in key and fail with \`SANDBOX_SCOPE\` in a sandbox.
 
-Locally none of this exists: pass the entry id, the run id and the build
-(\`--build-target\`, \`--build-rev\`) explicitly. A command that needs one and gets
+Locally none of this exists: pass the entry id and the run id explicitly, and the
+build (\`--build-target\`, \`--build-rev\`) only when a build ran. With no build, leave
+both out rather than sending the checkout's HEAD. A command that needs an id and gets
 none fails with \`MISSING_ARGUMENTS\`; it never guesses.
 
 ## Binding
@@ -22144,9 +22145,12 @@ before the first use.
    a refusal there (its \`code\`) leaves the entry registered: tell the user the code.
 4. **Show the result.** Render \`_directive.renderedCard\` verbatim, then
    \`mutagent factory show <id> --json\` to show the targets and the spec version.
-5. **Record the spec stage**: \`mutagent factory stage record --stage spec --state succeeded --spec-version <n> --json\`
+5. **Record the spec stage (required)**:
+   \`mutagent factory stage record --stage spec --state succeeded --spec-version <n> --json\`
    (\`<n>\` the version just recorded; pass \`<id>\` first only when this checkout links several entries).
-   Do the same after a \`spec push\` of a new version.
+   The spec stage has no report and no build, so pass neither \`--report\` nor the build flags. It
+   still gets this record: skipping the report push never skips it. Do the same after a
+   \`spec push\` of a new version. Check it with \`mutagent factory stage list <id> --json\`.
 
 | Refusal | What to do |
 |---|---|
@@ -22362,10 +22366,14 @@ Never run a stage in a local child process: no one could see it.
 
 ## P4: record a stage that ran locally
 
-Locally nothing defaults: pass the entry, the spec version and the build.
+Locally nothing defaults: pass the entry and the spec version. Pass the build
+(\`--build-target\`, \`--build-rev\`) only when a build ran: a build stage or a build
+artifact exists for this work. Otherwise leave both out; the checkout's HEAD is not a
+build.
 
 1. **Open a run before the work** when it takes a while:
-   \`mutagent factory stage start <entry-id> --stage evaluate --spec-version <n> --build-target <target-id> --build-rev <rev> --json\`.
+   \`mutagent factory stage start <entry-id> --stage evaluate --spec-version <n> --json\`, or
+   \`mutagent factory stage start <entry-id> --stage evaluate --spec-version <n> --build-target <target-id> --build-rev <rev> --json\` (after a build).
    Keep the printed run id (\`sr_…\`).
 2. **Push the report**, attached to the run:
    \`mutagent reports push <run-dir> --stage-run <run-id> --json\`. The report
@@ -22373,7 +22381,8 @@ Locally nothing defaults: pass the entry, the spec version and the build.
 3. **Finish it:** \`mutagent factory stage finish <run-id> --state succeeded --verdict PASS --json\`.
 
 For work that already finished, one call records it, closed:
-\`mutagent factory stage record <entry-id> --stage evaluate --state succeeded --verdict PASS --spec-version <n> --build-target <target-id> --build-rev <rev> --report <report-id> --json\`.
+\`mutagent factory stage record <entry-id> --stage evaluate --state succeeded --verdict PASS --spec-version <n> --report <report-id> --json\`, or
+\`mutagent factory stage record <entry-id> --stage evaluate --state succeeded --verdict PASS --spec-version <n> --build-target <target-id> --build-rev <rev> --report <report-id> --json\` (after a build).
 Push the report first (step 2 without \`--stage-run\`) to get its id.
 
 Confirm each write with the user first.
@@ -39187,7 +39196,7 @@ function registerRecord(stage) {
       ["VALIDATION_ERROR", "record takes a finished state; use stage start for a running one. --ended-at must not be before --started-at"],
       SCOPE3
     ],
-    directive: ["A write: confirm with the user first. Locally pass the build explicitly (--build-target, --build-rev)."]
+    directive: ["A write: confirm with the user first. Locally pass the build (--build-target, --build-rev) only when a build ran; otherwise omit both, never the checkout HEAD."]
   })).action(async (id, options, command) => {
     await runAction(command, async (isJson, output) => {
       if (options.stage === undefined || options.state === undefined) {
@@ -40632,4 +40641,4 @@ if (process.env.CLI_VERSION) {
 }
 runCli(process.argv.slice(2), cliVersion);
 
-//# debugId=13A1645D4E9B5AE164756E2164756E21
+//# debugId=B184832158B4433E64756E2164756E21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mutagent/cli",
-  "version": "0.2.139",
+  "version": "0.2.140",
   "description": "Bun-native CLI for the MutagenT AI platform - auth, provider config, and lifecycle-tool installer for AI-native workflows",
   "type": "module",
   "bin": {
@@ -45,7 +45,7 @@
   },
   "dependencies": {
     "@inquirer/prompts": "^8.7.2",
-    "@mutagent/sdk": "0.8.73",
+    "@mutagent/sdk": "0.8.74",
     "@sinclair/typebox": "^0.34.0",
     "chalk": "^5.3.0",
     "commander": "^12.1.0",
@@ -94,5 +94,5 @@
   "bugs": {
     "url": "https://docs.mutagent.io/support"
   },
-  "gitHead": "dcb4a4909ee768037802ee4855d4ef1b5f98eb0e"
+  "gitHead": "e5f8c75b341d78f265b621a397c4f7efd67edfde"
 }