@maka/maka-cli 5.172.0 → 5.173.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.172.0",
+  "version": "5.173.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/backlog.js

@@ -160,7 +160,14 @@ export class BacklogCommand extends Command {
             // different timestamps on different machines -- so without this
             // two reports about the same moment cannot be tied together. Seen
             // for real: one run produced items stamped 00-18-43 and 00-18-15.
-            sharedRunId: game?.remoteSession?.id,
+            // A HOSTED RUN NAMES ITSELF (2026-09-12, the reporter's note on
+            // ZdhkP8mAP9QhpqFvA): the browser client's session has no log
+            // file to upload, but its id is the key to the event stream the
+            // site keeps -- and the site reads the transcript off that
+            // (game-backlog-vetting.ts sessionEventsExcerpt). The CLI's own
+            // shared-run link keeps its id; the headless host's is the same
+            // GameSessions id under another name.
+            sharedRunId: game?.remoteSession?.id ?? currentSession()?.sessionId,
             cliVersion: cliVersion(),
             engineVersion: engineVersion(),
             platform: process.platform,

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

@@ -410,5 +410,10 @@
 //   in Medicine aftercare (+hits as recovery dice, once per set of wounds,
 //   persisted), the street doc has the Medicine skill, and a doc asked
 //   about wounds names the verb and the price.
-export const ENGINE_VERSION = '1.47.0';
+// 1.48.0 (2026-09-12): THE ROOM AND THE REPORT. A hosted run's backlog
+//   report names its session (sharedRunId) so the site can vet it with the
+//   run's own transcript; an exit-serving spot that is furniture (a booth,
+//   a counter) sits beside its doorway instead of on it; a job's objective
+//   is clamped to a carriable weight at scene build.
+export const ENGINE_VERSION = '1.48.0';
 //# sourceMappingURL=engine-version.js.map

package/bundle/typescript/src/commands/game/sideQuest/factories/scene-factory.js

@@ -5,6 +5,9 @@ import { Door } from '../models/door.js';
 import { RoomFactory } from './room-factory.js';
 import { NPCFactory } from './npc-factory.js';
 import { ItemFactory } from './item-factory.js';
+/** The heaviest a job's prize may be: a Strength 1 runner carries 30 kg
+ *  (player.ts maxCarryingWeight), and they still need room for gear. */
+export const OBJECTIVE_MAX_WEIGHT_KG = 15;
 import { Category } from '../types/shared/item-enum.js';
 import { Logger } from '../utilities/logger.js';
 import { migrateLegacySeed } from './seed-migration.js';
@@ -262,6 +265,21 @@ Key Locations: ${json.rooms.map(r => r.name).join(', ')}
         const itemMap = new Map();
         for (const itemJson of json.items ?? []) {
             const item = await itemFactory.createItemFromJson(itemJson);
+            // THE PRIZE HAS TO BE CARRIABLE (KSfzQzuHTx7kHjohi, 2026-09-12:
+            // "I shouldn't have an item I need to return, that I can't carry
+            // -- this case is too heavy"). The seed's items are written by a
+            // model that does not know the carry cap (20 + Strength x 10 kg,
+            // player.ts maxCarryingWeight); a "heavy case" at 60 kg is a job
+            // no runner can finish. The win condition's item is clamped to a
+            // weight the weakest runner can lift -- an objective you cannot
+            // pick up is a seed error, not a challenge. Other items keep
+            // whatever the seed said.
+            if (json.winCondition?.item === item.name) {
+                if (item.weight > OBJECTIVE_MAX_WEIGHT_KG) {
+                    console.warn(`[scene] objective "${item.name}" weighs ${item.weight} kg -- clamped to ${OBJECTIVE_MAX_WEIGHT_KG} so it can be carried.`);
+                    item.weight = OBJECTIVE_MAX_WEIGHT_KG;
+                }
+            }
             itemMap.set(item.name, item);
             // Step 4.5: Distribute Items
             if (itemJson.heldBy) {

package/bundle/typescript/src/commands/game/sideQuest/utilities/room-grid.js

@@ -1,4 +1,11 @@
 import { Direction } from '../types/shared/direction-enum.js';
+export function doorwayKindOf(spotName) {
+    if (/stair|\bsteps?\b|ladder|hatch|shaft|chute|\bramp\b|\blift\b|elevator|escalator/i.test(spotName))
+        return 'vertical';
+    if (/door|entrance|entry|threshold|gate|arch|portal|airlock/i.test(spotName))
+        return 'lateral';
+    return undefined;
+}
 export const METERS_PER_CELL = 2;
 /**
  * How tall one storey is. A CHOICE, not a citation -- SR5 never says how
@@ -609,7 +616,23 @@ export function synthesizeGrid(input) {
     // own walls; the hub sits where all of them are plausibly reachable.
     for (const [spotName, served] of exitCellsBySpot.entries()) {
         if (served.length === 1) {
-            grid.spotCells.set(spotName, served[0]);
+            // FURNITURE BESIDE THE DOOR, NOT IN IT (XanDMPmRrbJQ8ta8e,
+            // 2026-09-12: "the corner booth is right in front of the door
+            // north ... doors and booths should not be on top of each
+            // other"). A seed may name any spot as the one an exit is
+            // reached from -- "the booth by the north door". Only a spot
+            // that IS a doorway (a door, a gate, the stairs) takes the
+            // doorway cell; a booth, a counter or a bar takes the nearest
+            // free cell beside it instead. The doorway and its approach are
+            // already claimed above, so "nearest free" is next to the door,
+            // never on it or in front of it.
+            if (doorwayKindOf(spotName)) {
+                grid.spotCells.set(spotName, served[0]);
+                continue;
+            }
+            const beside = nearestFree(served[0], occupied, dims, exists);
+            claim(beside);
+            grid.spotCells.set(spotName, beside);
             continue;
         }
         const mid = {

package/bundle/typescript/src/commands/game/sideQuest/utilities/spots.js

@@ -2,7 +2,10 @@ import { Direction } from '../types/shared/direction-enum.js';
 import { significantWords, wordsAreCloseEnough } from './fuzzy-match.js';
 import { hint } from './hints.js';
 import { placeName } from './log-style.js';
-import { findPath, distanceMeters, coverBetween, blockingRegionFor, pathClimbSteps, levelFootprint, key, isCellBlocked, pathSqueezes, METERS_PER_CELL, } from './room-grid.js';
+import { findPath, distanceMeters, coverBetween, blockingRegionFor, pathClimbSteps, levelFootprint, key, isCellBlocked, pathSqueezes, METERS_PER_CELL, doorwayKindOf, } from './room-grid.js';
+// The doorway vocabulary moved to room-grid.ts (the grid seats exit
+// spots by it); every caller of spots.ts keeps its import.
+export { doorwayKindOf };
 /**
  * Intra-room locations ("at" spots -- player request: every room felt
  * like everything stood at your elbow; walking into the bar had both
@@ -1283,13 +1286,31 @@ export function lockedRouteHint(room, direction, door) {
     }
     return '';
 }
-export function doorwayKindOf(spotName) {
-    if (/stair|\bsteps?\b|ladder|hatch|shaft|chute|\bramp\b|\blift\b|elevator|escalator/i.test(spotName))
-        return 'vertical';
-    if (/door|entrance|entry|threshold|gate|arch|portal|airlock/i.test(spotName))
-        return 'lateral';
-    return undefined;
-}
+/**
+ * WHAT KIND OF WAY THROUGH a spot's name describes, or undefined when
+ * it isn't a way through at all (a bar, a workbench, the stalls).
+ *
+ * THE ONE DOORWAY PREDICATE (item A, 2026-08-27). There were two
+ * separately-written copies of this regex -- here in entrySpotFor and
+ * in Room.namedDoorwayFor -- free to drift apart, and neither knew the
+ * distinction that actually matters: a "back door" is a LATERAL way
+ * through and a "way down" is a VERTICAL one. Kind-blindness is what
+ * let namedDoorwayFor bind a spot called "the back door" to a DOWN
+ * exit, which put the basement's barrier at the back door (the player's
+ * report) and, because vertical exits are centre-placed, simultaneously
+ * put the back door in the middle of the room (the older report). One
+ * defect, two bug reports.
+ *
+ * This is a PERMANENT component, not a migration shim. Generation is
+ * moving toward binding every exit to a spot explicitly, but that data
+ * is model-written: validation can make it right more often, never
+ * always. And every scene seeded before that lands has nothing but
+ * names, forever. So this is the honest floor under a seed that is
+ * silent or lying, and it is the LAST resort -- an explicit
+ * room.exitSpots binding always wins.
+ *
+ * (Definition now in room-grid.ts -- see the re-export at the top.)
+ */
 /** The kind of way through a given direction NEEDS. */
 export function exitDoorwayKind(direction) {
     return direction === Direction.UP || direction === Direction.DOWN ? 'vertical' : 'lateral';

package/package.json

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