@maka/maka-cli 5.217.0 → 5.219.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.217.0",
+  "version": "5.219.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,47 @@
 //     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.
+// 1.78.0 (2026-09-16): CYBERCOMBAT IS NOT LAYING HANDS ON ANYBODY
+//   (27dAZvLuoaW4PjF6s, Maka, the whole report verbatim):
+//     "[order] Agent (Sony CIY-720): attack patrol ic ,
+//      You can't lay hands on Patrol IC: they are not present in their
+//      body, and there is nobody home to resist you."
+//   The absent-body gate in npc-authorization.ts exists for a good
+//   reason -- somebody grabbing a jacked-in runner's slumped shell is
+//   reaching for a person who is not home -- but it asked the question
+//   of every AI-driven actor on every contact verb. An Agent is a
+//   matrix-plane construct (companions.ts builds it with plane:
+//   'matrix') and Patrol IC has no body to be absent FROM, so a rule
+//   about hands fired on a program attacking a program and refused the
+//   most ordinary order anyone gives an agent. Attacking an icon is
+//   Cybercombat (Data Spike, p.239): two icons, no meat, nobody's hands
+//   anywhere near it. The question is now asked only of an actor
+//   standing in the meat; canPerceive, which is the rule that actually
+//   knows about planes, still decides whether the two can reach each
+//   other at all. The meat case is pinned in the same test file, because
+//   a fix that traded this report for the older one it was built from
+//   would be no fix.
+export const ENGINE_VERSION = '1.78.0';
 //# sourceMappingURL=engine-version.js.map

package/bundle/typescript/src/commands/game/sideQuest/utilities/npc-authorization.js

@@ -66,7 +66,26 @@ export function authorizeNpcAction(scene, actor, verb, args) {
     // which is lying right there in the room and is what the act was
     // reaching for. For a hands-on verb the absent-body reason is the one
     // that tells the fiction something it can use.
-    if (contact && !isPresentInBody(target)) {
+    // ...AND IT IS A RULE ABOUT HANDS, SO IT ONLY BINDS A BODY
+    // (27dAZvLuoaW4PjF6s, Maka -- the whole report, verbatim):
+    //
+    //   "[order] Agent (Sony CIY-720): attack patrol ic ,
+    //    You can't lay hands on Patrol IC: they are not present in their
+    //    body, and there is nobody home to resist you."
+    //
+    // An Agent is a matrix-plane construct (commands/companions.ts builds
+    // it with plane: 'matrix') and Patrol IC has no body to be absent
+    // from -- so a gate written for "somebody grabbed a jacked-in
+    // runner's slumped shell" fired on a program attacking a program,
+    // and refused the single most ordinary order anyone gives an agent.
+    //
+    // Attacking an icon is CYBERCOMBAT (Data Spike, p.239): two icons,
+    // no meat, nobody's hands anywhere near it. So the absent-body
+    // question is only asked of an actor standing in the meat. Everything
+    // else is still gated -- canPerceive below decides whether these two
+    // can reach each other at all, and it is the rule that actually knows
+    // about planes.
+    if (contact && actor.plane === 'meat' && !isPresentInBody(target)) {
         return {
             allowed: false,
             reason: `You can't lay hands on ${target.name}: they are not present in their body, and there is nobody home to resist you. Describe what you see, or wait for them to come back.`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.217.0",
+  "version": "5.219.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.",