@maka/maka-cli 5.206.0 → 5.207.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.206.0",
+  "version": "5.207.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/factories/repro-scene.js

@@ -39,6 +39,10 @@ export const REPRO_FAR_ROOM = 'The Far Side';
  *  Both rooms have it: a doorway has two sides, and a guard posted on
  *  the far side stands in their own. */
 export const REPRO_DOORWAY_SPOT = 'doorway';
+/** What locks a `barrier.plainDoor` that names no keyItem of its own.
+ *  A door with no key and no mechanism would simply stand open, which
+ *  is the opposite of the fixture the author asked for. */
+export const REPRO_PLAIN_DOOR_KEY = 'Door Key';
 /**
  * Somewhere to stand that is NOT the doorway, so "move to the door" is
  * a real move with a real before-state. Without it the runner starts in
@@ -202,7 +206,18 @@ export function buildReproScene(fixture) {
     const startSide = fixture.start ?? 'barrier';
     const startRoom = roomFor(startSide);
     let device;
-    if (barrier) {
+    // THE LOCK THAT IS IN THE DOOR (Gfx5RFFpHJdKB87Bh). barrier.plainDoor
+    // seals the exit with keyRequired and builds NO device -- the shape
+    // every ordinary locked door in a generated scene has, and the shape
+    // this builder could not make until the report proved it mattered.
+    // `open` still means what it means -- the door simply is not locked --
+    // and it must NOT quietly put the mechanism back, which is the
+    // silently-inert shape this file exists to avoid.
+    const plainDoor = barrier?.plainDoor === true;
+    if (barrier?.plainDoor && !barrier.keyItem && !barrier.open) {
+        warnings.push('A plain door with no keyItem has no quiet way through at all -- force is the only route, which is fine if that is the point.');
+    }
+    if (barrier && !plainDoor) {
         // INVARIANT 1: a code belongs to a panel and nowhere else. The
         // Device constructor DROPS it on a lock or a ward, silently and
         // correctly -- that is the runtime honouring "you can't talk at a
@@ -309,7 +324,13 @@ export function buildReproScene(fixture) {
         name: REPRO_BARRIER_ROOM,
         description: barrier
             ? `A short concrete run ending at one door, ${direction} of you. `
-                + `${device.name} is fixed beside the doorway${barrier.open ? ', standing open' : ', holding it shut'}. `
+                + (plainDoor
+                    // NOTHING BESIDE THE DOOR, and the prose has to say so: the
+                    // whole point of a plainDoor bench is that there is no
+                    // mechanism to work, so describing one would hand the
+                    // reviewer the wrong target to aim every verb at.
+                    ? `No panel, no maglock, no keypad -- just a lock in the door itself, and it is ${barrier.open ? 'off the latch' : 'shut'}. `
+                    : `${device.name} is fixed beside the doorway${barrier.open ? ', standing open' : ', holding it shut'}. `)
                 + `There is nothing else here, which is the point -- whatever is wrong is wrong at that door.`
             : `A short concrete run with a door ${direction} of you and nothing else in it.`,
         // fixture.home: the barrier room is the runner's own bed, so a rest
@@ -319,7 +340,16 @@ export function buildReproScene(fixture) {
         spots,
         levels: level ? [{ name: level.name, side: level.side ?? 'north', kind: level.kind ?? 'catwalk', climbOnly: level.climbOnly === true }] : undefined,
         isStartRoom: startSide === 'barrier',
-        exits: [{ direction, targetRoom: REPRO_FAR_ROOM, atSpot: REPRO_DOORWAY_SPOT }],
+        exits: [{
+                direction,
+                targetRoom: REPRO_FAR_ROOM,
+                atSpot: REPRO_DOORWAY_SPOT,
+                // INVARIANT 3, the deviceless case: with no mechanism to name the
+                // exit, the KEY is what locks the door.
+                ...(plainDoor && !barrier?.open
+                    ? { keyRequired: barrier?.keyItem ?? REPRO_PLAIN_DOOR_KEY }
+                    : {}),
+            }],
         devices: device ? [device] : undefined,
     };
     const farRoom = {
@@ -327,7 +357,7 @@ export function buildReproScene(fixture) {
         ...watchedFields('far'),
         name: REPRO_FAR_ROOM,
         description: `The other side of the door, which lies ${OPPOSITE[direction]} of you`
-            + `${barrier ? ` and is held from the far side by ${device.name}` : ''}. Bare, and no further out.`,
+            + `${barrier && device ? ` and is held from the far side by ${device.name}` : ''}. Bare, and no further out.`,
         roomType: 'Street',
         size: 'medium',
         spots,

package/bundle/typescript/src/commands/game/sideQuest/types/repro.js

@@ -27,7 +27,7 @@
  * 2.5.0 adds IReproHost.purpose / .sculpt and IReproItem.file (engine
  * 1.50.0, hosts with a purpose) -- additive.
  */
-export const REPRO_SCHEMA_VERSION = '2.6.0';
+export const REPRO_SCHEMA_VERSION = '2.7.0';
 /** THE LIVE REASON, from the field or the card's own words.
  *
  *  `repro.live` is authoritative -- but the server's validator must

package/package.json

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