@maka/maka-cli 5.217.0 → 5.218.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.217.0",
+  "version": "5.218.0",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 3.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 3.x applications using React.",

package/bundle/typescript/src/commands/game/sideQuest/commands/give.js

@@ -91,6 +91,35 @@ export class GiveCommand extends Command {
             this.logger.write(`${this.actor.name} tried to give item "${itemOrAmount}" but does not have it.`);
             return `You don’t have "${itemOrAmount}".`;
         }
+        // A DELIVERED OBJECTIVE DOES NOT COME BACK (qk7TtQqyaT4CaWNka, Maka:
+        // "when I returned from a job, after giving Ms. Halvorsen the Skim
+        // Ledger Archive -- I kept a copy, is that by design?").
+        //
+        // It was not a copy, and nothing duplicated anything. The transcript
+        // (session vi2bvgA7XhHZRjwYL) has Ted hand the chip over, the job
+        // complete -- "The ledger's yanked clean ... Karma earned: 4" -- a
+        // beat where "Ms. Halvorsen's hand shoots out and closes around the
+        // datachip", and then, one line later:
+        //
+        //   Ms. Halvorsen give Skim Ledger Archive to Ted
+        //
+        // Her AI issued a `give` and handed the paydata straight back, so the
+        // runner walked out of a finished job still holding the thing he had
+        // just been paid for. The brief's own example of a matching command
+        // is `give <item> to <name>`, which is exactly the shape a model
+        // echoes when it has just been handed something.
+        //
+        // So the engine settles it rather than the prompt. Once the win
+        // condition is SATISFIED, the objective item is spent: it is the
+        // client's now, and no hand -- theirs, a bystander's, or the
+        // runner's -- passes it on. Scoped hard to the completed objective:
+        // an ordinary chip, an unfinished job, and the reward item all move
+        // exactly as they did.
+        const won = this.scene.getWinCondition?.();
+        if (this.scene.isCompleted?.() && won?.item.toLowerCase() === item.name.toLowerCase()) {
+            this.logger.write(`${this.actor.name} tried to pass on the delivered objective "${item.name}"; refused (job already settled).`);
+            return `The ${item.name} is already delivered and paid for -- it belongs to the client now, and nobody is handing it back.`;
+        }
         if (servedFromShelf) {
             room.inventory.removeItem(item.name);
             try {

package/bundle/typescript/src/commands/game/sideQuest/engine-version.js

@@ -1163,5 +1163,27 @@
 //     and a room with a node has exactly one; the tree says the same
 //     thing in a shape that can be read. A watched room with NO node
 //     still names no master, pinned as a test.
-export const ENGINE_VERSION = '1.76.0';
+// 1.77.0 (2026-09-16): A DELIVERED OBJECTIVE DOES NOT COME BACK
+//   (qk7TtQqyaT4CaWNka, Maka: "when I returned from a job, after giving
+//   Ms. Halvorsen the Skim Ledger Archive -- I kept a copy, is that by
+//   design?"). It was not a copy and nothing duplicated anything -- the
+//   vetting could not find it in the transcript because it was not
+//   looking for a `give`. Session vi2bvgA7XhHZRjwYL, in order: Ted hands
+//   the chip over, the job completes ("The ledger's yanked clean ...
+//   Karma earned: 4"), a beat where "Ms. Halvorsen's hand shoots out and
+//   closes around the datachip" -- and then, one line later:
+//     Ms. Halvorsen give Skim Ledger Archive to Ted
+//   Her AI issued a `give` and handed the paydata straight back, so the
+//   runner walked out of a finished job still holding what he had just
+//   been paid for. The brief's own example of a matching command is
+//   `give <item> to <name>`, which is the shape a model echoes when it
+//   has just been handed something -- so the ENGINE settles it rather
+//   than the prompt. Once the win condition is satisfied the objective
+//   item is spent: it belongs to the client, and no hand passes it on.
+//   Scoped hard to the COMPLETED objective. An ordinary chip, the reward
+//   item, and above all the delivery itself keep moving -- a gate that
+//   read the win condition without reading completion would make the job
+//   unwinnable, which is a worse bug than the one being fixed, and that
+//   is the load-bearing test in the file.
+export const ENGINE_VERSION = '1.77.0';
 //# sourceMappingURL=engine-version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.217.0",
+  "version": "5.218.0",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 3.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 3.x applications using React.",