rightsize 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,4 @@
+Copyright 2026 the rightsize authors
+
+Licensed under the Apache License, Version 2.0. See LICENSE for the full
+license text.

package/README.md

@@ -0,0 +1,255 @@
+# rightsize
+
+[![CI](https://github.com/ngriaznov/rightsize-node/actions/workflows/ci.yml/badge.svg)](https://github.com/ngriaznov/rightsize-node/actions/workflows/ci.yml)
+
+**Testcontainers-style integration testing on microVMs. No Docker required.**
+
+rightsize runs your integration-test containers as hardware-isolated
+[microsandbox](https://github.com/superradcompany/microsandbox) microVMs —
+one microVM per container — behind a strict-mode ESM TypeScript API whose
+flagship lifecycle is TC39 explicit resource management. The runtime
+self-provisions on first use (no install step), and a hand-rolled Docker
+backend covers the platforms microVMs can't reach.
+
+```ts runnable
+import "rightsize/backend-msb";
+import "rightsize/backend-docker";
+import { RedisContainer } from "rightsize/modules";
+
+async function main(): Promise<void> {
+  await using redis = await RedisContainer.start(); // boots a real microVM
+  console.log("redis is up at", redis.uri); // redis://127.0.0.1:<mapped port>
+  // ... your test ...
+}
+
+await main();
+```
+
+`await using` is the whole story: `redis` is disposed automatically at the
+end of its scope — stopped, removed, its port freed — ordered and awaited,
+the same way a `try`/`finally` would, with none of the boilerplate.
+
+## Why microVMs
+
+| | Docker + Testcontainers | rightsize |
+|---|---|---|
+| Isolation | shared kernel (containers) | **hardware-level (microVM per container)** |
+| Runtime install | Docker Desktop / daemon required | **none — self-provisions on first use** |
+| Licensing | Docker Desktop licensing in orgs | Apache-2.0 all the way down |
+| Lifecycle | manual `try`/`finally` | **`await using` explicit resource management** |
+| Docker client | a general-purpose SDK over a shared HTTP stack | **hand-rolled, unix-socket-only — can't be misrouted onto TCP** |
+
+The lifecycle and Docker-client rows above aren't incidental implementation
+choices — see [Lifecycle](https://github.com/ngriaznov/rightsize-node/blob/main/docs/guide/lifecycle.md)
+and [Backends](https://github.com/ngriaznov/rightsize-node/blob/main/docs/guide/backends.md)
+for why each one is the way it is. (If you've used Testcontainers, the
+builder shape — `withEnv`, `withExposedPorts`, `waitingFor`, `getMappedPort`
+— will feel familiar; the lifecycle is where this library departs from it
+most.)
+
+## Quickstart
+
+```sh
+npm install --save-dev rightsize
+```
+
+Importing a backend subpath registers it as a side effect — import whichever
+one(s) you want considered, and `rightsize` picks the best supported one
+automatically (or `RIGHTSIZE_BACKEND` forces a specific one):
+
+```ts
+import "rightsize/backend-msb";
+import "rightsize/backend-docker";
+```
+
+Drive any image directly with `GenericContainer`, or use one of eighteen
+preconfigured modules:
+
+```ts
+import { GenericContainer, Wait } from "rightsize";
+
+await using arango = await new GenericContainer("arangodb:3.11")
+  .withEnv("ARANGO_NO_AUTH", "1")
+  .withExposedPorts(8529)
+  .waitingFor(Wait.forHttp("/_api/version").forPort(8529))
+  .start();
+
+const port = arango.getMappedPort(8529); // published on 127.0.0.1
+```
+
+Full guide: [Quickstart](https://github.com/ngriaznov/rightsize-node/blob/main/docs/guide/quickstart.md).
+
+## Modules
+
+Preconfigured containers with sensible waits and connection helpers. Each is
+a `GenericContainer` subclass, so the fluent builders (`withEnv`,
+`withExposedPorts`, `waitingFor`, …) are available on every one.
+
+| Module | Helpers |
+|---|---|
+| `RedisContainer` | `uri` |
+| `MemcachedContainer` | `address` |
+| `ArangoContainer` | `endpoint`; `withRootPassword(...)` to enable auth (default: no-auth) |
+| `MongoDBContainer` | `connectionString`, `replicaSetUrl` (alias) — single-node replica set, auto-initiated |
+| `PostgresContainer` | `connectionString`, `username`, `password`, `databaseName`; `withUsername`/`withPassword`/`withDatabase(...)` |
+| `MySQLContainer` | `connectionString`, `username`, `password`, `databaseName`; `withUsername`/`withPassword`/`withDatabase(...)` |
+| `MariaDBContainer` | `connectionString`, `username`, `password`, `databaseName`; `withUsername`/`withPassword`/`withDatabase(...)` |
+| `RedpandaContainer` | `bootstrapServers`, `schemaRegistryUrl` |
+| `KafkaContainer` | `bootstrapServers` — KRaft single node |
+| `RabbitMQContainer` | `amqpUrl`, `managementUrl`, `username`, `password`; `withUsername`/`withPassword(...)` — management plugin enabled |
+| `PinotContainer` | `controllerUrl`, `brokerUrl` — single-container QuickStart cluster |
+| `SpringCloudConfigContainer` | `uri` |
+| `WireMockContainer` | `baseUrl`, `adminUrl` — stub via the `/__admin` API |
+| `KeycloakContainer` | `authServerUrl`, `adminUsername`, `adminPassword`; `withAdminUsername`/`withAdminPassword(...)` |
+| `ClickHouseContainer` | `httpUrl`, `username`, `password`, `databaseName`; `withUsername`/`withPassword`/`withDatabase(...)` |
+| `Neo4jContainer` | `httpUrl`, `boltUrl`, `username`, `password`; `withPassword(...)` — HTTP Cypher endpoint (username fixed at `neo4j`) |
+| `FlociContainer` | `FlociContainer.aws()`/`.azure()`/`.gcp()` factories, `endpointUrl` — [floci.io](https://floci.io) cloud emulators (unsigned REST, no SDK needed) |
+| `FlinkContainer` | `restUrl`; `withTaskManager()` for a full session cluster — **Docker only**¹ |
+
+Some modules raise a memory floor for their image (`withMemoryLimit`):
+heavyweight JVM images — Spring Cloud Config, Keycloak, Neo4j, Flink
+(1024 MB) — and Pinot's multi-JVM QuickStart cluster (4096 MB) — need more
+than the microVM default. That's baked into the module; you don't set it.
+Every module's page under [`docs/modules/`](https://github.com/ngriaznov/rightsize-node/tree/main/docs/modules)
+documents its exact image tag, wait strategy, and the measured reasoning
+behind these choices.
+
+¹ `withTaskManager()` throws `UnsupportedByBackendError` on microsandbox (the
+Flink image carries no `nc`/busybox for network-link emulation — see
+[Networking](https://github.com/ngriaznov/rightsize-node/blob/main/docs/guide/networking.md));
+a bare JobManager still runs on microsandbox. Run TaskManager topologies
+under `RIGHTSIZE_BACKEND=docker`.
+
+## Backends
+
+rightsize picks a backend automatically; override with
+`RIGHTSIZE_BACKEND=microsandbox|docker`.
+
+| Platform | Backend used |
+|---|---|
+| macOS (Apple Silicon) | microsandbox (microVMs) |
+| Linux x86_64 / arm64 with `/dev/kvm` | microsandbox (microVMs) |
+| Windows x86_64 / arm64 (WHP enabled) | microsandbox (microVMs)¹ |
+| Intel Mac | Docker (auto-fallback) |
+| Windows without WHP | Docker (auto-fallback) |
+| Linux without KVM | Docker (auto-fallback) |
+
+¹ Verified in CI on `windows-2025` hosted runners, where Windows Hypervisor
+Platform is enabled by default. If WHP isn't enabled on your machine, run
+`msb doctor --fix` in an elevated terminal (may require a reboot) or use
+`RIGHTSIZE_BACKEND=docker`.
+
+Both backends satisfy one behavioral contract, verified by a shared test
+suite — the code you write runs unchanged on either. A few edges are
+backend-specific rather than behavioral divergences:
+
+- **Network-alias tunnels on microsandbox have real limits** versus Docker's
+  native bridge networking — see
+  [Networking](https://github.com/ngriaznov/rightsize-node/blob/main/docs/guide/networking.md).
+- **Read-only file mounts aren't enforced in-guest on microsandbox 0.6.3.**
+  `withCopyFileToContainer`'s read-only flag is honored by Docker; on
+  microsandbox the guest currently gets a writable mount regardless. Don't
+  rely on guest-side write protection under `RIGHTSIZE_BACKEND=microsandbox`.
+- **`followOutput` delivers the same ordered, no-duplicate log stream on
+  both backends**, but on microsandbox the final tail can arrive shortly
+  after the sandbox reports stopped, rather than exactly at stream EOF
+  (`msb logs -f` doesn't close on sandbox stop in 0.6.3, so the backend
+  replays the not-yet-delivered tail once stop is confirmed).
+
+## How it works
+
+- **Self-provisioning runtime.** A pinned `msb` release (binary + libkrunfw)
+  is downloaded once, SHA-256-verified against the release manifest, and
+  installed atomically under `~/.cache/rightsize/` (`%LOCALAPPDATA%\rightsize`
+  on Windows) — the binary lands last, so a crashed install is detected and
+  repaired, never half-trusted. A cross-process file lock keeps parallel
+  processes from racing.
+- **Attached-mode supervision.** Each container is a held child process
+  supervising its microVM; the image's ENTRYPOINT runs exactly as it would
+  under Docker.
+- **Pre-allocated ports.** Host ports are chosen before boot, so brokers
+  like Redpanda/Kafka get their advertised listeners baked in — no restart
+  dance. A backend binds the ports it's given; it never allocates its own.
+- **Two-tier cleanup, no async `Drop`.** The happy path is `await using` or
+  an explicit, awaited `stop()`. The fallback — a process that exits before
+  either runs — falls back to a synchronous, blocking teardown registered
+  per container (Node's `"exit"` handler can't `await`), with a run-id-scoped
+  orphan reaper at backend startup as the backstop for a hard `SIGKILL` that
+  bypasses even that.
+- **One interface, two backends.** `SandboxBackend` is a small interface;
+  the shared contract suite is the referee, with the Docker backend doubling
+  as the correctness oracle for the microVM backend.
+
+Full detail: [How It Works](https://github.com/ngriaznov/rightsize-node/blob/main/docs/guide/how-it-works.md).
+
+## Configuration
+
+| Env var | Effect |
+|---|---|
+| `RIGHTSIZE_BACKEND` | Force `microsandbox` or `docker` |
+| `MSB_PATH` | Use a pre-installed `msb` binary; skip downloads |
+| `RIGHTSIZE_CACHE_DIR` | Relocate the runtime cache (default `~/.cache/rightsize`; `%LOCALAPPDATA%\rightsize` on Windows) |
+| `RIGHTSIZE_MSB_SKIP_DOWNLOAD` | `true` = fail instead of downloading (air-gapped CI) |
+
+## Runtime support
+
+| Runtime | Minimum |
+|---|---|
+| Node.js | `>=22.11` (the 22.x "Jod" LTS line) |
+| Bun | `>=1.1` |
+
+Authored in TypeScript using `await using`; `tsc` emits ES2022 plus the
+downlevelled explicit-resource-management helpers, so the shipped
+`dist/**.js` runs unmodified on both runtimes with no flags.
+
+## Examples
+
+Three self-contained, runnable examples live under
+[`examples/`](https://github.com/ngriaznov/rightsize-node/tree/main/examples).
+Each builds the library once, then runs directly against the compiled
+`dist/` — no separate example-specific setup beyond `npm install`.
+
+| Example | What it shows | Run |
+|---|---|---|
+| [`redis-quickstart.ts`](https://github.com/ngriaznov/rightsize-node/blob/main/examples/redis-quickstart.ts) | The `await using` lifecycle — the library's signature | `npm run example:redis` |
+| [`network-alias.ts`](https://github.com/ngriaznov/rightsize-node/blob/main/examples/network-alias.ts) | Two containers on one `Network`, reachable by alias | `npm run example:network` |
+| [`redis.test.ts`](https://github.com/ngriaznov/rightsize-node/blob/main/examples/redis.test.ts) | A `node:test` suite using a module container, gated behind `RIGHTSIZE_IT=1` the same way this repo's own integration tests are | `npm run example:test` |
+
+Run all three back to back with `npm run examples:run`. Every example picks
+a backend automatically; force one explicitly the same way you would for
+any `rightsize` program:
+
+```bash
+RIGHTSIZE_BACKEND=docker npm run example:redis
+RIGHTSIZE_BACKEND=microsandbox npm run example:redis
+```
+
+`redis.test.ts` skips its container-backed assertions unless `RIGHTSIZE_IT=1`
+is set, so `npm run example:test` is safe to run on a machine with no
+container runtime — pass the flag to actually exercise it:
+`RIGHTSIZE_IT=1 npm run example:test`.
+
+## Development
+
+```bash
+npm install                                                # installs dependencies
+npm run build                                              # compiles src/ to dist/
+npm run typecheck                                          # tsc --noEmit
+npm test                                                    # unit suite, both runtimes
+npm run coverage:core                                       # core coverage, 80% line floor
+RIGHTSIZE_BACKEND=microsandbox npm run test:node:it         # needs Apple Silicon or Linux+KVM
+RIGHTSIZE_BACKEND=docker npm run test:node:it               # needs a reachable Docker daemon
+npm run docs:build                                          # static docs site
+npm run docs:verify                                         # typechecks every doc/README sample
+```
+
+CI runs the matrix on Linux (KVM), macOS (Apple Silicon), and a Docker-only
+job, both Node and Bun.
+
+See [`CONTRIBUTING.md`](https://github.com/ngriaznov/rightsize-node/blob/main/.github/CONTRIBUTING.md)
+for what each `tsconfig*.json` is for, the full npm script reference, and
+integration-test conventions.
+
+## License
+
+[Apache-2.0](LICENSE)

package/dist/backend-docker/backend.d.ts

@@ -0,0 +1,53 @@
+import type { FollowHandle, NetworkLink, SandboxBackend, SandboxHandle } from "../core/backend.js";
+import type { ContainerSpec, ExecResult } from "../core/model.js";
+import { DockerClient } from "./client.js";
+/**
+ * Drives the Docker daemon over `DockerClient`. This is also the
+ * correctness oracle other backends are checked against, since Docker
+ * enforces semantics (read-only mounts, native networks) microsandbox only
+ * emulates.
+ *
+ * Unlike the msb backend, a `SandboxHandle` here carries no companion
+ * mutable state keyed by id: every operation is a stateless HTTP call
+ * against the daemon-assigned container id already on the handle, so
+ * there's nothing to look up in a side table.
+ */
+export declare class DockerBackend implements SandboxBackend {
+    private readonly client;
+    /** `"docker"` — matched against `RIGHTSIZE_BACKEND`. */
+    readonly name = "docker";
+    readonly supportsNativeNetworks = true;
+    private readonly networkIds;
+    constructor(client: DockerClient);
+    /** Exposed for the transport regression test: the socket path this backend's client actually dials. */
+    socketPathForTest(): string;
+    private pullIfMissing;
+    private connectNetwork;
+    private ensureNetworkGetId;
+    create(spec: ContainerSpec): Promise<SandboxHandle>;
+    start(handle: SandboxHandle): Promise<void>;
+    stop(handle: SandboxHandle): Promise<void>;
+    remove(handle: SandboxHandle): Promise<void>;
+    exec(handle: SandboxHandle, cmd: ReadonlyArray<string>): Promise<ExecResult>;
+    logs(handle: SandboxHandle): Promise<string>;
+    /** Docker's stream ends cleanly on its own once the workload stops — unlike msb's `logs -f`, so no watchdog is needed here. */
+    followLogs(handle: SandboxHandle, consumer: (line: string) => void): Promise<FollowHandle>;
+    /** No-op: docker relies entirely on native networks (`ensureNetwork`/`create`'s connect step) — there is nothing to emulate here, unlike msb's exec-tunnel links. */
+    installNetworkLinks(_handle: SandboxHandle, _links: ReadonlyArray<NetworkLink>): Promise<void>;
+    ensureNetwork(networkId: string): Promise<void>;
+    removeNetwork(networkId: string): Promise<void>;
+    /** Removes every container carrying this run's label — the reaper safety net's normal-exit counterpart. */
+    close(): Promise<void>;
+    /**
+     * Synchronous, blocking teardown for the process-exit path. Node has no
+     * synchronous HTTP client, so this shells out to `curl --unix-socket` via
+     * `child_process.spawnSync` — curl ships on macOS and virtually every
+     * Linux CI image, and `spawnSync` genuinely blocks the exiting process the
+     * way the `"exit"` handler requires. If curl is unavailable, this is a
+     * silent no-op: the label-scoped orphan reaper each backend runs at
+     * startup (`close()`'s own reaping plus the next run's sweep) is the real
+     * safety net for that case, not this best-effort fast path.
+     */
+    cleanupSync(id: string): void;
+}
+//# sourceMappingURL=backend.d.ts.map

package/dist/backend-docker/backend.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"backend.d.ts","sourceRoot":"","sources":["../../src/backend-docker/backend.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,YAAY,EAAE,WAAW,EAAE,cAAc,EAAE,aAAa,EAAE,MAAM,oBAAoB,CAAC;AACnG,OAAO,KAAK,EAAE,aAAa,EAAE,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAElE,OAAO,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AA4F3C;;;;;;;;;;GAUG;AACH,qBAAa,aAAc,YAAW,cAAc;IAOtC,OAAO,CAAC,QAAQ,CAAC,MAAM;IANnC,wDAAwD;IACxD,QAAQ,CAAC,IAAI,YAAY;IACzB,QAAQ,CAAC,sBAAsB,QAAQ;IAEvC,OAAO,CAAC,QAAQ,CAAC,UAAU,CAA6B;gBAE3B,MAAM,EAAE,YAAY;IAEjD,uGAAuG;IACvG,iBAAiB,IAAI,MAAM;YAIb,aAAa;YAcb,cAAc;YAWd,kBAAkB;IAkC1B,MAAM,CAAC,IAAI,EAAE,aAAa,GAAG,OAAO,CAAC,aAAa,CAAC;IA0BnD,KAAK,CAAC,MAAM,EAAE,aAAa,GAAG,OAAO,CAAC,IAAI,CAAC;IAa3C,IAAI,CAAC,MAAM,EAAE,aAAa,GAAG,OAAO,CAAC,IAAI,CAAC;IAK1C,MAAM,CAAC,MAAM,EAAE,aAAa,GAAG,OAAO,CAAC,IAAI,CAAC;IAK5C,IAAI,CAAC,MAAM,EAAE,aAAa,EAAE,GAAG,EAAE,aAAa,CAAC,MAAM,CAAC,GAAG,OAAO,CAAC,UAAU,CAAC;IA0C5E,IAAI,CAAC,MAAM,EAAE,aAAa,GAAG,OAAO,CAAC,MAAM,CAAC;IA4BlD,+HAA+H;IACzH,UAAU,CAAC,MAAM,EAAE,aAAa,EAAE,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,GAAG,OAAO,CAAC,YAAY,CAAC;IAkDhG,qKAAqK;IAC/J,mBAAmB,CAAC,OAAO,EAAE,aAAa,EAAE,MAAM,EAAE,aAAa,CAAC,WAAW,CAAC,GAAG,OAAO,CAAC,IAAI,CAAC;IAE9F,aAAa,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAI/C,aAAa,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAQrD,2GAA2G;IACrG,KAAK,IAAI,OAAO,CAAC,IAAI,CAAC;IAa5B;;;;;;;;;OASG;IACH,WAAW,CAAC,EAAE,EAAE,MAAM,GAAG,IAAI;CAiB9B"}