@koda-sl/baker-cli 0.92.0 → 0.93.0

package/README.md

@@ -2322,6 +2322,8 @@ baker actions release <action-id>
 
 baker actions create --name "Build hero" --description "..."
 # → returns { ok, data: { tempId }, hints: [...] } — check hints for dependencies/description reminders
+baker actions create --name "Pull data" --description "..." --mission <ref> --order 0
+# → creates the action AND attaches it to the mission as a step in one atomic op (no loose-action flicker)
 baker actions update <action-id> --name "Better name"
 baker actions complete <action-id-or-tempId> --note "What was done"  # stages — applies on chat publish
 baker actions discard <action-id> --reason "obsolete"
@@ -2368,10 +2370,17 @@ A **Mission** groups an ordered set of actions (its "steps") under one goal, wit
 Mission write ops stage on the **same chat draft as actions** and apply atomically on the existing publish — there is no separate apply. `BAKER_CHAT_ID` must be set for every command except `list`/`get`.
 
 ```bash
-# Open a mission (returns { ok, data: { missionTempId }, hints })
+# 1. Open the mission FIRST with the detailed plan (the overview is the point).
+#    Returns { ok, data: { missionTempId }, hints }.
 baker missions create --title "Audit Google Ads" --overview "## Phase 1 — Pull data\n..."
 
-# Create the action steps in order, then attach each by 0-based --order.
+# 2. Create each step already attached to the mission, in order. This is the
+#    preferred path: create+attach is one atomic op, so a step never appears as
+#    a loose action between create and attach.
+baker actions create --name "Pull data" --description "..." --mission <missionTempId> --order 0
+baker actions create --name "Analyze" --description "..." --mission <missionTempId> --order 1
+
+# Attach an already-existing action to a mission (when it wasn't created with --mission).
 # Both --mission and --action accept a real id or a temp_* ref from the same draft.
 baker missions add-action --mission <id-or-missionTempId> --action <id-or-tempId> --order 0
 

package/dist/cli.js

@@ -547,7 +547,7 @@ var completeCommand = defineCommand2({
 import { defineCommand as defineCommand3 } from "citty";
 registerSchema({
   command: "actions.create",
-  description: "Stage creation of a new action (applies when the chat is published). Returns a tempId you can use to link in the same draft. After creating, check if this action blocks or is blocked by other actions and wire dependencies with `baker actions link`.",
+  description: "Stage creation of a new action (applies when the chat is published). Returns a tempId you can use to link in the same draft. After creating, check if this action blocks or is blocked by other actions and wire dependencies with `baker actions link`. To make this action a mission step, pass --mission and --order \u2014 it attaches atomically, so the step never flickers as a loose action.",
   args: {
     name: { type: "string", description: "Action name (short, action-verb, \u22646 words)", required: true },
     description: {
@@ -555,7 +555,17 @@ registerSchema({
       description: "Context-complete description: what / why / where / done-when",
       required: false
     },
-    "temp-id": { type: "string", description: "Custom tempId (auto-generated if omitted)", required: false }
+    "temp-id": { type: "string", description: "Custom tempId (auto-generated if omitted)", required: false },
+    mission: {
+      type: "string",
+      description: "Attach the new action to this mission (id or missionTempId) as a step, in one atomic op",
+      required: false
+    },
+    order: {
+      type: "string",
+      description: "0-based position of the step within the mission (required when --mission is set)",
+      required: false
+    }
   }
 });
 var createCommand = defineCommand3({
@@ -566,7 +576,9 @@ var createCommand = defineCommand3({
   args: {
     name: { type: "string", description: "Action name", required: false },
     description: { type: "string", description: "Description", required: false, default: "" },
-    "temp-id": { type: "string", description: "Optional custom tempId", required: false }
+    "temp-id": { type: "string", description: "Optional custom tempId", required: false },
+    mission: { type: "string", description: "Mission ref to attach this step to", required: false },
+    order: { type: "string", description: "0-based step position (required with --mission)", required: false }
   },
   run: async ({ args }) => {
     try {
@@ -574,19 +586,31 @@ var createCommand = defineCommand3({
       if (!name || name.trim().length === 0) {
         failValidation("--name is required.");
       }
+      const mission = args.mission;
+      let order;
+      if (mission) {
+        order = Number.parseInt(args.order ?? "", 10);
+        if (Number.isNaN(order) || order < 0) {
+          failValidation("--order must be a non-negative integer when --mission is set.");
+        }
+      }
       const chatId = requireChatId();
       const tempId = args["temp-id"] || generateTempId();
       const response = await apiPost("/api/actions/create", {
         chatId,
         tempId,
         name,
-        description: args.description ?? ""
+        description: args.description ?? "",
+        ...mission ? { missionRef: mission, order } : {}
       });
       const hints = [];
       hints.push(`Link dependencies: baker actions link --blocker <id> --blocked ${tempId}`);
       if (!args.description) {
         hints.push("Add description: baker actions update <tempId> --description '...' (what/why/where/done-when)");
       }
+      if (mission) {
+        hints.push(`Attached to mission ${mission} at order ${order}.`);
+      }
       writeJson({ ...response, hints });
     } catch (err) {
       failApi(err);