@maka/maka-cli 5.224.0 → 5.225.0

package/bundle/typescript/package.json

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

@@ -1,5 +1,7 @@
 import { Direction } from '../types/shared/direction-enum.js';
 import { ARCHETYPES, getArchetype } from '../archetypes.js';
+import { catalogGearDef } from '../utilities/catalog.js';
+import { Category, Size, Rating } from '../types/shared/item-enum.js';
 /**
  * BUILDING THE BENCH A REVIEW ITEM SHIPS WITH.
  *
@@ -97,6 +99,43 @@ const ARMED_NPC_KIT = [
     { name: 'Ares Predator V', description: 'A heavy pistol, smartlinked and chattering to its owner over the wireless.', size: 'Small', category: 'RangedWeapon', shape: 'Pistol', color: 'Black', texture: 'Matte', rating: 'Standard', weight: 2 },
     { name: 'Meta Link', description: 'A cheap commlink. It is what puts everything else on the grid.', size: 'Tiny', category: 'Commlink', shape: 'Rectangle', color: 'Gray', texture: 'Plastic', rating: 'Common', weight: 0.1 },
 ];
+/**
+ * THE SEED ROW FOR A REAL PIECE OF GEAR (items[].gear).
+ *
+ * catalogGearDef answers in enum VALUES ('cyberdeck'); a seed carries
+ * enum KEYS, because ItemFactory does `Category[json.category]`. So the
+ * values are mapped back to their keys here rather than anywhere that
+ * would have to know both shapes.
+ *
+ * A NAME THAT RESOLVES TO NOTHING THROWS. It would be easy to fall back
+ * to a Document and let the bench build -- and that is exactly the bug
+ * pFNBSzb95JHCHSJjE was: a key item whose name had drifted one word
+ * failed silently and left a door nobody could open. A fixture that
+ * quietly ships the wrong object is worse than one that refuses.
+ */
+function catalogSeedFor(name) {
+    const def = catalogGearDef(name);
+    if (!def) {
+        throw new ReproFixtureError(`items[].gear is set for "${name}", but the catalog has no such row. `
+            + `Spell it the way the catalog does, or drop "gear" to make it an ordinary prop.`);
+    }
+    const keyOf = (e, v) => Object.keys(e).find(k => e[k] === v) ?? 'Document';
+    return {
+        category: keyOf(Category, def.category),
+        size: keyOf(Size, def.size),
+        rating: keyOf(Rating, def.rating),
+        shape: def.shape,
+        color: def.color,
+        texture: def.texture,
+        weight: def.weight,
+        // A DECK WITH NO CONFIG IS A DECK WITH A ZEROED ARRAY, which reads
+        // as a bricked one at every roll site. The book lets the owner order
+        // the four attributes (p.227); a bench has nobody to ask, so it gets
+        // the identity order and says so here rather than leaving a fixture
+        // author to discover it from a mechanics line.
+        ...(def.category === Category.Cyberdeck ? { deckOrder: [0, 1, 2, 3] } : {}),
+    };
+}
 /** A fixture that cannot be built into an honest bench. Thrown, never
  *  swallowed -- the caller turns it into a sentence for whoever wrote
  *  the spec. */
@@ -465,13 +504,23 @@ export function buildReproScene(fixture) {
         name: it.name,
         description: it.description,
         details: it.details,
-        size: 'Tiny',
-        category: 'Document',
-        shape: 'Rectangle',
-        color: 'Gray',
-        texture: 'Plain',
-        rating: 'Common',
-        weight: 0.1,
+        // REAL GEAR WHEN THE FIXTURE ASKS FOR IT (items[].gear). Everything
+        // here used to be a Document whatever it was called, which works for
+        // the props a fixture is mostly made of and breaks the moment the
+        // engine recognises something by CATEGORY rather than by name -- a
+        // "Fairlight Excalibur" that isCyberdeck() called a sheet of paper.
+        // The catalog is the engine's own answer for what a named piece of
+        // gear IS (chargen builds every runner's kit from these rows), so
+        // this asks it rather than inventing a second source.
+        ...(it.gear ? catalogSeedFor(it.name) : {
+            size: 'Tiny',
+            category: 'Document',
+            shape: 'Rectangle',
+            color: 'Gray',
+            texture: 'Plain',
+            rating: 'Common',
+            weight: 0.1,
+        }),
         // A FILE rides the host's room on the matrix plane and takes no
         // spot -- a spot is a meat position (see the ice rule above).
         ...(it.file

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

@@ -24,10 +24,18 @@
  * 2.4.0 adds IReproNpc.astral -- purely additive, older drafts still
  * valid.
  *
+ * 2.8.0 adds IReproItem.gear -- resolve the name against the CATALOG
+ *       and build the real thing. Purely additive: an item without it is
+ *       the same Document prop it always was, so every existing draft
+ *       stays valid. It exists because a fixture could not express a
+ *       CYBERDECK at all (isCyberdeck reads the category, which was
+ *       hard-coded to Document), which made a whole class of bench
+ *       unbuildable -- see factories/repro-gear.test.ts.
+ *
  * 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.7.0';
+export const REPRO_SCHEMA_VERSION = '2.8.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.224.0",
+  "version": "5.225.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.",