@maka/maka-cli 5.96.0 → 5.99.0

package/bundle/typescript/src/commands/game/sideQuest/types/save-file.d.ts

@@ -13,7 +13,11 @@ import { ISceneSeedJson } from './seed/scene-seed.js';
  * deletion -- an old save outlives the build that can't read it).
  */
 export declare const SAVE_VERSION = 1;
-export type SaveReason = 'homecoming' | 'rest' | 'job-accept' | 'quit' | 'hub-arrival' | 'venue-bust' | 'sin-choice';
+/** Why a save was written. `creation` is the BIRTH CERTIFICATE -- written
+ *  once by the chargen factory before any session exists; its game/hub are
+ *  empty shells that resume must NOT apply as world state (the world boots
+ *  fresh from the embedded hubSeed). Every in-play save uses the others. */
+export type SaveReason = 'creation' | 'homecoming' | 'rest' | 'job-accept' | 'quit' | 'hub-arrival' | 'venue-bust' | 'sin-choice';
 /**
  * A REGISTERED sprite waiting in the Resonance (SR5 p.254-256) -- what
  * it takes to rebuild its shell later. `name` is carried so a sprite

package/bundle/typescript/src/commands/game/sideQuest/utilities/web-character-generator.d.ts

@@ -31,6 +31,18 @@ export declare function buildCharacterGeneratorUrl(resumeToken: string): string;
  *  handoff message can never drift from the verb that actually works
  *  (there is only one thing to play -- user ruling, 2026-08-29). */
 export declare const RELAUNCH_COMMAND = "maka play";
+/**
+ * "sheet web" (user request, 2026-09-01): the same /cli-login handoff as
+ * Forge, but landing on the LIVE character sheet -- /characters, deep-
+ * linked to the character currently being played. Token in the FRAGMENT
+ * for the same reasons as above; `next` carries the deep link. Unlike the
+ * Forge handoff the game KEEPS RUNNING -- this is a glance at the sheet
+ * mid-play, not a goodbye.
+ *
+ * The /characters/<slug> shape is CO-OWNED with the web side (their
+ * character-sheet page) -- do not reshape it here alone.
+ */
+export declare function buildCharacterSheetUrl(resumeToken: string, slug: string): string;
 /**
  * WHAT THE CLI SAYS ON ITS WAY OUT of the chargen handoff. Extracted
  * from the command handler so the two things that matter about it are

package/bundle/typescript/src/commands/game/sideQuest/utilities/web-character-generator.js

@@ -42,6 +42,22 @@ export function buildCharacterGeneratorUrl(resumeToken) {
  *  handoff message can never drift from the verb that actually works
  *  (there is only one thing to play -- user ruling, 2026-08-29). */
 export const RELAUNCH_COMMAND = 'maka play';
+const CHARACTERS_PAGE = '/characters';
+/**
+ * "sheet web" (user request, 2026-09-01): the same /cli-login handoff as
+ * Forge, but landing on the LIVE character sheet -- /characters, deep-
+ * linked to the character currently being played. Token in the FRAGMENT
+ * for the same reasons as above; `next` carries the deep link. Unlike the
+ * Forge handoff the game KEEPS RUNNING -- this is a glance at the sheet
+ * mid-play, not a goodbye.
+ *
+ * The /characters/<slug> shape is CO-OWNED with the web side (their
+ * character-sheet page) -- do not reshape it here alone.
+ */
+export function buildCharacterSheetUrl(resumeToken, slug) {
+    const next = `${CHARACTERS_PAGE}/${encodeURIComponent(slug)}`;
+    return `${CLI_LOGIN_URL}?t=${Date.now()}#token=${encodeURIComponent(resumeToken)}&next=${next}`;
+}
 /**
  * WHAT THE CLI SAYS ON ITS WAY OUT of the chargen handoff. Extracted
  * from the command handler so the two things that matter about it are

package/bundle/typescript/src/commands/game/sideQuest/utilities/web-character-generator.js.map

@@ -1 +1 @@
-{"version":3,"file":"web-character-generator.js","sourceRoot":"","sources":["../../../../../../../src/commands/game/sideQuest/utilities/web-character-generator.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,MAAM,aAAa,GAAG,oCAAoC,CAAC;AAC3D,MAAM,wBAAwB,GAAG,sBAAsB,CAAC;AAExD;;;;;;;GAOG;AACH,MAAM,UAAU,gCAAgC,CAAC,KAGhD;IACC,OAAO,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,IAAI,OAAO,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC;AAC1D,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,0BAA0B,CAAC,WAAmB;IAC5D,qEAAqE;IACrE,oEAAoE;IACpE,mEAAmE;IACnE,oEAAoE;IACpE,kEAAkE;IAClE,gEAAgE;IAChE,+DAA+D;IAC/D,6BAA6B;IAC7B,OAAO,GAAG,aAAa,MAAM,IAAI,CAAC,GAAG,EAAE,UAAU,kBAAkB,CAAC,WAAW,CAAC,SAAS,wBAAwB,EAAE,CAAC;AACtH,CAAC;AAED;;oEAEoE;AACpE,MAAM,CAAC,MAAM,gBAAgB,GAAG,WAAW,CAAC;AAE5C;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,qBAAqB,CAAC,GAAW;IAC/C,OAAO;QACL,MAAM,EAAE,oCAAoC,GAAG,EAAE;QACjD,KAAK,EAAE;YACL,yFAAyF;YACzF,0BAA0B,gBAAgB,oCAAoC;SAC/E;KACF,CAAC;AACJ,CAAC"}
+{"version":3,"file":"web-character-generator.js","sourceRoot":"","sources":["../../../../../../../src/commands/game/sideQuest/utilities/web-character-generator.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,MAAM,aAAa,GAAG,oCAAoC,CAAC;AAC3D,MAAM,wBAAwB,GAAG,sBAAsB,CAAC;AAExD;;;;;;;GAOG;AACH,MAAM,UAAU,gCAAgC,CAAC,KAGhD;IACC,OAAO,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,IAAI,OAAO,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC;AAC1D,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,0BAA0B,CAAC,WAAmB;IAC5D,qEAAqE;IACrE,oEAAoE;IACpE,mEAAmE;IACnE,oEAAoE;IACpE,kEAAkE;IAClE,gEAAgE;IAChE,+DAA+D;IAC/D,6BAA6B;IAC7B,OAAO,GAAG,aAAa,MAAM,IAAI,CAAC,GAAG,EAAE,UAAU,kBAAkB,CAAC,WAAW,CAAC,SAAS,wBAAwB,EAAE,CAAC;AACtH,CAAC;AAED;;oEAEoE;AACpE,MAAM,CAAC,MAAM,gBAAgB,GAAG,WAAW,CAAC;AAE5C,MAAM,eAAe,GAAG,aAAa,CAAC;AAEtC;;;;;;;;;;GAUG;AACH,MAAM,UAAU,sBAAsB,CAAC,WAAmB,EAAE,IAAY;IACtE,MAAM,IAAI,GAAG,GAAG,eAAe,IAAI,kBAAkB,CAAC,IAAI,CAAC,EAAE,CAAC;IAC9D,OAAO,GAAG,aAAa,MAAM,IAAI,CAAC,GAAG,EAAE,UAAU,kBAAkB,CAAC,WAAW,CAAC,SAAS,IAAI,EAAE,CAAC;AAClG,CAAC;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,qBAAqB,CAAC,GAAW;IAC/C,OAAO;QACL,MAAM,EAAE,oCAAoC,GAAG,EAAE;QACjD,KAAK,EAAE;YACL,yFAAyF;YACzF,0BAA0B,gBAAgB,oCAAoC;SAC/E;KACF,CAAC;AACJ,CAAC"}

package/bundle/typescript/src/commands/update.js

@@ -3,7 +3,8 @@ import { Log } from '../tools/log/log.class.js';
 Command.create({
     name: 'update',
     validOpts: [
-        { name: 'binary', boolFlag: true, description: 'From an npm install, switch to the standalone release binary instead of updating via npm (removes the npm install once the binary is verified on PATH)' },
+        { name: 'binary', boolFlag: true, description: 'Switch to the standalone release binary, unlinking or removing the npm install once the binary is verified on PATH' },
+        { name: 'npm', boolFlag: true, description: 'Switch back to the npm install, removing the standalone binary once the npm install is verified on PATH (needs Node.js)' },
     ],
     validArgs: ['maka'],
     minArgLength: 1,
@@ -12,6 +13,7 @@ Command.create({
     examples: [
         'maka update maka',
         'maka update maka --binary',
+        'maka update maka --npm',
     ]
 }, async function (args, opts) {
     try {
@@ -21,7 +23,7 @@ Command.create({
             process.exit(1);
         }
         const { updateMakaCli } = await import('../tools/self-update/update-maka.js');
-        await updateMakaCli({ binary: opts.binary });
+        await updateMakaCli({ binary: opts.binary, npm: opts.npm });
     }
     catch (e) {
         Log.error(`Update failed: ${e.message}`);

package/bundle/typescript/src/commands/update.js.map

@@ -1 +1 @@
-{"version":3,"file":"update.js","sourceRoot":"","sources":["../../../../src/commands/update.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,GAAG,EAAE,MAAM,2BAA2B,CAAC;AA6BhD,OAAO,CAAC,MAAM,CAAC;IACb,IAAI,EAAE,QAAQ;IACd,SAAS,EAAE;QACT,EAAE,IAAI,EAAE,QAAQ,EAAE,QAAQ,EAAE,IAAI,EAAE,WAAW,EAAE,wJAAwJ,EAAE;KAC1M;IACD,SAAS,EAAE,CAAC,MAAM,CAAC;IACnB,YAAY,EAAE,CAAC;IACf,KAAK,EAAE,kBAAkB;IACzB,SAAS,EAAE,oDAAoD;IAC/D,QAAQ,EAAE;QACR,kBAAkB;QAClB,2BAA2B;KAC5B;CACF,EAAE,KAAK,WAAW,IAAc,EAAE,IAAiB;IAClD,IAAI,CAAC;QACH,IAAI,IAAI,CAAC,CAAC,CAAC,KAAK,MAAM,EAAE,CAAC;YACvB,GAAG,CAAC,KAAK,CAAC,iFAAiF,CAAC,CAAC;YAC7F,GAAG,CAAC,MAAM,CAAC,qGAAqG,CAAC,CAAC;YAClH,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;QAClB,CAAC;QACD,MAAM,EAAE,aAAa,EAAE,GAAG,MAAM,MAAM,CAAC,qCAAqC,CAAC,CAAC;QAC9E,MAAM,aAAa,CAAC,EAAE,MAAM,EAAE,IAAI,CAAC,MAAM,EAAE,CAAC,CAAC;IAC/C,CAAC;IAAC,OAAO,CAAC,EAAE,CAAC;QACX,GAAG,CAAC,KAAK,CAAC,kBAAmB,CAAW,CAAC,OAAO,EAAE,CAAC,CAAC;QACpD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;AACH,CAAC,CAAC,CAAC"}
+{"version":3,"file":"update.js","sourceRoot":"","sources":["../../../../src/commands/update.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,GAAG,EAAE,MAAM,2BAA2B,CAAC;AAuChD,OAAO,CAAC,MAAM,CAAC;IACb,IAAI,EAAE,QAAQ;IACd,SAAS,EAAE;QACT,EAAE,IAAI,EAAE,QAAQ,EAAE,QAAQ,EAAE,IAAI,EAAE,WAAW,EAAE,oHAAoH,EAAE;QACrK,EAAE,IAAI,EAAE,KAAK,EAAE,QAAQ,EAAE,IAAI,EAAE,WAAW,EAAE,yHAAyH,EAAE;KACxK;IACD,SAAS,EAAE,CAAC,MAAM,CAAC;IACnB,YAAY,EAAE,CAAC;IACf,KAAK,EAAE,kBAAkB;IACzB,SAAS,EAAE,oDAAoD;IAC/D,QAAQ,EAAE;QACR,kBAAkB;QAClB,2BAA2B;QAC3B,wBAAwB;KACzB;CACF,EAAE,KAAK,WAAW,IAAc,EAAE,IAAiB;IAClD,IAAI,CAAC;QACH,IAAI,IAAI,CAAC,CAAC,CAAC,KAAK,MAAM,EAAE,CAAC;YACvB,GAAG,CAAC,KAAK,CAAC,iFAAiF,CAAC,CAAC;YAC7F,GAAG,CAAC,MAAM,CAAC,qGAAqG,CAAC,CAAC;YAClH,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;QAClB,CAAC;QACD,MAAM,EAAE,aAAa,EAAE,GAAG,MAAM,MAAM,CAAC,qCAAqC,CAAC,CAAC;QAC9E,MAAM,aAAa,CAAC,EAAE,MAAM,EAAE,IAAI,CAAC,MAAM,EAAE,GAAG,EAAE,IAAI,CAAC,GAAG,EAAE,CAAC,CAAC;IAC9D,CAAC;IAAC,OAAO,CAAC,EAAE,CAAC;QACX,GAAG,CAAC,KAAK,CAAC,kBAAmB,CAAW,CAAC,OAAO,EAAE,CAAC,CAAC;QACpD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;AACH,CAAC,CAAC,CAAC"}

package/bundle/typescript/src/tools/self-update/binary-install.d.ts

@@ -14,52 +14,87 @@ export interface IInstallCheck {
      *  --binary's refusal prints, naming what was actually found. */
     reason: string;
 }
-/**
- * Classifies the global npm install of @maka/maka-cli. Pure -- takes the
- * gathered facts instead of gathering them (see gatherInstallFacts()),
- * so the decision itself needs no filesystem or npm to test.
- *
- * REALPATH COMPARISON IS THE ONLY RELIABLE CHECK HERE. A Windows npm-link
- * junction does NOT report as a symlink via fs.lstatSync().isSymbolicLink()
- * -- verified directly against this machine's own global maka, a real
- * example of exactly this shape: isSymbolicLink() false, realpathSync()
- * resolving somewhere else entirely. Comparing realpathSync() against the
- * raw path is what actually catches it, on every platform, so that is the
- * only signal this function looks at.
- */
-export declare function classifyGlobalInstall(facts: {
+export interface IInstallFacts {
     /** <npm root -g>/@maka/maka-cli, or undefined if npm reports no global
      *  install at all. */
     globalPackagePath: string | undefined;
     /** fs.realpathSync(globalPackagePath), or undefined if the path above
      *  is undefined or does not exist. */
     globalPackageRealPath: string | undefined;
-}): IInstallCheck;
-/** Gathers the facts classifyGlobalInstall() needs. The one impure half of
- *  the classification -- kept separate so the decision above stays pure. */
-export declare function gatherInstallFacts(globalNpmRoot: string): {
-    globalPackagePath: string | undefined;
-    globalPackageRealPath: string | undefined;
-};
+    /** fs.realpathSync(<npm root -g>), or undefined when that will not
+     *  resolve. Load-bearing -- see classifyGlobalInstall(). */
+    globalNpmRootRealPath: string | undefined;
+}
 /**
- * The PATH a freshly opened shell will see once the disclosed PATH edit
- * has actually taken effect -- NOT what the currently-running process
- * inherits. A registry/profile edit never reaches an already-running
- * process, so verifying against process.env.PATH as-is would silently
- * check the OLD path (finding the npm shim pre-uninstall, or nothing
- * post-uninstall) and pass for the wrong reason. Pure: given the pieces,
- * constructs the string; the caller decides what to spawn with it.
+ * Classifies the global npm install of @maka/maka-cli. Pure -- takes the
+ * gathered facts instead of gathering them (see gatherInstallFacts()),
+ * so the decision itself needs no filesystem or npm to test.
+ *
+ * REALPATH COMPARISON IS THE ONLY THING THAT CATCHES AN npm link. A Windows
+ * npm-link junction does NOT report as a symlink via
+ * fs.lstatSync().isSymbolicLink() -- verified directly on this project's dev
+ * machine: isSymbolicLink() false, realpathSync() resolving elsewhere. So a
+ * realpath comparison it is.
  *
- * npmShimDir is removed from the old PATH (not just left alongside the
- * new entry) so the constructed env matches the END STATE this flow
- * commits to -- binary replaces, never coexists on PATH either.
+ * BUT THE COMPARISON HAS TO BE MADE RELATIVE TO THE NPM ROOT, and the first
+ * cut of this function was not. It compared the package's raw path against
+ * its own realpath and called any difference a dev link -- which is wrong
+ * for every version manager that reaches node through a symlinked prefix.
+ * nvm-for-windows makes `C:\Program Files\nodejs` itself a junction to the
+ * active version, so on that machine EVERY global package "resolves
+ * elsewhere" and --binary refused to run for an install that was as plain
+ * as they come. Homebrew, fnm, volta, asdf and n all have the same shape on
+ * POSIX. Measured, not theorised: it is why the switch this file exists for
+ * silently never worked on the machine it was written on.
+ *
+ * The distinction that actually separates the two: an ancestor-only link
+ * PRESERVES the package's position under the root, so the realpath is
+ * exactly <real root>/@maka/maka-cli. A real `npm link` points off to a
+ * working tree somewhere else entirely. Comparing against the resolved root
+ * asks that question directly.
  */
+export declare function classifyGlobalInstall(facts: IInstallFacts): IInstallCheck;
+/** The question --binary asks before it unlinks a dev link. Kept next to
+ *  the classification that produces the case, and pure, so the promise it
+ *  makes about the working tree is asserted rather than assumed.
+ *
+ *  IT IS A QUESTION AND NOT A REFUSAL, which it used to be. Refusing sent
+ *  the user off to run npm by hand for a step this flow can do correctly
+ *  itself -- and it is safe to do, because removing a global link removes
+ *  the LINK: the tree it points at is not npm's to delete and npm does not
+ *  touch it. What the refusal was really protecting against is the switch
+ *  happening without the user knowing, so that is what survives -- the
+ *  disclosure, asked up front, before a single byte is downloaded. */
+export declare function unlinkPrompt(linkPath: string, workingTreePath: string): string;
+/** Gathers the facts classifyGlobalInstall() needs. The one impure half of
+ *  the classification -- kept separate so the decision above stays pure. */
+export declare function gatherInstallFacts(globalNpmRoot: string): IInstallFacts;
+/** Where npm puts the command shims for a global install: the prefix
+ *  itself on Windows, <prefix>/bin everywhere else. Both switch directions
+ *  need it -- one to take that directory OFF the verification PATH, the
+ *  other to put it back. */
+export declare function npmShimDirFor(npmPrefix: string, platform: NodeJS.Platform): string;
+/** The `--binary` direction: the downloaded binary's directory takes the
+ *  front, npm's shim directory goes. */
 export declare function buildVerificationPath(input: {
     currentPath: string;
     newBinDir: string;
     npmShimDir: string | undefined;
     pathSeparator: string;
 }): string;
+/** The `--npm` direction: the same edit run backwards. npm's shim
+ *  directory takes the front (it is usually already on PATH, which is why
+ *  composeVerificationPath promotes rather than duplicates it), and the
+ *  binary's directory comes off. The directory removed is always
+ *  binaryInstallDir() -- somewhere maka owns outright and nothing else
+ *  lives -- never whatever directory a hand-placed binary happens to sit
+ *  in, which could be /usr/local/bin. */
+export declare function buildRevertVerificationPath(input: {
+    currentPath: string;
+    binaryBinDir: string;
+    npmShimDir: string;
+    pathSeparator: string;
+}): string;
 export interface IPosixProfile {
     shell: string;
     profilePath: string;
@@ -79,14 +114,44 @@ export declare function detectPosixProfile(shellEnv: string | undefined, homeDir
  *  `fish_add_path` is idiomatic there (fish does not use `export`); every
  *  other shell gets a plain POSIX export. */
 export declare function pathExportLine(shell: string, binDir: string): string;
+/** The comment `--binary` writes above the line it adds. Exported and used
+ *  by BOTH the write and the removal, so the two cannot drift into a state
+ *  where `--npm` leaves an orphaned comment behind. */
+export declare const PATH_EDIT_MARKER = "# added by `maka update maka --binary`";
+/**
+ * A shell profile with the PATH line `--binary` added taken back out,
+ * ready for `--npm` to write. Pure: string in, string out, so what it
+ * promises to leave alone is asserted rather than hoped for.
+ *
+ * MATCHES ON THE LINE, NOT ON THE MARKER, and removes the marker
+ * separately. Anchoring to the comment would strand the export whenever a
+ * user has tidied their profile, and stranding the export is the failure
+ * that matters: it silently keeps a deleted directory on PATH. Both shell
+ * dialects are checked because the profile that gets read here is not
+ * necessarily the one that was written -- $SHELL can change between the
+ * two runs.
+ */
+export declare function withoutPathExport(profileContents: string, binDir: string): string;
+/** True when the profile still carries a PATH line for this directory --
+ *  asked before prompting, so `--npm` does not offer to edit a file it has
+ *  nothing to change in. */
+export declare function hasPathExport(profileContents: string, binDir: string): boolean;
 /** Resolves a bare command name against a PATH string by hand, the same
  *  way a shell would -- used to PROVE the constructed verification PATH
- *  actually finds our binary first, rather than trusting that spawning
- *  "maka" and getting SOME successful output means it found the right
- *  one. Extension order matches Windows' own PATHEXT precedence
+ *  actually finds the incoming shape first, rather than trusting that
+ *  spawning "maka" and getting SOME successful output means it found the
+ *  right one. Extension order matches Windows' own PATHEXT precedence
  *  (.exe before .cmd/.bat); POSIX has no such notion, so the bare name
- *  is the only candidate there. */
-export declare function resolveOnPath(name: string, pathValue: string, platform: NodeJS.Platform, pathSeparator: string): string | undefined;
+ *  is the only candidate there.
+ *
+ *  `ignore` is how the `--npm` direction models its own end state. That
+ *  flow verifies BEFORE it removes the binaries -- deliberately, so a
+ *  failed verification can stop with the binary still working -- which
+ *  means the files it is about to retire are still sitting on disk, still
+ *  first, and would answer the question with the very thing being
+ *  replaced. Skipping them asks what a shell will find AFTERWARDS, which
+ *  is the question worth answering. */
+export declare function resolveOnPath(name: string, pathValue: string, platform: NodeJS.Platform, pathSeparator: string, ignore?: string[]): string | undefined;
 /** Places a downloaded, verified binary at targetPath. Reuses
  *  self-update.ts's swapPlanFor()/executeSwapPlan() for the case they
  *  were built for -- overwriting an EXISTING file, where Windows' plan
@@ -96,6 +161,43 @@ export declare function resolveOnPath(name: string, pathValue: string, platform:
  *  plain move instead of asking swapPlanFor to rename a file that does
  *  not exist. */
 export declare function installStagedBinary(stagedPath: string, targetPath: string, platform: NodeJS.Platform): Promise<void>;
+/**
+ * Takes the binary distribution back out of service -- the last and only
+ * destructive step of `--npm`, the mirror of the npm uninstall that ends
+ * `--binary`.
+ *
+ * ON WINDOWS THIS FILE IS THE RUNNING PROCESS and cannot be deleted, so it
+ * is renamed aside to `.old` instead, exactly the trick swapPlanFor() uses
+ * to update a binary in place. Renaming is enough for the purpose: the
+ * name `maka.exe` stops resolving, which is the whole requirement. POSIX
+ * unlinks a running executable happily, so there it simply goes.
+ */
+export declare function retireBinaryInstall(binaryPath: string, platform: NodeJS.Platform): {
+    removed: boolean;
+    renamedTo?: string;
+};
+/**
+ * What to run to make a maka -- packaged or npm-installed -- print its
+ * version, used by BOTH switch directions to prove the incoming install
+ * actually runs before the outgoing one is taken away.
+ *
+ * IT IS THE `version` COMMAND AND NOT `--version`, and the difference is
+ * not cosmetic. maka's argument parser wants a command; a bare flag with
+ * no command reaches it as no command at all and it exits 1 with "Too few
+ * arguments". Both directions of this switch verify by looking for the
+ * version string in successful output, so `--version` fails that check
+ * every single time -- which is how --binary came to be a flow that could
+ * download, verify, stage and PATH-install a binary and then refuse to
+ * finish, every time, on every machine. Measured, not reasoned: `maka
+ * version` prints "Maka <x.y.z>" and exits 0, `maka --version` prints the
+ * usage banner and exits 1.
+ *
+ * A constant rather than a literal at each site because there are two
+ * sites now, and the failure mode of getting this wrong is silent: a
+ * verification that can never pass looks exactly like a careful one until
+ * somebody runs it.
+ */
+export declare const VERSION_PROBE_ARGV: string[];
 /** Compares two spawnSync-style results the way check-bundle-parity.mjs
  *  compares builds: same exit status, same combined stdout+stderr. No
  *  path-scrubbing normalization here -- both invocations run the exact