@maka/maka-cli 5.66.0 → 5.67.0

package/bundle/typescript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.66.0",
+  "version": "5.67.0",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 2.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 2.x applications using React.",

package/bundle/typescript/src/commands/game/_index.d.ts

@@ -3,3 +3,4 @@ import './pong.sub.cmd.js';
 import './snake.sub.cmd.js';
 import './battleship.sub.cmd.js';
 import './sideQuest.sub.cmd.js';
+import './sideQuest-backlog.sub.cmd.js';

package/bundle/typescript/src/commands/game/_index.js

@@ -3,5 +3,6 @@ import './pong.sub.cmd.js';
 import './snake.sub.cmd.js';
 import './battleship.sub.cmd.js';
 import './sideQuest.sub.cmd.js';
+import './sideQuest-backlog.sub.cmd.js';
 //import './tetris.sub.cmd.js';
 //# sourceMappingURL=_index.js.map

package/bundle/typescript/src/commands/game/_index.js.map

@@ -1 +1 @@
-{"version":3,"file":"_index.js","sourceRoot":"","sources":["../../../../../src/commands/game/_index.ts"],"names":[],"mappings":"AAAA,OAAO,mBAAmB,CAAC;AAC3B,OAAO,mBAAmB,CAAC;AAC3B,OAAO,oBAAoB,CAAC;AAC5B,OAAO,yBAAyB,CAAC;AACjC,OAAO,wBAAwB,CAAC;AAChC,+BAA+B"}
+{"version":3,"file":"_index.js","sourceRoot":"","sources":["../../../../../src/commands/game/_index.ts"],"names":[],"mappings":"AAAA,OAAO,mBAAmB,CAAC;AAC3B,OAAO,mBAAmB,CAAC;AAC3B,OAAO,oBAAoB,CAAC;AAC5B,OAAO,yBAAyB,CAAC;AACjC,OAAO,wBAAwB,CAAC;AAChC,OAAO,gCAAgC,CAAC;AACxC,+BAA+B"}

package/bundle/typescript/src/commands/game/sideQuest/commands/backlog.d.ts

@@ -76,9 +76,112 @@ export declare class BacklogCommand extends Command implements ICommand {
      * are being asked for.
      */
     private renderItem;
+    /**
+     * ANSWERING THE ITEM THIS SESSION IS ABOUT -- no index, because there
+     * is only one thing it could mean.
+     *
+     *   backlog review reject <what is still wrong>
+     *   backlog review accept [what you saw]
+     *   backlog review <what you saw>          (accept, said plainly)
+     *   backlog review repro                   (re-read the steps)
+     *
+     * `accept` is spelled out as a keyword AND left optional, which looks
+     * redundant and is not. Bare prose has always signed an item off, and
+     * removing that would break the habit of everyone already using it --
+     * but a person who has just typed "reject <reason>" reasonably
+     * expects "accept <reason>" to exist, and finding that it does not is
+     * how somebody ends up typing "accept" alone as their whole
+     * confirmation note.
+     */
+    private answerBound;
+    /**
+     * A BENCH IS DONE WHEN THE ITEM IS ANSWERED (player request
+     * 2026-08-28: "after accepting or rejecting, give a 3s timeout and
+     * then close the session").
+     *
+     * It exists to answer one report; once that is posted there is
+     * nothing left in it. Three seconds so the confirmation above can
+     * actually be read -- closing on the same frame would wipe the only
+     * evidence the answer went anywhere.
+     *
+     * ONLY in a bench, and only after a post that SUCCEEDED. Answering
+     * from an ordinary session must never shut the game down: that is
+     * somebody's run, not a scratch scene, and the failure would be
+     * spectacular.
+     */
+    /**
+     * ASK THE LAUNCHER FOR THE BENCH, then leave so it can run it.
+     *
+     * Returns the line to print, or undefined when this session cannot
+     * hand off -- in which case the caller falls back to simply showing
+     * the steps, which is strictly better than an error.
+     *
+     * REFUSED DURING A SHARED RUN, and this is the guard that matters:
+     * quitting to a bench would drop the table and take everyone else's
+     * evening with it. The refusal names the route that IS safe from
+     * anywhere, because a refusal that does not is just a wall.
+     */
+    private requestBenchHandoff;
+    private closeBench;
+    /**
+     * THE BENCH FOR ONE ITEM.
+     *
+     * Wired as far as it currently goes, and no further: the repro spec
+     * lives on the board (server work, not yet deployed), so today this
+     * can only report honestly that there is nothing attached. What it
+     * must NEVER do is fall through to the sign-off, which is the whole
+     * reason it exists this early.
+     */
+    private repro;
+    /**
+     * ONE ROW OF THE BOARD, in full.
+     *
+     * Resolved against the snapshot that was PRINTED, never a fresh
+     * fetch -- the same invariant the review queue holds, and for the
+     * same reason: a list that reshuffles between being read and being
+     * numbered at hands the player a different item than the one they
+     * counted. With no snapshot it shows the board rather than guessing
+     * which list they had in mind.
+     */
+    private readBoardItem;
+    /**
+     * PLAY ANY BOARD ITEM'S BENCH, not just one awaiting review.
+     *
+     * The review queue holds only what is waiting on YOU, so once an item
+     * is answered its bench became unreachable from in-game -- even
+     * though checking a fix a second time, or showing somebody what you
+     * saw, are ordinary things to want. The board is the wider set and
+     * this is its verb.
+     */
+    private reproFromBoard;
+    /**
+     * CLOSE A BOARD ROW OUTRIGHT -- no verdict, no evidence, no sign-off.
+     *
+     * "backlog close <n> [why]". For an item that should never have been
+     * filed: a duplicate, a mis-typed command that became a report, or
+     * something you have since decided was never real.
+     *
+     * Deliberately NOT one of the review verbs. Accepting a mistake would
+     * record a confirmation nobody made; rejecting it would send
+     * imaginary work back to whoever fixed it. This says the third thing.
+     */
+    private closeFromBoard;
     private list;
     /** One item: what it says, where it stands, and what the books said. */
     private row;
+    /** Blessed's ink for a shared tone. Gray is deliberately absent: it
+     *  reads as absent on this screen (playtest ruling), so 'dim' lands on
+     *  plain white -- unemphatic without being unreadable. */
+    private paint;
+    /** The label and its loudness both come from utilities/backlog-vocab,
+     *  which the out-of-game dump reads too -- one place decides what a
+     *  status is CALLED and how much it matters, and each surface maps
+     *  that to its own palette.
+     *
+     *  An in-review row now paints MAGENTA rather than the same cyan as
+     *  in-progress. It is the one status that is waiting on the reader,
+     *  and it did not look like it -- the same complaint, in a smaller
+     *  font, as the board being unreadable out of game. */
     private statusMark;
     /** The verdict is about the GAME, not the rulebooks (reframed
      *  2026-08-27). Asking canon whether a stale map mattered graded every