@maka/maka-cli 5.156.0 → 5.158.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.156.0",
+  "version": "5.158.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/stance.js

@@ -94,8 +94,16 @@ export class StanceCommand extends Command {
         if (onMatrix) {
             return `That's not a Matrix route. Choose: ${MATRIX_STANCE_CYCLE.join(', ')} (${MATRIX_STANCE_CYCLE.map(m => MATRIX_STANCE_ACTION[m]).join(' / ')}).`;
         }
+        // THE EXACT NAME ALWAYS WINS. "stance non-lethal" -- the very word the
+        // refusal below lists -- used to be refused: fuzzyPickName normalizes
+        // punctuation to whitespace, so "non-lethal" and the "non lethal"
+        // alias both became "non lethal", the exact tier saw two candidates,
+        // and an ambiguous guess deliberately misses. Caught by a bench that
+        // typed the name off the "Choose:" line (2jbprbSYqF7EPXrkR's dry run).
         // The old words (and their typos) still land: fuzzy over the cycle AND the aliases, then through the alias map.
-        const pickedRaw = STANCE_ALIASES[raw] ?? fuzzyPickName(args.join(' '), [...STANCE_CYCLE, ...Object.keys(STANCE_ALIASES)]);
+        const pickedRaw = STANCE_CYCLE.includes(raw)
+            ? raw
+            : STANCE_ALIASES[raw] ?? fuzzyPickName(args.join(' '), [...STANCE_CYCLE, ...Object.keys(STANCE_ALIASES)]);
         const picked = pickedRaw ? (STANCE_ALIASES[pickedRaw] ?? pickedRaw) : undefined;
         if (!picked) {
             return `That's not a stance. Choose: ${STANCE_CYCLE.join(', ')}.`;

package/bundle/typescript/src/commands/game/sideQuest/models/npc.js

@@ -1669,6 +1669,17 @@ ${worldEventsSummary}
         const heatSummary = heat
             ? `The district's current HEAT on this run is ${heat}. If you would naturally reassure them that things are quiet, clean, or under control, that claim has to be TRUE against this -- never tell them the coast is clear, that nobody noticed, or that things went quiet if heat says otherwise. Speak honestly about how hot it actually is instead.`
             : '';
+        // A JOB ITEM IN THE WRONG HANDS (5Lq8wNX9szaA45u6b): the runner
+        // handed the client the crate meant for Doc Wrench by mistake, and
+        // she held it through three polite asks, yielding only to a threat.
+        // Same shape as payoutSummary -- nothing told the model whose
+        // delivery the thing in its pocket actually was, so "carry it to
+        // the Stitch yourself" came out as a refusal instead of a handover.
+        const wc = this._scene?.getWinCondition?.();
+        const carriesPrize = !!wc?.item && this.inventory.getAllItems().some(i => i.name === wc.item);
+        const jobItemSummary = carriesPrize && wc?.toNpc && wc.toNpc !== this.name
+            ? `You are currently HOLDING ${wc.item}, which the job needs delivered to ${wc.toNpc} -- not to you. It is the runner's cargo, not yours: if they ask for it back, hand it over in the SAME response with "[COMMAND] give ${wc.item} to <their name>" -- never make them argue or threaten for it, and never keep it as leverage.`
+            : '';
         // If nothing else has happened to/around this NPC yet this scene, this
         // is the first time anyone's reached out -- nudge toward volunteering
         // the job rather than waiting to be asked, which real playtesting
@@ -2113,6 +2124,7 @@ Your objective is to drive the story line.`}
     ${dialogueSummary}
     ${eph ? '' : payoutSummary}
     ${eph ? '' : heatSummary}
+    ${eph ? '' : jobItemSummary}
 
     ${roomDesc}${spotBlock}${combatSpatialBlock}
     ${formattedExitsStr}

package/package.json

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