@tikoci/quickchr 0.5.1 → 0.5.3

package/.bun-version

@@ -0,0 +1 @@
+1.4.4

package/DESIGN.md

@@ -245,7 +245,9 @@ CI, integration and release all install, enforced by `scripts/check-bun-pin.ts`
 runtime could change between two identical commits — and did: a six-week gap with no `ci.yml`
 runs spanned the Bun 1.4.0 release, and the next PR inherited a 1.3.14 → 1.4.2 jump as if it
 were its own regression. Anything that can turn the build red is a dependency and belongs in
-a reviewable diff; "whatever is newest at run time" is not a version.
+a reviewable diff; "whatever is newest at run time" is not a version. The same
+`.bun-version` file ships in the npm package so `doctor` can name the tested
+runtime and warn when the running Bun is older without duplicating the pin.
 
 **The 2026-07 refactor (#29)** replaced the organically-grown scheme (integration on every
 PR push, three parallel copies of the runner logic, `continue-on-error` green-washing)
@@ -1174,3 +1176,39 @@ before acting, and uses shared stopped-state cleanup without recursively taking
 the non-reentrant stop lock. It confirms QEMU exit before clearing the PID or
 releasing named-network membership. Lock wait, hard-stop escalation and final
 exit verification are separate bounded phases outside the guest grace budget.
+
+## Frozen boot + continue (#214)
+
+Some lab workflows must touch the guest before RouterOS init runs. The driver:
+CHR's `:beep` speaker driver is skipped when CPUID reports a hypervisor, and
+patching the 2-byte gate in guest RAM via gdbstub before sys2 init unlocks
+PC-speaker capture for acoustic testing (verified on CHR 7.25, QEMU 11.1.2).
+`start --frozen` boots held at reset (`-S`) with a gdbstub; `quickchr continue`
+resumes. The RAM patch itself stays in the harness, not quickchr.
+
+The gdbstub is a unix socket (`-gdb unix:<machineDir>/gdb.sock,server=on,
+wait=off`), not `-s` (TCP :1234): no port bookkeeping, no parallel-VM
+collisions. `wait=off` is required so the spawn never blocks waiting for a
+client. Measured: `info status` reads `paused (prelaunch)`; gdb attaches with
+the CPU at the reset vector `0xfff0`. POSIX-first by scope — a Windows TCP
+fallback (e.g. `portBase+9`) is parked as a follow-up, and the integration test
+is gated off win32 until it lands.
+
+`frozen` is per-boot intent, like `--no-wait`, not persisted config: stopping
+clears the marker and a later plain `start` boots normally. `status` stays
+`"running"` while frozen — without a third status value — so `isMachineRunning()`,
+`stop`/`remove` (host-side SIGTERM works on frozen QEMU unchanged), and the
+`--all` filters keep working untouched. A never-continued frozen machine can
+never produce `BOOT_TIMEOUT`, by construction: the boot wait is skipped
+entirely, and `start` returns after the spawn early-exit check.
+
+`continue` is one existing primitive — `monitorCommand("cont")` — plus the
+promise `start` makes: REST-ready by default, `--no-wait` to return
+immediately, `--timeout-extra` extending the resume wait like `start`. It
+checks `info status` first, so a guest gdb already resumed just clears the
+marker (idempotent); a QEMU-level `cont` error throws `PROCESS_FAILED` before
+the marker is touched (same `/^error/i` contract as savevm/loadvm); a dead pid
+is `MACHINE_STOPPED`; a wait that never reaches REST is a genuine
+`BOOT_TIMEOUT` with `preserve-existing` cleanup. Deliberately out: no frozen-specific hint on `exec`/`get` failures,
+and no `savevm` refusal on prelaunch VMs (snapshot is already tricky business;
+QEMU accepts or errors on its own).

package/MANUAL.md

@@ -64,7 +64,7 @@ by the user (or their AI agent) using `quickchr` as a building block.
 | Bun ≥ 1.1 | runtime | macOS/Linux: `curl -fsSL https://bun.sh/install \| bash` · Windows: `powershell -c "irm bun.sh/install.ps1 \| iex"` (or `winget install Oven-sh.Bun`) |
 | `qemu-system-x86_64` | x86 CHR | brew/apt/dnf/pacman · Windows: `winget install SoftwareFreedomConservancy.QEMU` |
 | `qemu-system-aarch64` | arm64 CHR | brew/apt/dnf/pacman · Windows: bundled in the SFC QEMU package above |
-| `qemu-img` | `--boot-size`, `--add-disk`, snapshots | included in all standard QEMU packages (brew, apt, dnf, SFC installer) |
+| `qemu-img` | Default qcow2 creation, setup wizard, `--boot-size`, `--add-disk`, snapshots | included in all standard QEMU packages (brew, apt, dnf, SFC installer) |
 | UEFI firmware (edk2) | arm64 CHR | `qemu-efi-aarch64` (apt), `edk2-aarch64` (dnf), bundled with `qemu` (brew) |
 | `socket_vmnet` (optional) | rootless `shared`/`bridged` networking on macOS | `brew install socket_vmnet` |
 | `socat` (optional) | piping serial console externally | brew/apt |
@@ -116,7 +116,9 @@ The `--json` form emits `{ ok, checks, staleImages }`, where `checks` is an
 array of `{ label, status, detail }` and `staleImages` lists cached images older
 than the current long-term release. The exit code still reflects `ok`.
 
-![quickchr doctor output](./images/doctor-demo.gif)
+`doctor` reports the tested Bun pin and warns when the running runtime is older.
+
+![quickchr doctor output](./docs/images/doctor-demo.gif)
 
 Use this whenever a `start` fails — the diagnostic almost always points
 at a missing dependency, missing firmware, or insufficient disk.
@@ -125,7 +127,7 @@ at a missing dependency, missing firmware, or insufficient disk.
 
 ## 3. CLI command reference
 
-The dispatcher lives in `src/cli/index.ts` (lines 121–194). Help text is
+The dispatcher lives in `src/cli/index.ts`. Help text is
 available for every command via `quickchr help <command>`.
 
 ### Lifecycle
@@ -138,14 +140,14 @@ directory, downloads the RouterOS image (cached), and writes
 
 | Flag | Default | Notes |
 |---|---|---|
-| `--name <s>` | auto | `host-arch-N` if omitted |
+| `--name <s>` | auto | `version-arch-N` if omitted |
 | `--version <ver>` | latest in channel | e.g., `7.22.1` |
 | `--channel <ch>` | `stable` | `stable`, `long-term`, `testing`, `development` |
 | `--arch <a>` | host native | `arm64`, `x86`, or `auto` |
 | `--cpu <n>` | `1` | vCPU count |
 | `--mem <mb>` | `512` | RAM (cross-arch TCG bumps to `1024`) |
 | `--boot-disk-format <f>` | `qcow2` | `qcow2` or `raw` |
-| `--boot-size <size>` | — | Resize boot disk; needs `qemu-img`; auto-converts to qcow2 |
+| `--boot-size <size>` | — | Resize qcow2 boot disk; needs `qemu-img`; explicit raw is refused |
 | `--add-disk <size>` | — | Extra blank qcow2 disk; repeatable |
 | `--forward <spec>` | — | Extra hostfwd port or built-in service host-port pin; repeatable. See §Custom port forwards. |
 | `--add-package <pkg>` | — | Provisioning, repeatable, ≥ 7.20.8 |
@@ -165,6 +167,7 @@ directory, downloads the RouterOS image (cached), and writes
 | `--no-winbox` | false | Exclude WinBox port |
 | `--no-api-ssl` | false | Exclude API-SSL port |
 | `--port-base <n>` | auto from 9100 | First port of the 10-port block |
+| `--qemu-arg <arg>` | — | Extra QEMU argv element, repeatable (space form only). Recorded and reused every boot. See Extra QEMU arguments below. |
 
 `--vmnet-shared` and `--vmnet-bridge <iface>` have been removed. Use
 `--add-network shared` and `--add-network bridged:<iface>`; either old spelling is
@@ -192,7 +195,9 @@ Additional flags:
 | `--fg` / `--foreground` (alias `--no-bg`, `--no-background`) | Serial console on stdio |
 | `--bg` / `--background` | **Deprecated, does nothing.** Background is the default, and the flag never made `start` return early — it only ever chose where the serial console went. Prints a warning; use `--no-wait` |
 | `--timeout-extra <s>` / `-T <s>` | Add extra seconds to computed boot timeout |
-| `--dry-run` | Print resolved options and QEMU command, exit |
+| `--dry-run` | Print the resolved start options as JSON (including `qemuArgs`/`frozen`) and exit — not the final QEMU argv |
+| `--qemu-arg <arg>` | Extra QEMU argv element, repeatable (space form only). Recorded when creating; on an existing machine it replaces recorded args for this boot only. Refused with `--all`. |
+| `--frozen` | Boot frozen at reset (`-S`) with a gdbstub; resume with `continue`. Refused with `--fg`, provisioning, and `--all` |
 
 After `--no-wait`, readiness is yours. centrs (0.1.8+) waits for it in one command:
 
@@ -216,6 +221,62 @@ When `--fg` is combined with provisioning options, quickchr boots
 foreground with stdio attached. This is observable as a brief stop in
 machine state.
 
+**Extra QEMU arguments (`--qemu-arg`).** One argv element per occurrence,
+appended verbatim (no splitting, no validation) after quickchr's own args.
+Use the space form: `--qemu-arg=x` overwrites instead of accumulating, so
+mixing space and `=` forms keeps only the `=` values. Values beginning with
+`--` need the `--qemu-arg=<arg>` form (one element per flag).
+
+Passthrough runs with your privileges and is replayed every boot: it can
+touch any path you can (`-drive`, `-audiodev`) or open QEMU-side listeners,
+so treat recorded args like config you own. A bad recorded arg fails every
+start; recover with a session override (`start <name> --qemu-arg …`) and then
+persist the fix with `set <name> --qemu-arg …` (or `--clear-qemu-args`) while
+stopped.
+Ordering is load-bearing — passthrough goes last, so a conflicting option
+resolves last-wins (a duplicate `-M pc,...` merges over quickchr's `-M pc`;
+measured on QEMU 11.1.2). A bad element surfaces as `SPAWN_FAILED` with the
+QEMU log tail. Lab escape hatch for QEMU surface quickchr does not model —
+e.g. capturing the CHR PC speaker (x86 only) to a WAV file:
+
+```sh
+quickchr start beep-lab --version 7.25 --arch x86 \
+  --qemu-arg -M --qemu-arg pc,pcspk-audiodev=cap \
+  --qemu-arg -audiodev --qemu-arg wav,id=cap,path=$PWD/cap.wav
+# cap.wav is created at spawn (0 bytes while running); QEMU flushes the
+# 44-byte RIFF header on exit. Capturing actual beeps also needs the
+# --frozen RAM-patch workflow below: stock CHR skips :beep under a
+# hypervisor, so an unpatched guest never emits audio.
+```
+
+#### `continue <name> [--no-wait] [--timeout-extra <s>]`
+
+Resume a machine started with `start --frozen` (held at reset with a
+gdbstub). Sends one monitor `cont`, then waits for RouterOS to become
+ready — the same promise `start` makes. `--no-wait` returns right after
+resuming; `--timeout-extra`/`-T` extends the resume timeout like `start`. Idempotent: when the guest is already running (e.g. gdb
+continued it), this just clears the frozen marker. A machine that never
+reaches readiness is a `BOOT_TIMEOUT`; it is stopped and preserved.
+
+`--frozen` exists for harnesses that must touch the guest before RouterOS
+init runs — e.g. patching guest RAM via gdb, then resuming:
+
+```sh
+quickchr start beep-lab --version 7.25 --arch x86 --frozen
+# frozen at reset; gdb at <machineDir>/gdb.sock (see 'quickchr list beep-lab')
+gdb -ex "target remote /path/to/machines/beep-lab/gdb.sock" \
+    -ex "set *(char *)0xADDR = 0x.." -ex detach -ex quit
+quickchr continue beep-lab
+# resumed, REST-ready
+```
+
+Frozen is per-boot intent, not config: `stop` clears it and a later plain
+`start` boots normally. `list` marks frozen machines (`(frozen)` in the
+table, a `Frozen:` line plus the gdb socket path in the detail view).
+Note the vocabulary overlap: this `frozen` (QEMU held at reset) is a
+different domain from QGA `fsfreeze-status` (guest filesystems frozen for
+snapshots).
+
 #### `stop [name | --all]`
 
 Power cut: sends SIGTERM to QEMU, waits up to 5 seconds, then SIGKILL if
@@ -320,7 +381,10 @@ repeat the original command rather than to run a bare `start`.
 
 Without a name: tabular summary of every machine. With a name: detailed
 view including credentials and connection tips. `--json` for
-machine-readable output.
+machine-readable output. A machine held by `start --frozen` shows
+`(frozen)` in the table and a `Frozen:` line with its gdb socket path in
+the detail view; single-machine `--json` carries `frozen` (and the recorded
+`qemuArgs`) alongside the other fields.
 
 A machine whose `machine.json` cannot be read — unreadable on disk, not valid JSON, or
 valid JSON that is not usable machine state — still appears, as a row marked
@@ -447,6 +511,8 @@ flags that were asked for so it can be run as given.
 | `--device-mode <m>` | `rose`, `advanced`, `basic`, `home`, `auto`. |
 | `--device-mode-enable <f,…>` | Set one or more device-mode flags to yes. Repeatable, comma-separated. |
 | `--device-mode-disable <f,…>` | Set one or more to no. |
+| `--qemu-arg <arg>` | Replace the recorded QEMU passthrough args (repeatable, space-form only). Stopped only; takes effect on the next start. |
+| `--clear-qemu-args` | Drop the recorded QEMU passthrough args. Stopped only. |
 
 **Device-mode restarts the machine.** RouterOS only applies a device-mode change
 across a power cycle, and quickchr owns the power button — which is why this lives
@@ -486,7 +552,7 @@ Interactive wizard (`@clack/prompts`) that walks through all machine creation
 options and starts the CHR. Triggered by `quickchr setup` or automatically
 when `quickchr` is run with no subcommand on a TTY.
 
-![quickchr setup wizard walkthrough](./images/wizard-demo.gif)
+![quickchr setup wizard walkthrough](./docs/images/wizard-demo.gif)
 
 **First-run detection**: if no machines exist yet, the wizard opens with a
 welcome message before the first prompt.
@@ -513,7 +579,10 @@ another machine, view status, or quit.
 | 12 | Run mode: background / foreground | background | (default) / `--fg` |
 | 13 | Final confirmation | — | — |
 
-Steps 7–9 are skipped when `qemu-img` is absent (a warning is shown). Step 10
+The wizard requires `qemu-img` and refuses before any prompts or image downloads
+when it is absent, showing the install remedy. For a raw x86 boot without `qemu-img`,
+use `quickchr add --arch x86 --boot-disk-format raw` to create a stopped machine,
+then `quickchr start <name>` with the returned name to boot it. Step 10
 only appears when the platform supports networks beyond user-mode (macOS or
 Linux). The provisioning gate (step 11) only appears for RouterOS ≥ 7.20.8;
 older versions show an upgrade prompt.
@@ -597,7 +666,7 @@ default output form when writing step outputs directly.
   process that wrote it is alive (an extraction: for 30 minutes after its last
   write). `prune` removes stale ones before anything else.
 
-`cache list --json` prints one object per entry, including `kind` (`image`, `image-zip`,
+`cache list --json` prints an array of entry objects, including `kind` (`image`, `image-zip`,
 `packages` or `partial`) and `paths` (every file deleting the entry removes).
 Files in the cache that quickchr did not write are reported as "Other files"
 and never deleted. `prune` and `clear` never delete an in-use entry.
@@ -690,7 +759,7 @@ mutate any machine's `machine.json`.
 
 | Env var | Effect |
 |---|---|
-| `QUICKCHR_DATA_DIR` | Override the data root (defaults to `$XDG_DATA_HOME/quickchr` or platform equivalent — see §8) |
+| `QUICKCHR_DATA_DIR` | Override the data root (defaults to `~/.local/share/quickchr` on POSIX or the Windows path — see §8) |
 | `QUICKCHR_NO_PROMPT` | Force non-interactive mode (skips all wizards) |
 | `QUICKCHR_DEBUG` | Emit `[debug]` lines from the progress logger |
 | `QUICKCHR_INTEGRATION` | Required to run `test/integration/` |
@@ -814,7 +883,7 @@ throws `INVALID_NAME` for a name that is not a usable path segment.
 |---|---|---|
 | Identity | `name`, `state`, `ports`, `restUrl`, `sshPort`, `portBase` | Static metadata persisted in `machine.json` |
 | Capture | `captureInterface`, `hostGatewayIp` | Platform-correct values for TZSP capture (`tshark -i …`) and the guest→host address any UDP emitter targets |
-| Lifecycle | `waitForBoot()`, `waitFor(fn, ms?)`, `stop()`, `shutdown(opts?)`, `remove()`, `clean()`, `destroy()` | Boot readiness, custom polling, power-cut or guest-shutdown teardown |
+| Lifecycle | `waitForBoot()`, `waitFor(fn, ms?)`, `stop()`, `shutdown(opts?)`, `continue(opts?)`, `remove()`, `clean()`, `destroy()` | Boot readiness, custom polling, power-cut or guest-shutdown teardown, frozen resume |
 | Comms | `rest()`, `exec()`, `monitor()`, `serial()`, `qga()` | REST, RouterOS CLI, QEMU monitor, serial console, QGA (x86 only) |
 | Provisioning | `license()`, `setDeviceMode()`, `availablePackages()`, `installPackage()` | Post-boot configuration |
 | Files | `upload()`, `download()` | SCP transfer to/from the CHR |
@@ -836,6 +905,7 @@ interface ChrInstance {
   waitFor(condition: () => Promise<boolean>, timeoutMs?: number): Promise<boolean>;
   stop(): Promise<void>;      // power cut: SIGTERM, then SIGKILL
   shutdown(opts?: ShutdownOptions): Promise<ShutdownResult>; // /system/shutdown, bounded fallback
+  continue(opts?: ContinueOptions): Promise<void>; // resume a frozen start, REST-ready by default
   remove(): Promise<void>;
   clean(): Promise<void>;
   destroy(): Promise<void>;   // stop + remove
@@ -922,6 +992,8 @@ redact before logging or attaching to bug reports.
 | `installDeps` | boolean | — | **Deprecated, ignored.** Never installed anything; run `quickchr doctor` for install hints |
 | `dryRun` | boolean | `false` | Print QEMU command and exit |
 | `timeoutExtra` | number | `0` | Extra **milliseconds** added to boot timeout |
+| `qemuArgs` | string[] | — | Extra QEMU argv elements, one entry each, appended verbatim last. Recorded by `add()`; a `start()` value replaces stored args for that boot only |
+| `frozen` | boolean | `false` | Boot frozen at reset with a gdbstub; resume with `continue()`. Refused with provisioning or `background: false` |
 | `onProgress` | `(msg) => void` | `console.log` | `[debug]` lines only when `QUICKCHR_DEBUG=1` |
 
 Provisioning fields trigger a version check at the top of `start()` /
@@ -1257,10 +1329,10 @@ restrictions, half-open SLiRP under TCG), see `docs/networking.md`.
 
 ## 8. Storage layout
 
-### macOS / Linux (XDG)
+### macOS / Linux
 
 ```text
-$XDG_DATA_HOME/quickchr/  (defaults to ~/.local/share/quickchr/)
+~/.local/share/quickchr/
 ├── .allocate.lock/              held while a new machine picks its ports/MACs
 ├── cache/                       Downloaded RouterOS images
 │   ├── chr-7.22.1.img.zip
@@ -1283,8 +1355,8 @@ $XDG_DATA_HOME/quickchr/  (defaults to ~/.local/share/quickchr/)
     └── <name>.json
 ```
 
-`$XDG_DATA_HOME` defaults to `~/.local/share/quickchr/`. Override the
-whole tree with `QUICKCHR_DATA_DIR=/some/path`.
+The data root is `~/.local/share/quickchr/`; `XDG_DATA_HOME` does not
+change it. Override the whole tree with `QUICKCHR_DATA_DIR=/some/path`.
 
 **Global settings** live separately, under the XDG **config** tier, not this
 data tree: `~/.config/quickchr/quickchr.env` (dotenv-style). See §3's
@@ -1581,12 +1653,16 @@ ceiling.
 
 ### Boot disk
 
-Default format is **raw** (the image MikroTik ships). `--boot-size`
-auto-converts to **qcow2** before the first boot and resizes to the
-requested size. Requires `qemu-img` on the host.
+The CLI and wizard default to **qcow2**, converted from the raw MikroTik
+image before first boot. Creating qcow2 requires `qemu-img` even without resize.
+`--boot-size` resizes qcow2 to the requested size; explicitly selecting raw
+with a boot size is refused. Without `--boot-size`, qcow2 keeps the original
+image size and enables snapshots.
 
-`--boot-disk-format=qcow2` (without `--boot-size`) just keeps the
-default size but enables snapshots.
+Library callers default to **raw** unless `bootSize` implies qcow2. CLI users
+can select raw explicitly with `--boot-disk-format raw`. On x86, this permits
+creation without `qemu-img` when no resize or extra disks are requested. ARM64
+also needs `qemu-img` for its writable UEFI firmware disk.
 
 ### Extra disks
 

package/README.md

@@ -1,11 +1,5 @@
 # quickchr
 
-> **Experimental** — quickchr is under active development. Most testing has been on
-> macOS (Apple Silicon + Intel), with CI on Linux (x86_64 + aarch64). Windows support
-> is early-stage: unit tests pass on `windows-latest` CI, and a weekly sweep boots a real
-> CHR on Windows (TCG, anchor smoke subset only). Expect rough edges on Windows — bug
-> reports welcome.
-
 CLI and library to download, launch, and manage MikroTik CHR virtual machines via QEMU.
 
 ## Quick Start
@@ -14,7 +8,7 @@ CLI and library to download, launch, and manage MikroTik CHR virtual machines vi
 
 - [Bun](https://bun.sh) runtime
 - [QEMU](https://www.qemu.org) with `qemu-system-x86_64` and/or `qemu-system-aarch64`
-- `qemu-img` for disk resize and extra-disk features (`--boot-size`, `--add-disk`, `quickchr disk`)
+- `qemu-img` for default qcow2 creation, the setup wizard, disk resize, extra disks, and snapshots
 - UEFI firmware (edk2) for arm64 CHR
 
 Install QEMU:
@@ -60,7 +54,7 @@ bun add @tikoci/quickchr
 ### Prerelease QA (0.5.1)
 
 0.5.1 is published to npm `next` first; the unqualified install above uses `latest`,
-and 0.5.1 is promoted there once QA passes. After 0.5.1 is published, pin it for
+and 0.5.1 is promoted there once QA passes. Pin this published candidate for
 reproducible CLI or library QA:
 
 ```bash
@@ -77,7 +71,8 @@ The [0.5.0 notes](./CHANGELOG.md#050--2026-10-22) cover migration from 0.4.x.
 ### CLI Usage
 
 The easiest way to start is the interactive wizard — it walks through
-every option and starts the CHR for you:
+every option and starts the CHR for you. It requires `qemu-img` and reports
+a missing tool before prompting or downloading:
 
 ```bash
 quickchr setup
@@ -201,6 +196,7 @@ reports a forced power cut if the guest does not stop within the grace budget.
 | `--install-all-packages` | Install all packages from `all_packages.zip` | |
 | `--add-user <user:pass>` | Create a user after boot | |
 | `--disable-admin` | Disable the default admin account | |
+| `--secure-login` | Create a managed login; use `--disable-admin` to disable admin | |
 | `--no-secure-login` | Keep admin with no password (skip managed account creation) | |
 | `--add-network <spec>` | Add a network NIC (repeatable). Specs: `user`, `shared`, `bridged:<iface>`, `socket::<name>`, `tap:<iface>`. Default: single user NIC. | |
 | `--no-network` | Start with no NICs (headless) | |
@@ -260,7 +256,8 @@ In **foreground** mode, your terminal becomes the CHR serial console. Use these
 
 ### Disk Support
 
-- The CHR boot image starts as raw. Using `--boot-size` converts it to qcow2 and resizes it before first boot.
+- CLI and wizard boot disks default to qcow2, converted from the raw MikroTik image using `qemu-img`. Library callers default to raw unless `bootSize` implies qcow2.
+- `--boot-size` resizes qcow2 before first boot; explicitly combining raw with a boot size is refused.
 - Extra disks from `--add-disk` are always created as blank qcow2 images.
 - `quickchr clean <name>` removes any resized boot disk and extra disks, then recreates them from the saved machine config.
 - `quickchr disk <name>` shows the stored disk layout. If `qemu-img` is installed, it also shows virtual and actual sizes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tikoci/quickchr",
-  "version": "0.5.1",
+  "version": "0.5.3",
   "description": "CLI and library to download, launch, and manage MikroTik CHR virtual machines via QEMU",
   "module": "src/index.ts",
   "main": "src/index.ts",
@@ -15,6 +15,7 @@
     }
   },
   "files": [
+    ".bun-version",
     "src",
     "README.md",
     "DESIGN.md",

package/src/cli/flags.ts

@@ -20,12 +20,13 @@ const CREATE_FLAGS = [
 	"boot-disk-format", "boot-size", "add-disk",
 	"device-mode", "device-mode-enable", "device-mode-disable",
 	"add-user", "disable-admin", "secure-login",
+	"qemu-arg",
 ] as const;
 
 /** `start` also boots, so it owns the run-time flags on top of the create set. */
 const START_ONLY_FLAGS = [
 	"all", "dry-run", "wait", "background", "bg", "fg", "foreground",
-	"timeout-extra",
+	"timeout-extra", "frozen",
 	"license-level", "license-account", "license-password",
 ] as const;
 
@@ -40,6 +41,7 @@ const START_ONLY_FLAGS = [
 const SET_ONLY_FLAGS = [
 	"name", "license", "level", "account", "password",
 	"device-mode", "device-mode-enable", "device-mode-disable",
+	"qemu-arg", "clear-qemu-args",
 ] as const;
 
 export const ADD_FLAGS: readonly string[] = CREATE_FLAGS;
@@ -78,6 +80,7 @@ export const VALUE_FLAGS: ReadonlySet<string> = new Set([
 	"device-mode", "device-mode-enable", "device-mode-disable",
 	"add-user", "timeout-extra",
 	"license-level", "license-account", "license-password",
+	"qemu-arg",
 	// exec / qga / console
 	"via", "user", "password", "timeout", "path", "data", "script",
 	// set --license