@crvouga/mockingbird-service-docker 1.0.0 → 1.2.0

package/API_EVIDENCE.md

@@ -4,7 +4,7 @@ US-002 research, retrieved **2026-09-25 UTC**. Status: documentation and pinned
 source inspected; **historical research status, superseded by the US-013 live
 run recorded below**.
 This file defines a planned subset, not an implemented support claim. See
-[boundaries and scenario IDs](../../../docs/INFRASTRUCTURE_MOCKS.md).
+[boundaries and scenario IDs](../../../docs/INFRASTRUCTURE_EMULATORS.md).
 
 ## Compatibility target and provenance
 
@@ -73,7 +73,7 @@ limit includes non-running containers. Exited filtering requires a stopped
 container that has started. JSON filter maps accept legacy arrays and boolean
 sets (keys matter even if false); null denotes an empty map. Boolean query
 parsing is permissive: trimmed empty/0/no/false/none are false, other values true.
-The mock bounds name regex support as documented in README and returns explicit
+The emulator bounds name regex support as documented in README and returns explicit
 501 for other patterns/filters. No installed Engine or differential run was used.
 Pinned [container lookup](https://github.com/moby/moby/blob/710302ecf2e958db92cb7d92f8838ea063a31765/daemon/container.go)
 and [prefix lookup](https://github.com/moby/moby/blob/710302ecf2e958db92cb7d92f8838ea063a31765/daemon/container/view.go)
@@ -81,20 +81,20 @@ confirm full ID, exact name, then unique prefix precedence; ambiguous prefixes
 return InvalidParameter (400), while missing containers return 404.
 List status descriptions follow pinned S7 and its
 [duration formatter](https://github.com/moby/moby/blob/710302ecf2e958db92cb7d92f8838ea063a31765/vendor/github.com/docker/go-units/duration.go),
-using the injected mock clock rather than host process uptime.
+using the injected emulator clock rather than host process uptime.
 
 S2/S3 explain why the observed `/v1.52/containers/{id}/attach` and unversioned
 `/info` can belong to one client: every provider route is registered with and
 without a version, and an absent version uses the daemon default (1.52 here).
 Deprecation guidance is not evidence that this pinned daemon rejects `/info`.
 
-Planned mock policy: support v1.52 and unversioned aliases for the listed subset.
+Planned emulator policy: support v1.52 and unversioned aliases for the listed subset.
 Do not claim to emulate all older APIs merely because the real Engine accepts them.
 For numeric versions above 1.52, use the provider's too-new `400` error; versions
 below the default minimum 1.44 use its too-old `400` error. Versions 1.44–1.51
-are **unsupported by this mock subset**: return an explicitly Mockingbird-labelled
+are **unsupported by this emulator subset**: return an explicitly Mockingbird-labelled
 `501` message, not a fictional Engine rejection. Historical compatibility can only
-be expanded with new evidence. Document these mock-only 501 responses in codegen.
+be expanded with new evidence. Document these emulator-only 501 responses in codegen.
 
 Provider version-error message templates from S2 are:
 
@@ -107,7 +107,7 @@ S3 serializes errors as `{"message":"..."}` except requests below API 1.24,
 which receive plain text. Unknown paths/methods use `404` with
 `{"message":"page not found"}`. Malformed version paths are not a promise of
 version negotiation. No automatic client reconnection or fallback is part of
-the mock. Its declared API support must remain distinct from simulated Engine
+the emulator. Its declared API support must remain distinct from simulated Engine
 `MinAPIVersion` metadata.
 
 ## Planned operation contract
@@ -115,7 +115,7 @@ the mock. Its declared API support must remain distinct from simulated Engine
 Paths below are relative to `/v1.52`, also available unversioned as above.
 The status column is the pinned S1 vendor contract; additional implementation
 errors supported by pinned source must be annotated explicitly, not silently
-invented. Global version errors and mock-only unsupported-feature errors are
+invented. Global version errors and emulator-only unsupported-feature errors are
 separate from this table. Unless stated otherwise, vendor errors use
 `ErrorResponse` with required string `message`.
 
@@ -156,9 +156,9 @@ and [configuration merge](https://github.com/moby/moby/blob/710302ecf2e958db92cb
 establish image resolution, platform warnings, request-over-image environment
 and label precedence, command/entrypoint defaults, empty-entrypoint clearing,
 and `no command specified` (400). The selected 1.52 request fields come from S1.
-The mock stores launch/host/network configuration without executing it. Full
+The emulator stores launch/host/network configuration without executing it. Full
 daemon resource/network validation and image execution are excluded; the README
-lists the explicit supported subset and mock-only501 behavior. No real Engine
+lists the explicit supported subset and emulator-only501 behavior. No real Engine
 creation or host resource operation was performed.
 
 - S4/S6: a successful stop `204` follows backend completion. For delayed-stop
@@ -197,7 +197,7 @@ Upgrade: tcp
 D1/S1's old illustrative handshake uses raw-stream, but its framing prose and
 S4 agree on multiplexed-stream for upgraded non-TTY API >=1.42. S4's non-upgrade
 path really uses HTTP 200/raw-stream; it is deliberately excluded from initial
-mock serving. Fetch cannot represent the raw hijacked duplex connection.
+emulator serving. Fetch cannot represent the raw hijacked duplex connection.
 
 Output frames have an 8-byte header: stream byte (1 stdout, 2 stderr), three zero
 bytes, and a uint32 big-endian payload length, followed by exactly that many bytes.
@@ -219,7 +219,7 @@ execution remains necessary to establish observed fidelity.
 Excluded modes: TTY/PTY, websocket attach, non-upgrade attach, log replay
 (`logs=true`), exec, standalone logs/events, detach-key processing, image
 pull/build, real networking/volumes/__admin/health checks and arbitrary command execution.
-Unsupported modes receive explicit mock-only 501 errors before upgrade rather
+Unsupported modes receive explicit emulator-only 501 errors before upgrade rather
 than silently different successful behavior. Reset/checkout/shutdown terminate
 owned streams and waiters; handles are never serialized into Timeline state.
 
@@ -269,10 +269,10 @@ Pinned sources resolve the precise v1.52 semantics:
 - [signal.go](https://github.com/moby/moby/blob/710302ecf2e958db92cb7d92f8838ea063a31765/vendor/github.com/moby/sys/signal/signal.go) and [Linux map](https://github.com/moby/moby/blob/710302ecf2e958db92cb7d92f8838ea063a31765/vendor/github.com/moby/sys/signal/signal_linux.go): zero is invalid; kill restricts to the Linux map (1–31 and34–64). Real-time aliases are supported.
 - S4/S6 and [HTTP status mapping](https://github.com/moby/moby/blob/710302ecf2e958db92cb7d92f8838ea063a31765/daemon/server/httpstatus/status.go): malformed t returns an unclassified strconv error (500), while a stop signal parsing error is wrapped as System (500). Kill signal errors are InvalidParameter (400). Stop on an already stopped record returns304 before validating its signal.
 
-The mock holds stop/SIGKILL/forced-removal replies until explicit completion;
+The emulator holds stop/SIGKILL/forced-removal replies until explicit completion;
 acceptance and socket loss never prove retirement. Signal/timeout parameters are
 stored diagnostic metadata; fixture-controlled completion replaces process/timer
-scheduling. v is inert without modeled volumes; link removal is explicit mock-only501.
+scheduling. v is inert without modeled volumes; link removal is explicit emulator-only501.
 Shared state/checkpoints and transient handles are reused. Fetch and real Node HTTP
 tests cover acceptance versus exit and response loss; no live Engine parity claimed.
 
@@ -283,7 +283,7 @@ limit, receive timeouts and retained connections. The Docker-local transport use
 these Node facilities plus its own bounded body collector and owned connection
 set. [Node IPC sockets](https://nodejs.org/api/net.html#ipc-support) define local
 path serving and normal server-close cleanup. Transport bounds and path refusal
-are explicit mock controls, not assertions of Docker daemon limits. Verification
+are explicit emulator controls, not assertions of Docker daemon limits. Verification
 uses synthetic project-local Unix sockets and TCP, including a built-entry fixture
 executed under Node; it does not use Linux peer credentials or a real Engine.
 
@@ -323,7 +323,7 @@ and Unix. All mutations, inspections, setup and completion travel through HTTP;
 Node attachment handles supply scripted output/input observation. Both transports
 exercise accepted create/start/stop/kill/remove response loss and re-inspection,
 retained ordinary HTTP connections and fragmented attach with exact binary frames.
-This is independent client/protocol evidence against the mock, not a real Engine
+This is independent client/protocol evidence against the emulator, not a real Engine
 oracle or evidence of the external consumer's retry policy.
 
 OpenAPI walks assert eligible planned/exercised operation coverage. A seeded
@@ -376,7 +376,7 @@ wait results and post-removal 404. The three named/labeled containers were confi
 absent during cleanup. The [captured JSON report](evidence/engine-29.8.0-api-1.52.json)
 retains actual/model values, image identity, exact Engine version and cleanup.
 
-An earlier attempt failed at mock image seeding before creating any container:
+An earlier attempt failed at emulator image seeding before creating any container:
 the PostgreSQL image contained unsupported metadata and declared storage. The
 harness now rejects declared volumes/active healthchecks and projects only modeled
 image defaults, recording omitted metadata. The successful fixture omitted
@@ -384,9 +384,9 @@ image defaults, recording omitted metadata. The successful fixture omitted
 published and no config-equivalence claim covers those fields.
 
 Normalization excludes dynamic IDs/timestamps, daemon identity/platform fields,
-frame/packet boundaries and cross-channel interleaving. The mock scripts expected
+frame/packet boundaries and cross-channel interleaving. The emulator scripts expected
 process completion; it never executes the image. Existing synthetic response-loss
 checks remain separate from real Engine execution. Daemon restart/live-restore,
 host isolation, SDKs, all API 1.56 features and external consumer policies remain
-unverified. The historical mock discovery profile remains explicit; this narrow
+unverified. The historical emulator discovery profile remains explicit; this narrow
 live run does not certify every operation/response field against every newer Engine.

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog — @crvouga/mockingbird-service-docker
 
+## 1.2.0 (2026-10-09)
+
+### Features
+
+- match Emulate provider coverage ([16b65ce](https://github.com/crvouga/mockingbird/commit/16b65ce791fa216f28ec1521df636f57771d9c5e))
+
+### Dependencies
+
+- `@crvouga/mockingbird-service-sqlite`
+
+## 1.1.0 (2026-10-08)
+
+### Features
+
+- redesign emulator experience ([d6038c2](https://github.com/crvouga/mockingbird/commit/d6038c27eebbaa1751f02bc9305002a5b1304779))
+
 ## 1.0.0 (2026-10-07)
 
 ### ⚠️ Breaking changes

package/DISCOVERY.md

@@ -1,7 +1,7 @@
 # @crvouga/mockingbird-service-docker discovery
 
 This is the installed-package index for coding agents and tooling. All relative links resolve
-inside `node_modules/@crvouga/mockingbird-service-docker/`; no repository checkout is needed to discover the mock's
+inside `node_modules/@crvouga/mockingbird-service-docker/`; no repository checkout is needed to discover the emulator's
 supported surface or documented behavior.
 
 ## Capability and behavior sources
@@ -47,7 +47,7 @@ designed for assertions and diagnosis by consuming test suites.
 ## Report a mismatch or missing capability
 
 Follow the [agent reporting contract](https://github.com/crvouga/mockingbird/blob/main/docs/REPORTING_ISSUES.md). Include package version,
-operation/command, a minimal redacted request, actual mock result, expected oracle result or vendor
+operation/command, a minimal redacted request, actual emulator result, expected oracle result or vendor
 documentation, and whether the mismatch appears in the matrix. Never include keys, tokens,
 customer data, prompts, PHI, card data, or unredacted recordings.
 

package/ORACLE.md

@@ -67,7 +67,7 @@ wait exit code, attach upgrade headers and stdout/stderr bytes. Multiplexed outp
 is decoded independently and concatenated by channel, removing arbitrary frame
 and packet boundaries. Output bytes are recorded as base64. Container IDs,
 timestamps, daemon-specific metadata and cross-channel interleaving are not
-compared. The mock's completion control scripts the known exit behavior; it does
+compared. The emulator's completion control scripts the known exit behavior; it does
 not execute the image. Tests of image execution or host isolation are not implied.
 
 The harness performs no daemon restart or live-restore operation. Existing

package/README.md

@@ -1,8 +1,8 @@
 # @crvouga/mockingbird-service-docker
 
-> Familiar calls. Faithful echoes. Part of [Mockingbird](https://github.com/crvouga/mockingbird).
+> Local emulators. Real API contracts. Part of [Mockingbird](https://github.com/crvouga/mockingbird).
 
-Work-in-progress Docker Engine API 1.52 mock. It implements GET/HEAD `/_ping`,
+Work-in-progress Docker Engine API 1.52 emulator. It implements GET/HEAD `/_ping`,
 GET `/version`, `/info`, `/containers/json`, and `/containers/{id}/json`, plus
 Mockingbird's shared runtime controls. POST `/containers/create` persists a stopped
 container. Start, wait, stop, kill, and removal use explicit simulated completion.
@@ -38,7 +38,7 @@ HTTP clients can target `http://127.0.0.1:8826`. A Docker client using `DOCKER_H
 can select `tcp://127.0.0.1:8826`. Unversioned and `/v1.52` provider routes work.
 Versions above 1.52 or below the simulated Engine minimum 1.44 receive provider
 400 errors (plain text below 1.24, JSON otherwise). Versions 1.44–1.51 receive an
-explicit mock-only 501: their wire formats are not implemented. The mock reports
+explicit emulator-only 501: their wire formats are not implemented. The emulator reports
 a synthetic Engine 29.1.0 identity; this is not a required local Docker version.
 Selected API 1.52 scenarios passed against Engine 29.8.0; full client and Engine
 compatibility are not claimed. See [verification boundaries](#verification-boundaries).
@@ -95,7 +95,7 @@ or exact tag. Duplicate IDs, names and image tags conflict; unknown images retur
 fields also accept `exitCode`, `entrypoint`, `env`, `workingDir`, `user`,
 `hostConfig`, `networkSettings`, `sizeRw`, and `sizeRootFs`. Status is one of
 `created`, `running`, `paused`, `restarting`, `removing`, `exited`, or `dead`.
-Timestamps use the mock clock; reported PIDs are zero, never host processes.
+Timestamps use the emulator clock; reported PIDs are zero, never host processes.
 
 `GET /__admin/docker/daemon` reports `{ available, rootless, simulated: true }`.
 `POST` to the same route changes either boolean. `available: false` drops provider
@@ -113,7 +113,7 @@ other values mean true. Inspect resolves full IDs, unique prefixes, and names.
 `status`, `label`, and `exited`. Categories combine with AND; values within a
 category combine with OR, except labels which all must match. Name matching
 supports literals, dots, anchors, and at most one `.*`; other regex constructs
-and other filter categories return explicit mock-only 501 errors. Malformed
+and other filter categories return explicit emulator-only 501 errors. Malformed
 filter shapes, statuses and exit codes return 400. Seeded state and daemon
 settings participate in shared reset and Timeline checkpoints.
 
@@ -129,7 +129,7 @@ The supported body fields are `Image`, `Cmd`, `Entrypoint`, `Env`, `Labels`,
 `WorkingDir`, `User`, `Hostname`, `Domainname`, `AttachStdin`, `AttachStdout`,
 `AttachStderr`, `OpenStdin`, `StdinOnce`, `Tty`, `NetworkDisabled`, `StopSignal`,
 `StopTimeout`, `HostConfig`, and `NetworkingConfig`. Unsupported fields return
-explicit mock-only 501 errors. Bad field types, relative working directories,
+explicit emulator-only 501 errors. Bad field types, relative working directories,
 invalid stop signals, invalid names, and missing commands return 400.
 Image defaults supply commands/entrypoints, environment, labels and selected
 strings. Request environment keys and labels take precedence. `Entrypoint: [""]`
@@ -157,7 +157,7 @@ network validation is not modelled. No host isolation claim follows from it.
 returns 304 when already running/restarting, and returns 409 for paused, dead,
 or removing records. No image is executed. The clock supplies `StartedAt`;
 restart clears the exit code but retains the prior `FinishedAt` until completion.
-Checkpoint, checkpoint-dir and detachKeys options return explicit mock-only 501.
+Checkpoint, checkpoint-dir and detachKeys options return explicit emulator-only 501.
 As in the pinned Engine route, bodies longer than seven bytes and chunked bodies
 return 400; use an empty body.
 
@@ -195,7 +195,7 @@ checks selected wait and termination outcomes; cancellation coverage is syntheti
 finishes execution, then returns 204. Already-stopped containers return 304.
 `signal` selects the requested signal (default Config.StopSignal or TERM); `t`
 selects the timeout (default Config.StopTimeout or 10 seconds; negative means no
-escalation timeout). The mock records these parameters for scenario inspection.
+escalation timeout). The emulator records these parameters for scenario inspection.
 It does not schedule real timers or automatically declare exit when a timeout
 expires: script graceful completion or forced completion, including the exit code,
 through `/__admin/docker/containers/<id>/complete`. This permits controlled delayed
@@ -207,7 +207,7 @@ signal names/numbers acknowledge delivery with 204 while preserving execution
 state. The fixture decides the subsequent process response. No host signal is
 sent. Killing a stopped container returns 409. Invalid kill signals return 400;
 pinned Engine stop signal errors and malformed `t` return 500. Timeouts outside
-JavaScript's safe integer range return explicit mock-only 501.
+JavaScript's safe integer range return explicit emulator-only 501.
 
 `DELETE /containers/<id>` removes a stopped record and releases its name (204).
 Running or paused records require `force=true`; otherwise removal returns 409.
@@ -215,7 +215,7 @@ Forced removal records intent and waits for explicit completion, then removes th
 record and wakes both exit and removed waiters. A second removal while forced
 removal is pending returns 409. Seed status `removing` to model an existing removal
 conflict. Missing records return 404. `v` is accepted but no host volumes exist;
-`link=true` is outside this subset and returns mock-only 501.
+`link=true` is outside this subset and returns emulator-only 501.
 
 `GET /__admin/docker/containers/<id>/termination` returns the last accepted request
 (operation, numeric signal, optional timeout and request time), `removalPending`,
@@ -270,7 +270,7 @@ Type exports include `DockerAPIOptions`, `DockerRuntime`, `DockerRuntimeOptions`
 ## Deliberately not modelled
 
 Fetch attach and unsupported options return Mockingbird-specific 501 JSON errors;
-unknown routes return 404. The mock never starts real containers or executes
+unknown routes return 404. The emulator never starts real containers or executes
 commands. The Node server supports the documented non-TTY attach handshake and
 scripted duplex streams; a Fetch response cannot represent that upgrade.
 
@@ -359,7 +359,7 @@ already-framed bytes to the last fragment. This does not promise OS packet
 boundaries. The bytes are caller-owned wire fixtures, not generated container
 output. Use the live attachment controls below for framing, channel routing and scripted
 stdin. No command interprets the input, and payload bytes never enter the journal. Connection loss does not stop the container.
-Owned sockets close on server shutdown. The mock never connects to a real Engine;
+Owned sockets close on server shutdown. The emulator never connects to a real Engine;
 the separately invoked oracle performs the authorized provider comparison.
 
 ## Scripted attach streams
@@ -411,7 +411,7 @@ stale writes reject. Socket handles and buffered payloads are never snapshotted.
 `attachStreams.maxQueuedBytes` and `maxStdinBytes` default to 1 MiB. Queued output
 includes frame headers; exceeding the output limit rejects the write. Exceeding
 unread stdin capacity cancels that attachment. Stream limits must be positive
-integers no greater than 16 MiB. These bounds are mock resource controls.
+integers no greater than 16 MiB. These bounds are emulator resource controls.
 
 ## Verification boundaries
 
@@ -429,7 +429,7 @@ requests on a retained connection and raw attach bytes. It verifies lost create
 and start responses, lookup by name, duplicate-name conflict, framed binary
 stdout/stderr, raw stdin, continued execution after attachment loss, and lost
 stop/kill/remove responses followed by completion and re-inspection. Setup and
-completion use public mock admin controls; attachment handles only script output
+completion use public emulator admin controls; attachment handles only script output
 and observe synthetic stdin. Public request metadata confirms each dropped mutation
 was accepted and checkpointed. No client assertion imports provider handlers or
 internal state. The fixture never automatically retries a mutation.

package/SUPPORT.md

@@ -3,10 +3,10 @@
 Generated from `openapi.yaml`; do not edit by hand.
 
 - operations in spec: **13**
-- supported by the mock: **12**
+- supported by the emulator: **12**
 - parity enabled: **8**
 
-| operationId | route | mock | parity | notes |
+| operationId | route | emulator | parity | notes |
 | --- | --- | --- | --- | --- |
 | `ContainerList` | `GET /containers/json` | ✅ supported | ✅ |  |
 | `ContainerCreate` | `POST /containers/create` | ✅ supported | ⚠️ unsafe (opt-in) |  |