@maka/maka-cli 5.221.0 → 5.223.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.221.0",
+  "version": "5.223.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/jack.js

@@ -150,22 +150,49 @@ export class JackCommand extends Command {
             // price is paid on the other side: every point of Matrix damage
             // lands on their REAL stun track (see combat-exchange routing).
             if (!actor.isTechnomancer()) {
-                const deck = actor.getCyberdeck();
-                if (!deck) {
+                // A COMMLINK IS A WAY ONTO THE MATRIX (9d9kJJW3WANoA2MvA, Maka:
+                // "check the rules on page 222 -- anyone with a commlink should
+                // be able to enter the matrix"). He is right and the line he
+                // quoted -- "No cyberdeck, no Matrix" -- was flatly wrong.
+                // p.221: "the majority of people interact with the Matrix in
+                // augmented reality, using their commlink", and p.222 gives a
+                // commlink user their own Matrix attributes and their own five
+                // actions. The Matrix is where everyone already lives.
+                //
+                // WHAT A DECK ACTUALLY BUYS is the hacking half, and the model
+                // already said so without anyone having to write a rule here:
+                // Item.matrixAttribute gives a non-deck device Data Processing
+                // and Firewall equal to its rating and ATTACK AND SLEAZE OF
+                // ZERO -- exactly p.222's "both of these attributes are equal to
+                // your commlink's rating", and exactly p.221's reason ("unlike a
+                // cyberdeck it has no space for cyberprograms or other hacking
+                // tools"). So a commlink persona can ride the grid, look, talk
+                // and carry files, and cannot hack. The refusal for that lives
+                // where the hacking happens (Player.deckOnlyRefusal), not here.
+                const rig = actor.getCyberdeck() ?? actor.getPanMaster();
+                if (!rig) {
                     const bricked = actor.getAnyCyberdeck();
                     return bricked
                         ? `Your ${bricked.name} is BRICKED (${bricked.deckSummary()}) -- dead boards don't jack in. Rest somewhere safe to repair it.`
-                        : `No cyberdeck, no Matrix. A commlink gets you calls and AR -- riding the grid takes a real deck.`;
-                }
-                if (actor.runningSilent) {
-                    return `You're running silent -- no broadcast, no Matrix. Go loud first ("silent").`;
+                        : `Nothing to jack in ON. A commlink or a cyberdeck puts you on the grid (p.222) -- you are carrying neither.`;
                 }
+                // RUNNING SILENT IS A MATRIX STATE, NOT A DOOR (oJELzTwkTJE63bvXr,
+                // Maka: "I should be able to jack in, even running silent"). The
+                // refusal here had it exactly backwards. p.235-236: "you can
+                // switch your commlink, deck, other device, or persona ... to
+                // silent running" -- it is a mode you run WHILE on the Matrix,
+                // and going quiet is the first thing a runner does on the way
+                // in, not a reason to be kept out. The cost is already modelled
+                // where canon puts it: -2 on every Matrix action
+                // (Player.matrixActionPenalty), and an icon nobody can see
+                // without beating you in an opposed test (silent-icons.ts).
+                //
                 // VR NEEDS A DIRECT NEURAL INTERFACE (p.222-223): a datajack or
-                // a trode net. The deck's own screen still gives you AR -- calls,
+                // a trode net. The rig's own screen still gives you AR -- calls,
                 // the overlay, the sheet -- but riding the grid means plugging
                 // your nervous system in. Names the two cures and their prices.
                 if (!actor.hasDirectNeuralInterface()) {
-                    return `Jacking in is VR, and VR needs a direct neural interface -- a trode net (70 nuyen on any electronics shelf) or a datajack at the clinic. Without one your ${deck.name} is AR only.`;
+                    return `Jacking in is VR, and VR needs a direct neural interface -- a trode net (70 nuyen on any electronics shelf) or a datajack at the clinic. Without one your ${rig.name} is AR only.`;
                 }
             }
             let mode = (sub === 'hot' || args[1]?.toLowerCase() === 'hot') ? 'hot' : 'cold';

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

@@ -1279,5 +1279,51 @@
 //   it DOES (p.235-236, already charged to players through
 //   matrixActionPenalty) rather than added to its hide roll. Spending it
 //   twice would be a house rule wearing a citation.
-export const ENGINE_VERSION = '1.80.0';
+// 1.80.1 (2026-09-16): the camera-hide fix in 5.222.0 -- a camera hides
+//   behind its OWN rating, not its master host's. Recorded here late and
+//   deliberately: that commit said "engine 1.80.1" in its subject and did
+//   not move this constant, so 5.222.0 shipped reporting 1.80.0. The fix
+//   itself is in utilities/silent-icons.ts with its reasoning; this entry
+//   exists so the changelog does not have a hole where a version was
+//   announced. p.233's slaving rule is about DEFENDING AN ATTACK, not
+//   hiding, and borrowing the host's rating made a camera on a rating-8
+//   host unfindable -- measured at zero finds in twelve looks.
+// 1.81.0 (2026-09-16): A COMMLINK IS A WAY ONTO THE MATRIX, AND SILENCE
+//   IS NOT A LOCKED DOOR. Two reports, two refusals, seven lines apart in
+//   the same guard, both wrong.
+//   - 9d9kJJW3WANoA2MvA (Maka): "check the rules on page 222 -- anyone
+//     with a commlink should be able to enter the matrix". The line he
+//     quoted, "No cyberdeck, no Matrix. A commlink gets you calls and AR
+//     -- riding the grid takes a real deck", was flatly wrong. p.221:
+//     "the majority of people interact with the Matrix in augmented
+//     reality, using their commlink." p.222 gives a commlink user their
+//     own Matrix attributes and their own five actions.
+//   - oJELzTwkTJE63bvXr (Maka): "I should be able to jack in, even
+//     running silent". Backwards. p.235-236: "you can switch your
+//     commlink, deck, other device, or persona ... to silent running" --
+//     a mode you run WHILE on the Matrix, and the first thing a runner
+//     does on the way in. The cost is already modelled where canon puts
+//     it: -2 on every Matrix action, and an icon nobody sees without
+//     beating you in an opposed test (1.80.0).
+//   WHAT A DECK ACTUALLY BUYS is the hacking half, and the item model
+//   already said so without anyone writing a rule: a non-deck device has
+//   Data Processing and Firewall equal to its rating and ATTACK AND
+//   SLEAZE OF ZERO -- p.222's "both of these attributes are equal to your
+//   commlink's rating", p.221's "no space for cyberprograms or other
+//   hacking tools". So a commlink persona rides the grid, looks, talks
+//   and carries data, and cannot crack an icon.
+//   AND THAT HALF IS LOAD-BEARING, not a nicety. Attack 0 does not fail
+//   safe: a limit of 0 is NOT a cap of zero hits in rollPool, it is no
+//   cap at all (`limit > 0` is what makes a cap a cap). Opening the door
+//   without closing the hacking half would not have made a commlink user
+//   bad at hacking -- it would have made them roll UNLIMITED and out-hit
+//   the decker beside them. burnedAttributeRefusal answers for the
+//   no-gear case too now (deckOnlyRefusal), naming the gear instead of
+//   blaming an IC that was never there, and never sending somebody to
+//   reboot a deck they do not own.
+//   SEVEN TEST FIXTURES WERE HACKING WITH NO DECK, which is how long that
+//   hole had been open: they leaned on the old "no gear, stay quiet"
+//   branch and have been rolling unlimited all along. They carry decks
+//   now. The VR gate (a direct neural interface, p.222-223) is untouched.
+export const ENGINE_VERSION = '1.81.0';
 //# sourceMappingURL=engine-version.js.map

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

@@ -858,10 +858,48 @@ export class Player extends AbstractPlayer {
     burnedAttributeRefusal(kind) {
         if (this.matrixAttribute(kind) > 0)
             return undefined;
+        // NO GEAR IS ITS OWN REFUSAL, and it used to be nobody's
+        // (9d9kJJW3WANoA2MvA). This returned undefined here on the grounds
+        // that "its callers already gate on the gear" -- and the gate they
+        // meant was jack-in's "No cyberdeck, no Matrix", which was itself
+        // the canon violation being fixed. Once a commlink can reach the
+        // grid (p.222), a persona with Attack 0 and Sleaze 0 is an ordinary
+        // thing to be, and the hacking verbs had nothing left standing
+        // between them and a roll.
+        //
+        // THE FAILURE MODE IS WORSE THAN IT LOOKS, which is why it is
+        // refused rather than left to the dice: a limit of 0 is not a limit
+        // of zero hits in rollPool, it is NO LIMIT (`limit > 0` is what
+        // makes a cap a cap). So a commlink user who reached a hacking roll
+        // would not fail -- they would roll UNLIMITED, out-hitting the
+        // decker standing next to them.
         if (this.baseMatrixAttribute(kind) <= 0)
-            return undefined; // no gear, not a burn
+            return this.deckOnlyRefusal(kind);
         return `${Player.ATTR_EATER[kind]} ate your ${Player.ATTR_NAME[kind]} -- there is nothing left to work with. It comes back when you reboot ("jack out", then jack back in).`;
     }
+    /**
+     * WHY A COMMLINK CANNOT DO THIS, in the book's own terms.
+     *
+     * p.221: a commlink "has all of the necessary software already loaded,
+     * but unlike a cyberdeck it has no space for cyberprograms or other
+     * hacking tools." p.222 gives it Data Processing and Firewall equal to
+     * its rating and names no Attack or Sleaze at all. That is not an
+     * oversight in the engine's item model -- it is the whole difference
+     * between riding the Matrix and hacking it.
+     *
+     * Data Processing and Firewall can never be 0 on a working rig, so in
+     * practice this only ever answers for attack and sleaze; the other two
+     * are handled so the method cannot lie if a future device rates 0.
+     */
+    deckOnlyRefusal(kind) {
+        if (kind !== 'attack' && kind !== 'sleaze')
+            return undefined;
+        const rig = this.activeDeck ?? this.getCyberdeck() ?? this.getPanMaster();
+        const what = kind === 'attack' ? 'Attack' : 'Sleaze';
+        return rig
+            ? `Your ${rig.name} has no ${what} rating -- it is a commlink, not a cyberdeck, and "no space for cyberprograms or other hacking tools" (p.221). You are ON the grid and you can look, talk and carry data; cracking an icon takes a deck.`
+            : `Nothing you are carrying has an ${what} rating -- that takes a cyberdeck (p.221).`;
+    }
     /** Which IC eats which attribute (p.248), for naming the culprit. */
     static ATTR_EATER = {
         attack: 'Jammer IC', sleaze: 'Marker IC',

package/bundle/typescript/src/commands/game/sideQuest/utilities/silent-icons.js

@@ -1,6 +1,6 @@
 import { rollPool, formatRoll } from './dice.js';
 import { deviceDefensePool } from './matrix-intrusion.js';
-import { isWatched, cameraMasterHost } from './surveillance.js';
+import { isWatched } from './surveillance.js';
 import { DEFAULT_DEVICE_RATING } from '../models/device.js';
 function hiddenDevice(device) {
     return {
@@ -34,17 +34,25 @@ export function hiddenIconsIn(scene, room, viewer) {
         .map(hiddenDevice);
     // THE CAMERAS, which p.217 names FIRST. They are not a Device -- the
     // cluster is derived from the room (surveillance.ts isWatched) -- so
-    // they hide on the room's own set and resist with their master host's
-    // rating where there is one: a site's lenses are as quiet as the
-    // security that runs them, and a slave borrows its master's numbers
-    // (p.233). Without a host they fall back to the door-lock rating
-    // canon prices ordinary fixtures at (p.356).
+    // they hide on the room's own set, and they hide behind their OWN
+    // rating: an ordinary fixture, which canon prices at 2 (p.356).
+    //
+    // THE FIRST CUT GAVE THEM THEIR MASTER HOST'S RATING and that was
+    // wrong twice over. Canon first: p.233's slaving rule is about what a
+    // slave DEFENDS AN ATTACK with -- "whenever a slaved device is called
+    // on to make a defense test" -- and hiding is not an attack being
+    // defended. Borrowing the host's numbers here was an extrapolation
+    // with nothing under it, which is exactly what this project's rule
+    // against inventing canon is for. And then arithmetic: a rating-8
+    // host gave its lenses 16 dice against a sweep the Data Processing
+    // limit caps near 5, so a camera on any corporate host was not hard
+    // to find, it was impossible. Measured before shipping the fix --
+    // zero finds in twelve looks.
     if (isWatched(room) && !room.camerasSpottedBy.has(viewer.name)) {
-        const master = scene ? cameraMasterHost(scene.getRooms(), room) : undefined;
-        const rating = master?.hostRating ?? DEFAULT_DEVICE_RATING.lock ?? 2;
+        const rating = DEFAULT_DEVICE_RATING.lock ?? 2;
         out.push({
             name: 'Camera cluster',
-            hide: { pool: Math.max(0, rating * 2), label: master ? 'its host\'s rating' : 'Device Rating' },
+            hide: { pool: Math.max(0, rating * 2), label: 'Device Rating' },
             reveal: (v) => { room.camerasSpottedBy.add(v); },
         });
     }

package/package.json

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