@maka/maka-cli 5.213.0 → 5.215.0

package/bundle/typescript/package.json

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

@@ -150,7 +150,7 @@ export class BacklogCommand extends Command {
         // patch-probe exists to catch. game.ts already imports this module
         // lazily for the same reason (streetTransport).
         const { cliVersion, engineVersion } = await import('../utilities/shared-run.js');
-        const outcome = await submitBacklog(text, {
+        const filed = await submitBacklog(text, {
             runnerName: this.actor?.name,
             // Links the item back to the play session it came out of -- the
             // same id the uploaded logs are keyed by, so an item and its
@@ -177,10 +177,21 @@ export class BacklogCommand extends Command {
             client: currentSession()?.client ?? 'cli',
         });
         // A real call classifies the account for free -- no second request.
-        noteBacklogOutcome(outcome);
-        if (outcome !== 'ok')
-            return this.explain(outcome);
-        return `{cyan-fg}Filed. It'll come back checked against the books.${hint(` ("backlog list" reads the board.)`)}{/cyan-fg}`;
+        noteBacklogOutcome(filed.outcome);
+        if (filed.outcome !== 'ok')
+            return this.explain(filed.outcome);
+        // NAME THE THING YOU JUST FILED (X3tZu4rspsa5CQW38, Maka: 'Let's
+        // change this to read "Logged - <ID>"'). "Filed. It'll come back
+        // checked against the books." told the reporter a report exists
+        // somewhere and gave them no way to refer to it -- and the id was on
+        // the wire the whole time, thrown away by submitBacklog.
+        //
+        // The old sentence is kept for the case where the server answered
+        // 200 with a body we could not read: the item IS filed, and saying
+        // "Logged - undefined" would be worse than saying less.
+        return filed.id
+            ? `{cyan-fg}Logged - ${filed.id}${hint(` ("backlog list" reads the board.)`)}{/cyan-fg}`
+            : `{cyan-fg}Filed. It'll come back checked against the books.${hint(` ("backlog list" reads the board.)`)}{/cyan-fg}`;
     }
     /**
      * THE REVIEW QUEUE (user request 2026-08-27). Bare "backlog review"

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

@@ -1045,5 +1045,63 @@
 //   at the top of execute() has charged for the phase before it knows
 //   whether it has a target, and a verb that bills before delegating has
 //   charged for a refusal it cannot see.
-export const ENGINE_VERSION = '1.73.0';
+// 1.74.0 (2026-09-16): A BEAT IS WHAT THE ROOM CAN SEE AND HEAR
+//   (BDYYpN9EZJtTJ5B6A, Maka: 'I shouldn't "notice" skitter's inner
+//   monolog: "Skitter's eyes narrow--sharp as a razor. The kid just
+//   walked off with product without settling up, and now he's shouting
+//   about it like it's some kinda joke."'). The first sentence is what
+//   a beat is FOR. The second is Skitter's private assessment, printed
+//   to a player with no way to know it -- and a player who reads an
+//   NPC's judgement of them cannot un-know it.
+//   - The brief said only "Any exposition should be in 3rd person",
+//     which constrains grammatical person and says nothing about
+//     observability -- it licensed exactly this. A new bullet draws the
+//     line where it belongs: exposition is what someone standing in the
+//     room could see or hear, never what you know, have worked out,
+//     think of them, or are about to do.
+//   - An INTERIOR rule joins CONTACT, COMPELLED_MOVEMENT and
+//     SELF_LOCATION in narration-limits.ts, because an instruction is
+//     advice and this file is the engine. It catches interiority that
+//     ANNOUNCES itself: a mind named as a place ("in his head", "in her
+//     mind"), a certainty no watcher could have ("knows exactly", "knew
+//     full well"), and silent calculation as an event ("running the
+//     math").
+//   - MEASURED OVER ALL 294 exposition beats the site has stored, not a
+//     sample: five match, all five are the bug, and the newest is from
+//     TODAY ("The file updates itself quietly in his head") -- so this
+//     is live, not historical. Nothing else in the corpus matches.
+//   - THE NARROWNESS IS THE DESIGN. Good beats describe inner life
+//     constantly, from the OUTSIDE: "something behind her eyes does the
+//     arithmetic", "the math of a fixer deciding whether she's being
+//     played", "in a way that says she's heard this sound too many
+//     times". A pattern on "math", "deciding" or a bare "knows" eats
+//     every one of them, and a gate that eats those is worse than the
+//     defect. Those six lines are pinned as must-not-eat tests.
+//   - AND THE HONEST LIMIT, pinned as a test of its own: the reported
+//     sentence carries NO marker. It is free indirect discourse, a
+//     thought with the "he knows" filed off, and no regex can tell it
+//     from a statement of fact. The brief is what aims at that shape;
+//     the rule does not pretend to.
+//   (The author-voice leaks in the same corpus -- "I'll have Deacon Ruy
+//   stay guarded...", "Suspicious system-note injection detected" --
+//   are all dated 2026-08-24 and predate isOutOfCharacter, which
+//   already catches them. Checked, not assumed.)
+// 1.74.1 (2026-09-16): A PERSON MAY SAY WHAT THEY KNOW. 1.74.0's
+//   INTERIOR rule leaked onto the SPEECH channel and gagged ordinary
+//   dialogue -- an NPC saying "I know exactly what you mean" out loud
+//   was refused as mind-reading. Caught before anyone played it, by
+//   reading judgeNarration's other caller rather than by a report.
+//   THE TRAP IS WORTH RECORDING. Dialogue has run through this judge
+//   since KwiMKNMN2e8KBqTY7, and it was safe from the agency rules for
+//   an INVISIBLE reason: that caller passes an empty cast, so there is
+//   no subject to resolve and CONTACT/COMPELLED_MOVEMENT can never fire.
+//   A real guarantee, nowhere stated. INTERIOR needs no subject, so it
+//   walked straight through. judgeNarration now takes an explicit
+//   `channel` ('beat' by default, 'speech' from the dialogue call) and
+//   the beat-only rules are gated on it, so the next rule added here has
+//   to decide which channel it belongs to instead of inheriting an
+//   accident. The distinction is the rule itself: a character may SAY
+//   what they know; they may not have it NARRATED at a player who cannot
+//   hear it.
+export const ENGINE_VERSION = '1.74.1';
 //# sourceMappingURL=engine-version.js.map

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

@@ -2353,6 +2353,7 @@ You are an NPC named ${this.name} in a gritty cyberpunk text adventure game.
 
 - Stay in character. Respond naturally based on your surroundings, personality, and the player’s message.
 - Any exposition should be in 3rd person. Keep exposition to bare minimum.
+- Exposition is ONLY what someone standing in the room could see or hear. Never your own thoughts, judgements, conclusions, or memories -- not what you know, not what you have worked out, not what you think of them, not what you are about to do. Write the OUTSIDE of it: the look, the pause, the hand that stops moving. "His eyes narrow" is yours to write. "He knows the kid never paid" is not, and neither is the same thought with the "he knows" filed off.
 - Do NOT repeat, rephrase, or re-ask anything you have already said (check the recent-activity history below). If you already asked a question and it hasn't been answered, wait for the answer -- do not ask it again in different words.
 - Silence is a valid response: if this event doesn't genuinely need words from you, do not include a say command at all.
 - Keep spoken lines SHORT -- one or two sentences. People don't monologue at strangers.
@@ -2514,6 +2515,13 @@ Your objective is to drive the story line.`}
                 const placeVerdict = judgeNarration(said, this.name, [], {
                     here: this.currentLocation?.name,
                     worldRooms: Object.values(this._scene?.getRooms?.() ?? {}).map(r => r.name),
+                    // SAYS WHICH CHANNEL THIS IS, rather than relying on the empty
+                    // `others` above to keep the beat-only rules from firing. That
+                    // guarantee held for the agency rules, which need a subject to
+                    // resolve -- and broke the moment a rule arrived that does not
+                    // (INTERIOR), refusing an ordinary spoken "I know exactly what
+                    // you mean" as mind-reading. A person may SAY what they know.
+                    channel: 'speech',
                 });
                 if (placeVerdict.refused) {
                     this.logger.write(`${this.name} speech refused (claimed to be elsewhere): ${said.slice(0, 160)}`);

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

@@ -65,24 +65,39 @@ function parseData(raw) {
         return undefined;
     }
 }
+/**
+ * File one, and SAY WHICH ONE (X3tZu4rspsa5CQW38, Maka: 'Let's change
+ * this to read "Logged - <ID>"').
+ *
+ * The id was always on the wire -- the route has answered
+ * `{ id, status, vetting }` since it was written -- and this function
+ * threw it away, returning a bare outcome word. So the only thing the
+ * player who filed a report could say about it afterwards was "I filed
+ * something", which is not enough to look it up, quote it, or ask about
+ * it. Returns the shape its siblings already use.
+ */
 export async function submitBacklog(text, meta) {
     const token = authToken();
     if (!token)
-        return 'no-login';
+        return { outcome: 'no-login' };
     try {
         const res = await request('POST', `/${API_BASE}/item`, token, { text, ...meta });
-        if (res.statusCode === 200)
-            return 'ok';
+        if (res.statusCode === 200) {
+            // An id we cannot read is not a failure to file -- the item IS on
+            // the board. The caller falls back to wording that does not
+            // promise one rather than reporting a filing that worked as broken.
+            return { outcome: 'ok', id: parseData(res.data)?.id };
+        }
         if (res.statusCode === 401)
-            return 'expired';
+            return { outcome: 'expired' };
         if (res.statusCode === 403)
-            return 'forbidden';
+            return { outcome: 'forbidden' };
         if (res.statusCode === 400)
-            return 'rejected';
-        return 'offline';
+            return { outcome: 'rejected' };
+        return { outcome: 'offline' };
     }
     catch {
-        return 'offline';
+        return { outcome: 'offline' };
     }
 }
 /**

package/bundle/typescript/src/commands/game/sideQuest/utilities/narration-limits.js

@@ -121,6 +121,64 @@ const SELF_LOCATION = new RegExp([
     // "I'm standing/sitting/waiting in X".
     String.raw `\bI(?:'|’)?m\s+(?:stand|sitt|wait|post|hang|hold)\w*\s+(?:up\s+|out\s+|around\s+)*(?:at|in|by|outside)\s+(?:the\s+)?([^.,;!?"'’]{2,48})`,
 ].join('|'), 'i');
+/**
+ * READING THE NPC'S MIND (BDYYpN9EZJtTJ5B6A, Maka: 'I shouldn't "notice"
+ * skitter's inner monolog: "Skitter's eyes narrow—sharp as a razor. The
+ * kid just walked off with product without settling up, and now he's
+ * shouting about it like it's some kinda joke."').
+ *
+ * A beat is what a person standing in the room can SEE and HEAR. The
+ * first sentence of that line is exactly that and is good writing. The
+ * second is Skitter's private assessment, printed to a player who has no
+ * way to know it -- and a player who reads an NPC's judgement of them
+ * cannot un-know it, which is half the game gone.
+ *
+ * WHAT THIS CATCHES AND WHAT IT CANNOT. The reported sentence carries no
+ * marker at all: it is free indirect discourse, a thought written as
+ * plain narration, and nothing short of a model could tell it from a
+ * statement of fact. So this rule does NOT claim to catch it -- the
+ * brief in models/npc.ts is what aims at that shape. What is catchable
+ * is interiority that ANNOUNCES itself: a mind named, or a mental act
+ * given as a fact.
+ *
+ * MEASURED, NOT GUESSED, over all 294 exposition beats the site has
+ * stored (GameSessionEvents, channel 'log'). Five lines match and all
+ * five are the bug:
+ *
+ *   "...already sliding out of the booth's shadow in her mind if not
+ *    her body."
+ *   "...that's not natural, and Ilsen knows exactly what it means."
+ *   "...but he's already running the math -- two of them, close
+ *    quarters, his crew somewhere outside earshot."
+ *   "Forty years on the pier means he knows exactly how far a man has
+ *    to be standing before he can lie about why he's here."
+ *   "The file updates itself quietly in his head."
+ *
+ * Nothing else in the corpus matches, and the near misses are the
+ * reason the patterns are this narrow. Good beats constantly describe
+ * inner life FROM THE OUTSIDE -- "something behind her eyes does the
+ * arithmetic", "the math of a fixer deciding whether she's being
+ * played", "like he's reading a bill of sale", "in a way that says
+ * she's heard this sound too many times". Every one of those is an
+ * observer's inference about visible behaviour, which is precisely what
+ * a beat is FOR. A pattern on the word "math" or "deciding" would eat
+ * all of them, so the anchors are the mind itself ("in his head", "in
+ * her mind"), certainty no observer could have ("knows exactly"), and
+ * the one idiom that always means silent calculation ("running the
+ * math").
+ */
+const INTERIOR = new RegExp([
+    // The mind, named as a place something happens. "in his head", "in
+    // her mind", "inside their thoughts". NOT "in the back of the shop".
+    String.raw `\b(?:in|inside|through|across)\s+(?:his|her|their|its)\s+(?:mind|head|thoughts)\b`,
+    // A certainty no watcher could have. "he knows exactly what it
+    // means", "she knows exactly how far". The adverb is load-bearing:
+    // "he knows the code" is a fact about the world a beat may state.
+    String.raw `\b(?:knows|knew)\s+(?:exactly|full\s+well|perfectly\s+well|damn\s+well)\b`,
+    // Silent calculation as an event. "already running the math",
+    // "running the numbers in his head" (caught twice over, harmlessly).
+    String.raw `\brunning\s+the\s+(?:math|numbers|odds)\b`,
+].join('|'), 'i');
 /** Every place a self-location claim names in one line. */
 function placesClaimed(line) {
     const out = [];
@@ -251,6 +309,21 @@ function aimedAtAPerson(text, matches, subject) {
  * @param opts.holding  who this NPC already has a grapple on, if anyone --
  *                 narration about a hold the dice already settled is a
  *                 description, not a claim.
+ * @param opts.channel  which half of the reply this is. 'beat' (the
+ *                 default) is exposition and gets every rule. 'speech'
+ *                 is a line of DIALOGUE and gets the place rule only.
+ *
+ * WHY THE CHANNEL IS A PARAMETER AND NOT AN ACCIDENT. Dialogue has been
+ * passing through here since KwiMKNMN2e8KBqTY7 ("Whisper ... says he
+ * is"), and it survived the agency rules only because its caller passes
+ * an EMPTY `others` -- with nobody to resolve as the subject, CONTACT
+ * and COMPELLED_MOVEMENT can never fire. That is a real guarantee but an
+ * invisible one, and the INTERIOR rule broke it the moment it was
+ * written: interiority needs no subject, so a perfectly ordinary spoken
+ * "I know exactly what you mean" was refused as mind-reading. A person
+ * is allowed to say what they know. They are not allowed to have it
+ * NARRATED at a player who cannot hear it -- which is the whole
+ * distinction, and it now has a name in the signature.
  */
 export function judgeNarration(line, speaker, others, opts = {}) {
     const t = line.replace(/^[\s│|>*-]+/, '').trim();
@@ -268,6 +341,16 @@ export function judgeNarration(line, speaker, others, opts = {}) {
             };
         }
     }
+    // ALSO BEFORE the agency rules, and for the same reason: this is about
+    // the SPEAKER's own head, so there is no subject to resolve -- which
+    // is exactly why it must be told to stay off the speech channel.
+    if (opts.channel !== 'speech' && INTERIOR.test(t)) {
+        return {
+            refused: true,
+            subject: speaker,
+            note: `A BEAT IS WHAT THE ROOM CAN SEE AND HEAR. Your last beat read your own mind out loud -- what you know, what you are working out, what is going on in your head -- so it did not happen and the player was not shown it. Nobody standing in front of you can see any of that. Write the OUTSIDE of it instead: the look, the pause, the hand that stops moving, the glance at the door. A player who watches you narrow your eyes and go quiet learns more than one who is handed your conclusion.`,
+        };
+    }
     const contactAt = t.match(CONTACT);
     const movedAt = t.match(COMPELLED_MOVEMENT);
     if (!contactAt && !movedAt)

package/package.json

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