@maka/maka-cli 5.216.0 → 5.217.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.216.0",
+  "version": "5.217.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/engine-version.js

@@ -1138,5 +1138,30 @@
 //     because that is what narrowing means. One candidate is not a
 //     cycle -- a key that rewrites the box to what it already holds
 //     looks broken.
-export const ENGINE_VERSION = '1.75.0';
+// 1.76.0 (2026-09-16): THE WAN IS DRAWN AS A TREE (RXBaewsjGDZqqW8ba,
+//   Maka: "the heiarchy is confusing when using 'look' in the matrix.
+//   What 'host' does camera cluster attach to? it says 'live, feeding
+//   the site's host'. If we're allowed to know which host it's attached
+//   to, then let's make this a 'tree' view"). The list was flat: a host
+//   in one section, the devices hanging off it in another, nothing
+//   joining them, and the only clue a phrase that named no host. The
+//   structure was in the model all along and only the rendering hid it.
+//   - HOSTS OVERHEAD now indents a host's slaves beneath it with box
+//     drawing, and ICONS IN REACH holds only what answers to nobody.
+//   - The camera line NAMES its master, from the same cameraMasterHost
+//     tap.ts uses to decide what is on the other end of the cable.
+//   - WHAT COUNTS AS A SLAVE is p.233's rule, not "everything nearby":
+//     "the slaves must be devices and the master must be a host". So the
+//     room's devices and its camera cluster branch off the host; a
+//     person's commlink is THEIR PAN and a persona is nobody's slave,
+//     and both stay at top level.
+//   - "IF WE'RE ALLOWED TO KNOW" IS THE REPORTER'S OWN CONDITIONAL, and
+//     it was RAG-checked rather than assumed. Matrix Perception does NOT
+//     list a device's master among what a hit buys you (p.235), so this
+//     must not become a way to learn one -- and it is not. The engine
+//     already disclosed that these icons answered to "the site's host",
+//     and a room with a node has exactly one; the tree says the same
+//     thing in a shape that can be read. A watched room with NO node
+//     still names no master, pinned as a test.
+export const ENGINE_VERSION = '1.76.0';
 //# sourceMappingURL=engine-version.js.map

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

@@ -4,7 +4,7 @@ import { hostsInReach, hostLine, roomsInReach, gridVicinity } from './grid-reach
 import { NPC } from '../models/npc.js';
 import { hostLabel, hostPurposeFor } from './grid-names.js';
 import { isLinked } from './comm-style.js';
-import { isWatched, camerasLive, canSnoopFeeds } from './surveillance.js';
+import { isWatched, camerasLive, canSnoopFeeds, cameraMasterHost } from './surveillance.js';
 /**
  * The grid's icon inventory for one room -- everything a persona can
  * ACT on, each with its verb (player rulings 2026-08-23/24: "it's hard
@@ -277,7 +277,16 @@ export function gridIcons(scene, actor, room) {
             // catch is that a persona cannot hold a cable -- so this reads as
             // something your BODY could do, which is the price the rule
             // charges. See commands/tap.ts.
-            icons.push(`◎ Camera cluster -- live, feeding the site's host. Loud acts here travel. (own the host to loop them -- or walk in and "tap" a lens in the flesh: slaved to the host means a key to the host)`);
+            // NAME THE MASTER (RXBaewsjGDZqqW8ba, Maka: "What 'host' does
+            // camera cluster attach to? it says 'live, feeding the site's
+            // host'"). Nothing new is disclosed -- the line already said these
+            // lenses answer to a host, and cameraMasterHost is the same
+            // function tap.ts uses to decide what is on the other end of the
+            // cable. It simply refused to say WHICH, in a district that has
+            // exactly one, so the reader was left to guess at a fact the
+            // engine had already handed them.
+            const owner = cameraMasterHost(scene.getRooms(), room);
+            icons.push(`◎ Camera cluster -- live, feeding ${owner ? hostLabel(owner) : `the site's host`}. Loud acts here travel. (own the host to loop them -- or walk in and "tap" a lens in the flesh: slaved to the host means a key to the host)`);
         }
     }
     // THE DIVIDER (eJANPpm7qCaCAJBJw). Only when there is a host to be
@@ -562,9 +571,6 @@ export function gridIconBlock(scene, actor, room, rooms) {
     }
     const out = [];
     const hosts = hostsInReach(rooms, actor);
-    out.push(hosts.length > 0
-        ? `{light-blue-fg}HOSTS OVERHEAD:{/light-blue-fg}\n${hosts.map(h => `  {light-blue-fg}${hostLine(h, actor)}{/light-blue-fg}`).join('\n')}`
-        : `{light-blue-fg}Nothing overhead -- no host stands over this district.{/light-blue-fg}`);
     // THE DIVIDER DIVIDES NOTHING HERE. gridIcons puts the host's own icon
     // first and splices a "-- and NEAR it ... --" heading after it; this
     // block then pulls the host line OUT (it has its own HOSTS OVERHEAD
@@ -577,9 +583,51 @@ export function gridIconBlock(scene, actor, room, rooms) {
     const near = gridIcons(scene, actor, gridVicinity(actor))
         .filter(i => !isHostLine(i))
         .filter((i, idx) => !(idx === 0 && isNearDivider(i)));
-    out.push(near.length > 0
-        ? `{light-blue-fg}ICONS IN REACH:{/light-blue-fg}\n${near.map(i => `  {light-blue-fg}${i}{/light-blue-fg}`).join('\n')}`
-        : `{light-blue-fg}Nothing near -- background noise around your signal.{/light-blue-fg}`);
+    // THE WAN IS DRAWN AS A TREE (RXBaewsjGDZqqW8ba, Maka: "the heiarchy
+    // is confusing when using 'look' in the matrix. What 'host' does
+    // camera cluster attach to? ... let's make this a 'tree' view").
+    //
+    // The list was flat, so a host and the devices hanging off it sat in
+    // two separate sections with nothing joining them, and the only clue
+    // was the phrase "the site's host" -- which names no host. The
+    // structure was in the model the whole time and only the rendering
+    // hid it.
+    //
+    // WHAT IS ACTUALLY SLAVED, and the line is not "everything nearby":
+    // a WAN's slaves are DEVICES (p.233 -- "the slaves must be devices and
+    // the master must be a host"), which here means the room's own
+    // devices and its camera cluster. A person's commlink is their PAN,
+    // not the host's, and a persona is nobody's slave; those stay at top
+    // level where they belong.
+    //
+    // AND NOTHING NEW IS DISCLOSED. Checked against the books rather than
+    // assumed: Matrix Perception does NOT list a device's master among
+    // what a hit buys you (p.235), so this must not become a way to learn
+    // one. It doesn't -- the engine already told you these icons answered
+    // to "the site's host", and a room with a node has exactly one. The
+    // tree says the same thing in a shape that can be read; it does not
+    // reach for a relationship the player did not already have.
+    const hereRoom = gridVicinity(actor);
+    const master = hosts.find(h => h === hereRoom);
+    const isSlave = (i) => i.startsWith('▤') || i.startsWith('◎');
+    const slaved = master ? near.filter(isSlave) : [];
+    const loose = master ? near.filter(i => !isSlave(i)) : near;
+    out.push(hosts.length > 0
+        ? `{light-blue-fg}HOSTS OVERHEAD:{/light-blue-fg}\n${hosts.map(h => {
+            const line = `  {light-blue-fg}${hostLine(h, actor)}{/light-blue-fg}`;
+            if (h !== master || slaved.length === 0)
+                return line;
+            // Box-drawing, so the last child closes the branch and the eye can
+            // see where the WAN ends.
+            const kids = slaved.map((i, idx) => `  {light-blue-fg}${idx === slaved.length - 1 ? '└─' : '├─'} ${i}{/light-blue-fg}`);
+            return [line, ...kids].join('\n');
+        }).join('\n')}`
+        : `{light-blue-fg}Nothing overhead -- no host stands over this district.{/light-blue-fg}`);
+    out.push(loose.length > 0
+        ? `{light-blue-fg}ICONS IN REACH${slaved.length > 0 ? ' -- answering to nobody up there' : ''}:{/light-blue-fg}\n${loose.map(i => `  {light-blue-fg}${i}{/light-blue-fg}`).join('\n')}`
+        : slaved.length > 0
+            ? `{light-blue-fg}Nothing else near -- everything around you hangs off the host.{/light-blue-fg}`
+            : `{light-blue-fg}Nothing near -- background noise around your signal.{/light-blue-fg}`);
     // FARTHER OUT, WITHOUT AN ADDRESS (SR5 p.235, p.243): Matrix Perception
     // never tells you where a device physically sits -- that is Trace Icon,
     // two marks and an opposed test. So far icons are listed by the noise

package/package.json

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