@needmoretruth/nmts-cli 0.34.4 → 0.36.1

package/dist/arg-options.d.ts

@@ -0,0 +1,169 @@
+export interface ParsedArgs {
+    command: string | null;
+    /** Positional arguments after the command. */
+    operands: string[];
+    server?: string;
+    network?: string;
+    help: boolean;
+    version: boolean;
+    /** Machine-readable output where a command has one. */
+    json: boolean;
+    /** Include what is in the trash. */
+    all: boolean;
+    /** Where to write a fetched file. */
+    out?: string;
+    /** Replace a file that is already there. */
+    force: boolean;
+    /** The name an uploaded file gets in the drive. */
+    name?: string;
+    /** The destination folder for an upload. */
+    to?: string;
+    /** Say what an upload would cost and stop. */
+    dryRun: boolean;
+    /** `put`: how much of a file goes into one part. A byte count, optionally with a unit. */
+    partSize?: string;
+    /** `put`/`push`: what THIS run does about a name already in use. Absent = this machine's setting. */
+    onCollision?: string;
+    /** `put`/`push`: credits THIS upload sets aside per file, 0 to 64. Absent = the account's default. */
+    deposit?: string;
+    /** Answer yes to a warning this run would otherwise stop on. */
+    yes: boolean;
+    /** `public-code`: publish this account's public code on the server. Permanent. */
+    publish: boolean;
+    /** `login`: store the NMTS key unsealed rather than under a passphrase. */
+    plain: boolean;
+    /** `login`: store nothing; print the environment variable to set. */
+    env: boolean;
+    /** `verify`: report whether the human check is live and stop, asking for no new code. */
+    status: boolean;
+    /** `create`: print the registration address and stop, rather than waiting for a person. */
+    noWait?: boolean;
+    /** `ls`: keep only files whose name contains this text, case-insensitively. */
+    find?: string;
+    /** `ls`: which order to list in — `name`, `size` or `date`. Absent = the path order. */
+    sort?: string;
+    /** `ls`: reverse whichever order is in effect. */
+    desc: boolean;
+    /** `push`: include entries whose name begins with a dot. */
+    hidden: boolean;
+    /** `extend`: how many of the storage network's epochs to add; `put`/`push --pay wallet`: how many to buy. */
+    epochs?: string;
+    /** `put`/`push`: who pays for the storage — `credits` (the default) or `wallet`. */
+    pay?: string;
+    /** `put --pay wallet`: `fit`, `whole`, or a held storage resource's object id. */
+    storage?: string;
+    /** `consent grant wallet`: how long the grant lasts (days, at most 30), or until a date.
+     *  `key new`: how many days the new API key lasts. The server clamps at its own ceiling. */
+    days?: string;
+    until?: string;
+    /** `consent grant wallet`: `storage` or `all`. */
+    scope?: string;
+    /** `key new`: which permissions the key carries — `read`, `write`, `spend`, comma-separated. */
+    scopes?: string;
+    /** `consent grant wallet`: ceilings in coins. */
+    capWal?: string;
+    capSui?: string;
+    /** `wallet send` · `wallet swap`: a ceiling on the chain fee, in SUI. */
+    feeCap?: string;
+    /** `wallet swap`: which venue, deepbook or bluefin. Without it both are quoted and the run stops. */
+    venue?: string;
+    /** `wallet swap`: the slippage allowance in whole bps (1 bps = 0.01%). */
+    slippageBps?: string;
+    /** `wallet swap`: a person's say past the extremes gate. Refused while a mode is on. */
+    acceptExtremes: boolean;
+    /** `wallet address`: which of this key's wallets to print. Absent = the first one, offline. */
+    index?: string;
+    /**
+     * `put`/`push`/`extend`/`wallet send`/`wallet donate`: which wallet pays, THIS RUN ONLY — and
+     * `wallet swap`/`wallet storage split|merge|transfer`/`wallet hall --name`, which act on that
+     * same wallet without paying anybody.
+     *
+     * ⛔ IT DOES NOT SAVE. Which wallet pays is the account's own setting (`nmts wallet use N`), read
+     *    from the sealed file list so every device agrees; a flag that quietly rewrote it would make
+     *    one hurried command change where the money comes from for every later one, everywhere.
+     */
+    wallet?: string;
+    /** `s3`: which loopback port the gateway listens on. */
+    port?: string;
+    /**
+     * `create`: the version of the Terms of Service a PERSON read and accepts for the new account.
+     *
+     * ⛔ IT IS A VALUE AND NOT A FLAG, so that what was accepted is on the command line rather than
+     *    implied by it. A tool that could accept "whatever is current" would be agreeing on behalf
+     *    of somebody who never saw a version number.
+     */
+    acceptTerms?: string;
+    /** `create`: the version of the Privacy Policy accepted in the same act. */
+    acceptPrivacy?: string;
+    /** `losses`: ask the chain about ONE listed storage object now, instead of listing. */
+    recheck?: string;
+    /** `losses`: take ONE line off this account's own drive, instead of listing. ⛔ A VALUE AND NOT
+     *  A FLAG, so the line put down is named on the command line: a person reads one and puts it down. */
+    dismiss?: string;
+    /** `shares`: who ONE file was shared with, instead of what was shared with this account. */
+    sent?: string;
+    /** ultra-high acts under skip-permissions: why this is right to do now. Kept in the run log. */
+    reason?: string;
+    releaseStorage: boolean;
+    size?: string;
+    /** `devices`: sign ONE device out by id, or `all` — a person's act, proved by the NMTS key. */
+    signOut?: string;
+    /**
+     * `label`: the label to rename. The NEW name follows as the operand.
+     *
+     * ⛔ ONE VALUE, NOT TWO, because the table above gives every option exactly one — and a second
+     *    spelling of "how many values does this take" is how an option ends up parsed one way and
+     *    tested another. What a person types is still `label --rename <old> <new>`: the new name is
+     *    read from the operands, which is where `label <name> <files>` already reads a name from.
+     */
+    rename?: string;
+    /** `support send`: what the report is about, and optionally which part of that. */
+    category?: string;
+    sub?: string;
+    /** `support`: the message itself, or the file holding it. */
+    message?: string;
+    messageFile?: string;
+    /**
+     * `support send`: attach the run log, and how many runs of it.
+     * ⛔ THE EMPTY STRING IS "GIVEN WITH NO NUMBER", which is different from absent. A boolean
+     *    beside a count would be two fields answering one question, and the pair can disagree.
+     */
+    attachLog?: string;
+    /**
+     * `support`: values that must not travel, replaced wherever they appear.
+     *
+     * ⛔ THE ONLY REPEATABLE OPTION, and it is repeatable because what it names is one value at a
+     *    time. A comma-separated list would make a comma impossible to omit.
+     */
+    omit?: string[];
+    /**
+     * `whoami`: print the NMTS key itself.
+     *
+     * ⛔ A FLAG AND NOT A VALUE — it names no secret, it asks for the one this machine already
+     *    holds. The option table is checked for names that look like credentials; this one carries
+     *    nothing and says what it does.
+     */
+    reveal: boolean;
+    /**
+     * `key new`: put the new key on the screen once, as well as storing it. A flag and not a value
+     * for the reason above: it names no secret, it asks for the one this run was just handed.
+     */
+    print: boolean;
+    /** `nmts wallet address --qr` — the address as a QR code in the terminal as well. */
+    qr: boolean;
+    /** `wallet hall --remove`: be listed by a shortened address again. Never with `--name`. */
+    remove: boolean;
+    /** `terms`/`privacy`: which language to fetch — `en` or `ko`. Absent = English. */
+    lang?: string;
+    /** `terms`: the message board's terms rather than the service's. */
+    board: boolean;
+    /**
+     * `notices`/`terms`/`privacy`: keep the document as a file instead of printing it.
+     *
+     * ⛔ A FLAG, AND THE NOTICE'S ID IS STILL THE OPERAND. `notices --save <id>` reads exactly like
+     *    `notices <id>`, which is the point: one way to name a notice, whichever of the two things
+     *    is being done with it. The file's NAME is never an option — it is the server's, so that a
+     *    copy kept here and a copy kept from the browser are the same file.
+     */
+    save: boolean;
+}

package/dist/arg-options.js

@@ -0,0 +1,10 @@
+// What a command line can say — every option this tool accepts, in one place.
+//
+// ⛔ THE FIELDS ARE THE VOCABULARY, and the parser beside them (`args.ts`) is the only thing that
+//    fills them. They moved out of that file on 2026-09-16 because the two are different jobs and
+//    the parser's file had a ceiling: this is what the options MEAN, that is how a line is read.
+//
+// ⛔ NO SECRET IS EVER AN OPTION. There is no --code and no --api-key: on Linux any process can
+//    read another's command line, and the shell records it. A test asserts no option name looks
+//    like one.
+export {};

package/dist/args.d.ts

@@ -1,160 +1,5 @@
-export interface ParsedArgs {
-    command: string | null;
-    /** Positional arguments after the command. */
-    operands: string[];
-    server?: string;
-    network?: string;
-    help: boolean;
-    version: boolean;
-    /** Machine-readable output where a command has one. */
-    json: boolean;
-    /** Include what is in the trash. */
-    all: boolean;
-    /** Where to write a fetched file. */
-    out?: string;
-    /** Replace a file that is already there. */
-    force: boolean;
-    /** The name an uploaded file gets in the drive. */
-    name?: string;
-    /** The destination folder for an upload. */
-    to?: string;
-    /** Say what an upload would cost and stop. */
-    dryRun: boolean;
-    /** `put`: how much of a file goes into one part. A byte count, optionally with a unit. */
-    partSize?: string;
-    /** `put`/`push`: what THIS run does about a name already in use. Absent = this machine's setting. */
-    onCollision?: string;
-    /** `put`/`push`: credits THIS upload sets aside per file, 0 to 64. Absent = the account's default. */
-    deposit?: string;
-    /** Answer yes to a warning this run would otherwise stop on. */
-    yes: boolean;
-    /** `public-code`: publish this account's public code on the server. Permanent. */
-    publish: boolean;
-    /** `login`: store the NMTS key unsealed rather than under a passphrase. */
-    plain: boolean;
-    /** `login`: store nothing; print the environment variable to set. */
-    env: boolean;
-    /** `verify`: report whether the human check is live and stop, asking for no new code. */
-    status: boolean;
-    /** `create`: print the registration address and stop, rather than waiting for a person. */
-    noWait?: boolean;
-    /** `ls`: keep only files whose name contains this text, case-insensitively. */
-    find?: string;
-    /** `ls`: which order to list in — `name`, `size` or `date`. Absent = the path order. */
-    sort?: string;
-    /** `ls`: reverse whichever order is in effect. */
-    desc: boolean;
-    /** `push`: include entries whose name begins with a dot. */
-    hidden: boolean;
-    /** `extend`: how many of the storage network's epochs to add; `put`/`push --pay wallet`: how many to buy. */
-    epochs?: string;
-    /** `put`/`push`: who pays for the storage — `credits` (the default) or `wallet`. */
-    pay?: string;
-    /** `put --pay wallet`: `fit`, `whole`, or a held storage resource's object id. */
-    storage?: string;
-    /** `consent grant wallet`: how long the grant lasts (days, at most 30), or until a date.
-     *  `key new`: how many days the new API key lasts. The server clamps at its own ceiling. */
-    days?: string;
-    until?: string;
-    /** `consent grant wallet`: `storage` or `all`. */
-    scope?: string;
-    /** `key new`: which permissions the key carries — `read`, `write`, `spend`, comma-separated. */
-    scopes?: string;
-    /** `consent grant wallet`: ceilings in coins. */
-    capWal?: string;
-    capSui?: string;
-    /** `wallet send` · `wallet swap`: a ceiling on the chain fee, in SUI. */
-    feeCap?: string;
-    /** `wallet swap`: which venue, deepbook or bluefin. Without it both are quoted and the run stops. */
-    venue?: string;
-    /** `wallet swap`: the slippage allowance in whole bps (1 bps = 0.01%). */
-    slippageBps?: string;
-    /** `wallet swap`: a person's say past the extremes gate. Refused while a mode is on. */
-    acceptExtremes: boolean;
-    /** `s3`: which loopback port the gateway listens on. */
-    port?: string;
-    /**
-     * `create`: the version of the Terms of Service a PERSON read and accepts for the new account.
-     *
-     * ⛔ IT IS A VALUE AND NOT A FLAG, so that what was accepted is on the command line rather than
-     *    implied by it. A tool that could accept "whatever is current" would be agreeing on behalf
-     *    of somebody who never saw a version number.
-     */
-    acceptTerms?: string;
-    /** `create`: the version of the Privacy Policy accepted in the same act. */
-    acceptPrivacy?: string;
-    /** `losses`: ask the chain about ONE listed storage object now, instead of listing. */
-    recheck?: string;
-    /** `losses`: take ONE line off this account's own drive, instead of listing. ⛔ A VALUE AND NOT
-     *  A FLAG, so the line put down is named on the command line: a person reads one and puts it down. */
-    dismiss?: string;
-    /** `shares`: who ONE file was shared with, instead of what was shared with this account. */
-    sent?: string;
-    /** ultra-high acts under skip-permissions: why this is right to do now. Kept in the run log. */
-    reason?: string;
-    releaseStorage: boolean;
-    size?: string;
-    /** `devices`: sign ONE device out by id, or `all` — a person's act, proved by the NMTS key. */
-    signOut?: string;
-    /**
-     * `label`: the label to rename. The NEW name follows as the operand.
-     *
-     * ⛔ ONE VALUE, NOT TWO, because the table above gives every option exactly one — and a second
-     *    spelling of "how many values does this take" is how an option ends up parsed one way and
-     *    tested another. What a person types is still `label --rename <old> <new>`: the new name is
-     *    read from the operands, which is where `label <name> <files>` already reads a name from.
-     */
-    rename?: string;
-    /** `support send`: what the report is about, and optionally which part of that. */
-    category?: string;
-    sub?: string;
-    /** `support`: the message itself, or the file holding it. */
-    message?: string;
-    messageFile?: string;
-    /**
-     * `support send`: attach the run log, and how many runs of it.
-     * ⛔ THE EMPTY STRING IS "GIVEN WITH NO NUMBER", which is different from absent. A boolean
-     *    beside a count would be two fields answering one question, and the pair can disagree.
-     */
-    attachLog?: string;
-    /**
-     * `support`: values that must not travel, replaced wherever they appear.
-     *
-     * ⛔ THE ONLY REPEATABLE OPTION, and it is repeatable because what it names is one value at a
-     *    time. A comma-separated list would make a comma impossible to omit.
-     */
-    omit?: string[];
-    /**
-     * `whoami`: print the NMTS key itself.
-     *
-     * ⛔ A FLAG AND NOT A VALUE — it names no secret, it asks for the one this machine already
-     *    holds. The option table is checked for names that look like credentials; this one carries
-     *    nothing and says what it does.
-     */
-    reveal: boolean;
-    /**
-     * `key new`: put the new key on the screen once, as well as storing it. A flag and not a value
-     * for the reason above: it names no secret, it asks for the one this run was just handed.
-     */
-    print: boolean;
-    /** `nmts wallet address --qr` — the address as a QR code in the terminal as well. */
-    qr: boolean;
-    /** `wallet hall --remove`: be listed by a shortened address again. Never with `--name`. */
-    remove: boolean;
-    /** `terms`/`privacy`: which language to fetch — `en` or `ko`. Absent = English. */
-    lang?: string;
-    /** `terms`: the message board's terms rather than the service's. */
-    board: boolean;
-    /**
-     * `notices`/`terms`/`privacy`: keep the document as a file instead of printing it.
-     *
-     * ⛔ A FLAG, AND THE NOTICE'S ID IS STILL THE OPERAND. `notices --save <id>` reads exactly like
-     *    `notices <id>`, which is the point: one way to name a notice, whichever of the two things
-     *    is being done with it. The file's NAME is never an option — it is the server's, so that a
-     *    copy kept here and a copy kept from the browser are the same file.
-     */
-    save: boolean;
-}
+import type { ParsedArgs } from "./arg-options.ts";
+export type { ParsedArgs } from "./arg-options.ts";
 export declare const OPTIONS_TAKING_A_VALUE: string[];
 export declare const FLAGS: string[];
 export declare function parseArgs(argv: readonly string[]): ParsedArgs;

package/dist/args.js

@@ -32,6 +32,8 @@ const VALUE_OPTIONS = {
     "--fee-cap": "feeCap",
     "--venue": "venue",
     "--slippage-bps": "slippageBps",
+    "--index": "index",
+    "--wallet": "wallet",
     "--port": "port",
     "--accept-terms": "acceptTerms",
     "--accept-privacy": "acceptPrivacy",

package/dist/artifact-about.d.ts

@@ -11,7 +11,7 @@ export declare const CRYPTO_SPEC_URL = "https://github.com/needmoretruth/nmts-re
  *   is the field's own contract — what the writer says about itself — and a person holding two
  *   copies of one account's artefacts can then tell which program made each.
  */
-export declare const WRITTEN_BY = "nmts-cli 0.34.4";
+export declare const WRITTEN_BY = "nmts-cli 0.36.1";
 /** Which of the three artefacts a wrapper is. A reader holding several can sort them. */
 export type ArtifactKind = "recovery-list" | "file-list" | "recovery-kit";
 /**

package/dist/autonomy.d.ts

@@ -17,18 +17,11 @@ export declare function isAgentMode(mode: Autonomy): boolean;
  * and `auto` is `auto-low`. Anything else counts as `default`.
  */
 export declare function modeFromStored(value: unknown): Autonomy;
-/**
- * What this machine is set to.
- *
- * ⛔ Unreadable counts as `default`. The fail-safe direction for "I do not know" is the one where
- *    somebody is still asked -- a file that switches autonomy on when it cannot be parsed is worse
- *    than no file at all.
- */
-export declare function currentMode(): Autonomy;
+export declare function currentMode(): Promise<Autonomy>;
 /** When it was set, or null when it is default or unreadable. */
-export declare function setAt(): string | null;
+export declare function setAt(): Promise<string | null>;
 /** Write the choice down, with the date and the version that was asked. */
-export declare function setMode(mode: Autonomy, version: string, now: Date): void;
+export declare function setMode(mode: Autonomy, version: string, now: Date): Promise<void>;
 /**
  * The line every run prints when a mode is on.
  *

package/dist/autonomy.js

@@ -30,9 +30,10 @@
 // ⚠ AND WHAT NO COMMAND-LINE TOOL CAN DO: tell whether a person or a program typed this. The
 //   protection here is that the choice is explicit, written down, dated, and announced on every
 //   run that uses it -- not that it cannot be automated.
-import { existsSync, mkdirSync, readFileSync, rmSync, writeFileSync, chmodSync } from "node:fs";
-import { join } from "node:path";
-import { configDir, modesAreEnforced } from "./credentials.js";
+import { fromUtf8, utf8 } from "./bytes.js";
+import { host } from "./host.js";
+/** The one key this mode lives under. On this machine that is `autonomy.json`. */
+const KEY = "autonomy";
 export const AUTONOMY_MODES = ["default", "auto-low", "auto-high", "skip-permissions"];
 /** What each mode means, in the words the tool prints. One line each, no more. */
 export const MODE_MEANS = {
@@ -101,9 +102,6 @@ export const SKIP_SENTENCE = "NOTHING WILL ASK ME AND I ACCEPT THAT";
 export function isAgentMode(mode) {
     return mode !== "default";
 }
-function path() {
-    return join(configDir(), "autonomy.json");
-}
 /**
  * Read a stored name, including the two this tool wrote before 2026-09-06: `off` is `default`
  * and `auto` is `auto-low`. Anything else counts as `default`.
@@ -124,9 +122,13 @@ export function modeFromStored(value) {
  *    somebody is still asked -- a file that switches autonomy on when it cannot be parsed is worse
  *    than no file at all.
  */
-export function currentMode() {
+async function stored() {
+    const held = await host().state.read(KEY);
+    return held === undefined ? null : JSON.parse(fromUtf8(held));
+}
+export async function currentMode() {
     try {
-        const parsed = JSON.parse(readFileSync(path(), "utf8"));
+        const parsed = await stored();
         if (typeof parsed !== "object" || parsed === null)
             return "default";
         return modeFromStored(Reflect.get(parsed, "mode"));
@@ -136,9 +138,9 @@ export function currentMode() {
     }
 }
 /** When it was set, or null when it is default or unreadable. */
-export function setAt() {
+export async function setAt() {
     try {
-        const parsed = JSON.parse(readFileSync(path(), "utf8"));
+        const parsed = await stored();
         if (typeof parsed !== "object" || parsed === null)
             return null;
         const at = Reflect.get(parsed, "setAt");
@@ -149,17 +151,13 @@ export function setAt() {
     }
 }
 /** Write the choice down, with the date and the version that was asked. */
-export function setMode(mode, version, now) {
+export async function setMode(mode, version, now) {
     if (mode === "default") {
-        if (existsSync(path()))
-            rmSync(path(), { force: true });
+        await host().state.remove(KEY);
         return;
     }
     const body = { mode, setAt: now.toISOString(), byVersion: version };
-    mkdirSync(configDir(), { recursive: true, mode: 0o700 });
-    writeFileSync(path(), `${JSON.stringify(body, null, 2)}\n`, { mode: 0o600 });
-    if (modesAreEnforced())
-        chmodSync(path(), 0o600);
+    await host().state.write(KEY, utf8(`${JSON.stringify(body, null, 2)}\n`));
 }
 /**
  * The line every run prints when a mode is on.

package/dist/bytes.d.ts

@@ -0,0 +1,15 @@
+/** These bytes as unpadded base64url. */
+export declare function toBase64Url(bytes: Uint8Array): string;
+/**
+ * Base64url back to bytes.
+ *
+ * ⚠ PLAIN BASE64 IS ACCEPTED TOO, and on purpose: `Buffer.from(text, "base64url")` accepted both,
+ *   and a record written by an older version of this tool has to keep opening.
+ */
+export declare function fromBase64Url(text: string): Uint8Array;
+/** This text as UTF-8 bytes. */
+export declare function utf8(text: string): Uint8Array;
+/** These UTF-8 bytes as text. Malformed sequences become the replacement character. */
+export declare function fromUtf8(bytes: Uint8Array): string;
+/** One run of bytes from several, in order. */
+export declare function concat(parts: readonly Uint8Array[]): Uint8Array;

package/dist/bytes.js

@@ -0,0 +1,63 @@
+// Bytes to text and back, in the two spellings this format uses.
+//
+// ⛔ WHY NOT `Buffer`. It is Node's, it is the one global this package leaned on that a browser
+//    does not have, and every use of it was one of these five calls. A bundler shim would drag a
+//    polyfill of the whole class into a page to reach `toString("base64url")`; these are ten lines
+//    on top of what the chain library already carries.
+//
+// ⛔ BASE64URL IS THE FORMAT'S SPELLING (NCF-3), not a preference. Sealed blobs, wrapped keys and
+//    chunk names all travel unpadded with `-` and `_`, because they end up in URLs and file names.
+//    The alphabet swap and the padding live here, in one place, so that a second spelling cannot
+//    appear somewhere and produce a name that never matches.
+//
+// ⛔ `atob`/`btoa` RATHER THAN A LIBRARY, and that is not a reinvention: they are the runtime's own
+//    base64, present in Node and in every browser, and they are what the browser half of this
+//    product already decodes with (`web/src/lib/crypto/wasm-engine.ts`). A package would be a
+//    dependency in the chain of `nmts --help`, which `check:cli-startup` measures and refuses.
+const encoder = new TextEncoder();
+const decoder = new TextDecoder();
+/** These bytes as unpadded base64url. */
+export function toBase64Url(bytes) {
+    let binary = "";
+    // ⚠ In runs rather than one `String.fromCharCode(...bytes)`: spreading a multi-megabyte array
+    //   into an argument list overflows the stack, and the sealed blobs here are exactly that big.
+    for (let at = 0; at < bytes.length; at += 0x8000) {
+        binary += String.fromCharCode(...bytes.subarray(at, Math.min(at + 0x8000, bytes.length)));
+    }
+    return btoa(binary).replace(/\+/g, "-").replace(/\//g, "_").replace(/=+$/, "");
+}
+/**
+ * Base64url back to bytes.
+ *
+ * ⚠ PLAIN BASE64 IS ACCEPTED TOO, and on purpose: `Buffer.from(text, "base64url")` accepted both,
+ *   and a record written by an older version of this tool has to keep opening.
+ */
+export function fromBase64Url(text) {
+    const standard = text.replace(/-/g, "+").replace(/_/g, "/");
+    const binary = atob(standard.padEnd(standard.length + ((4 - (standard.length % 4)) % 4), "="));
+    const out = new Uint8Array(binary.length);
+    for (let at = 0; at < binary.length; at += 1)
+        out[at] = binary.charCodeAt(at);
+    return out;
+}
+/** This text as UTF-8 bytes. */
+export function utf8(text) {
+    return encoder.encode(text);
+}
+/** These UTF-8 bytes as text. Malformed sequences become the replacement character. */
+export function fromUtf8(bytes) {
+    return decoder.decode(bytes);
+}
+/** One run of bytes from several, in order. */
+export function concat(parts) {
+    let total = 0;
+    for (const part of parts)
+        total += part.length;
+    const out = new Uint8Array(total);
+    let at = 0;
+    for (const part of parts) {
+        out.set(part, at);
+        at += part.length;
+    }
+    return out;
+}

package/dist/collision.d.ts

@@ -19,13 +19,13 @@ export declare const DEFAULT_COLLISION: OnCollision;
  * ⛔ Unreadable counts as `rename`, for the same reason autonomy unreadable counts as off: the
  *    fail-safe direction for "I do not know" is the one that destroys nothing.
  */
-export declare function currentChoice(): OnCollision;
+export declare function currentChoice(): Promise<OnCollision>;
 /** Has anybody answered on this machine? Used to know whether setup still has to ask. */
-export declare function hasChosen(): boolean;
+export declare function hasChosen(): Promise<boolean>;
 /** Write the choice down, with the date and the version that asked. */
-export declare function setChoice(choice: OnCollision, version: string, now: Date): void;
+export declare function setChoice(choice: OnCollision, version: string, now: Date): Promise<void>;
 /** Forget the answer, so setup asks again. */
-export declare function forgetChoice(): void;
+export declare function forgetChoice(): Promise<void>;
 /** What decided, so the tool can say so rather than acting silently. */
 export interface Decision {
     readonly choice: OnCollision;
@@ -54,7 +54,7 @@ export interface Decision {
  */
 export declare function decide(
 /** What this run asked for, if anything. `undefined` means "use what this machine is set to". */
-askedFor?: OnCollision, setting?: OnCollision, mode?: Autonomy): Decision;
+askedFor?: OnCollision, setting?: OnCollision, mode?: Autonomy): Promise<Decision>;
 /** How the two answers are numbered where setup asks. Kept here so the question and the reading agree. */
 export declare const ANSWER_NUMBER: Readonly<Record<OnCollision, string>>;
 /**

package/dist/collision.js

@@ -23,12 +23,13 @@
 // ⚠ WHAT THIS CANNOT DO is tell an agent from a person. Nothing on a command line can. What it can
 //   do is make the destructive answer require a setting that was turned on deliberately, and say
 //   which setting decided.
-import { existsSync, mkdirSync, readFileSync, rmSync, writeFileSync, chmodSync } from "node:fs";
-import { join } from "node:path";
 import { currentMode } from "./autonomy.js";
+import { fromUtf8, utf8 } from "./bytes.js";
 import { NmtsError } from "./errors.js";
+import { host } from "./host.js";
 import { BINARY_NAME } from "./product.js";
-import { configDir, modesAreEnforced } from "./credentials.js";
+/** The one key this answer lives under. On this machine that is `collision.json`. */
+const KEY = "collision";
 export const COLLISION_CHOICES = ["rename", "overwrite"];
 /** What each choice does, in the words the tool prints. One line each. */
 export const COLLISION_MEANS = {
@@ -53,9 +54,6 @@ export function parseAsked(typed) {
 }
 /** What is written down when nobody has chosen. */
 export const DEFAULT_COLLISION = "rename";
-function path() {
-    return join(configDir(), "collision.json");
-}
 function isChoice(value) {
     return typeof value === "string" && COLLISION_CHOICES.includes(value);
 }
@@ -65,9 +63,12 @@ function isChoice(value) {
  * ⛔ Unreadable counts as `rename`, for the same reason autonomy unreadable counts as off: the
  *    fail-safe direction for "I do not know" is the one that destroys nothing.
  */
-export function currentChoice() {
+export async function currentChoice() {
     try {
-        const parsed = JSON.parse(readFileSync(path(), "utf8"));
+        const held = await host().state.read(KEY);
+        if (held === undefined)
+            return DEFAULT_COLLISION;
+        const parsed = JSON.parse(fromUtf8(held));
         if (typeof parsed !== "object" || parsed === null)
             return DEFAULT_COLLISION;
         const choice = Reflect.get(parsed, "onCollision");
@@ -78,21 +79,17 @@ export function currentChoice() {
     }
 }
 /** Has anybody answered on this machine? Used to know whether setup still has to ask. */
-export function hasChosen() {
-    return existsSync(path());
+export async function hasChosen() {
+    return (await host().state.read(KEY)) !== undefined;
 }
 /** Write the choice down, with the date and the version that asked. */
-export function setChoice(choice, version, now) {
-    mkdirSync(configDir(), { recursive: true, mode: 0o700 });
+export async function setChoice(choice, version, now) {
     const body = { onCollision: choice, setAt: now.toISOString(), byVersion: version };
-    writeFileSync(path(), `${JSON.stringify(body, null, 2)}\n`, { mode: 0o600 });
-    if (modesAreEnforced())
-        chmodSync(path(), 0o600);
+    await host().state.write(KEY, utf8(`${JSON.stringify(body, null, 2)}\n`));
 }
 /** Forget the answer, so setup asks again. */
-export function forgetChoice() {
-    if (existsSync(path()))
-        rmSync(path(), { force: true });
+export async function forgetChoice() {
+    await host().state.remove(KEY);
 }
 /**
  * What to do with this collision, and what settled it.
@@ -108,14 +105,14 @@ export function forgetChoice() {
  * ⛔ THE OVERRIDE IS ONE-WAY. A mode can let `overwrite` through; nothing here turns a `rename`
  *    into an `overwrite`.
  */
-export function decide(
+export async function decide(
 /** What this run asked for, if anything. `undefined` means "use what this machine is set to". */
-askedFor, setting = currentChoice(), mode = currentMode()) {
+askedFor, setting, mode) {
     if (askedFor === undefined)
-        return { choice: setting, by: "setting" };
+        return { choice: setting ?? (await currentChoice()), by: "setting" };
     if (askedFor === "rename")
         return { choice: "rename", by: "asked-for" };
-    if (mode === "default")
+    if ((mode ?? (await currentMode())) === "default")
         return { choice: "rename", by: "agent-refused" };
     return { choice: "overwrite", by: "asked-for" };
 }