@crvouga/mockingbird-service-daily 3.0.0 → 3.2.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog — @crvouga/mockingbird-service-daily
 
+## 3.2.0 (2026-10-09)
+
+### Features
+
+- match Emulate provider coverage ([16b65ce](https://github.com/crvouga/mockingbird/commit/16b65ce791fa216f28ec1521df636f57771d9c5e))
+
+### Dependencies
+
+- `@crvouga/mockingbird-service-sqlite`
+
+## 3.1.0 (2026-10-08)
+
+### Features
+
+- redesign emulator experience ([d6038c2](https://github.com/crvouga/mockingbird/commit/d6038c27eebbaa1751f02bc9305002a5b1304779))
+
 ## 3.0.0 (2026-10-07)
 
 ### ⚠️ Breaking changes
@@ -14,10 +30,6 @@
 - typecheck the brand gate before builds ([fc36095](https://github.com/crvouga/mockingbird/commit/fc3609514de70ffe3170a5d216fb8a49f9ce7cbb))
 - format the emulates records query ([8698872](https://github.com/crvouga/mockingbird/commit/8698872509d06002be5a8fcdc85d79f8462320c3))
 
-### Dependencies
-
-- `@crvouga/mockingbird-service-sqlite`
-
 ## 2.3.0 (2026-10-04)
 
 ### Features

package/DISCOVERY.md

@@ -1,7 +1,7 @@
 # @crvouga/mockingbird-service-daily discovery
 
 This is the installed-package index for coding agents and tooling. All relative links resolve
-inside `node_modules/@crvouga/mockingbird-service-daily/`; no repository checkout is needed to discover the mock's
+inside `node_modules/@crvouga/mockingbird-service-daily/`; no repository checkout is needed to discover the emulator's
 supported surface or documented behavior.
 
 ## Capability and behavior sources
@@ -48,7 +48,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/README.md

@@ -1,13 +1,13 @@
 # @crvouga/mockingbird-service-daily
 
-> 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).
 
-Stateful mock of the **Daily.co** REST API for test suites: rooms (create, get, update,
+Stateful emulator of the **Daily.co** REST API for test suites: rooms (create, get, update,
 delete, presence, eject), meeting tokens (mint and validate), verification of the HS256 meeting
 tokens our backend signs itself, and the end-of-call webhooks (`transcription.stopped`,
 `recording.ready-to-download`) with the transcript written to the stack's S3. Every EMR
 booking creates a room and a token; today a broken Daily integration is silent because booking
-swallows the error. Against the mock it is observable and assertable.
+swallows the error. Against the emulator it is observable and assertable.
 
 - Operation coverage: [SUPPORT.md](https://github.com/crvouga/mockingbird/blob/main/packages/service/daily/SUPPORT.md)
 - The contract (`openapi.yaml`) is trimmed from Daily's documented REST API to the calls our
@@ -25,7 +25,7 @@ any Fetch server.
 
 ## Usage
 
-Point the apps at the mock (the G-D1 seams):
+Point the apps at the emulator (the G-D1 seams):
 
 | App | Env | Value |
 | --- | --- | --- |
@@ -84,13 +84,13 @@ await admin("/rooms/<room name>/session", {
 | `GET /v1/rooms/:name/presence` | `{total_count, data: [{room, id, userId, userName, joinTime, duration}]}` — exactly the backend's strict schema. Participants come from `PUT /__admin/rooms/:name/presence`. |
 | `POST /v1/rooms/:name/eject` | `{user_ids?, ids?}` → `{ejectedIds}` (participant session ids), removing them from presence. |
 | `POST /v1/meeting-tokens` | `{properties}` → `{token}`: an HS256 JWT signed with the caller's API key, claims under Daily's abbreviations (`r`, `d`, `o`, `u`, `ud`, `nbf`, `exp`, `ejt`, `eje`, `er`, `erui`, `sr`, `ast`, `p`, …) plus `iat`. |
-| `GET /v1/meeting-tokens/:token` | Verifies a token (minted by the mock **or self-signed by our backend**) with the caller's API key and its `nbf`/`exp` on the mock clock (`?ignoreNbf=true` skips nbf); answers its properties under full names, else 400. |
+| `GET /v1/meeting-tokens/:token` | Verifies a token (minted by the emulator **or self-signed by our backend**) with the caller's API key and its `nbf`/`exp` on the emulator clock (`?ignoreNbf=true` skips nbf); answers its properties under full names, else 400. |
 
 **Auth.** `Authorization: Bearer <DAILY_API_KEY>`; any key unless `apiKeys` is set. Missing →
 401 `{error: "authentication-error"}`.
 
 **Milliseconds.** Some of our callers pass `nbf`/`exp` in milliseconds (e.g. the EMR's
-`generatePatientToken` passes `Date.parse(end)`). The mock accepts them, interprets values
+`generatePatientToken` passes `Date.parse(end)`). The emulator accepts them, interprets values
 ≥ 1e11 as ms in time checks, records each in `GET /__admin/warnings`, and tags the journal entry
 (`ids.warning: "exp in milliseconds"`).
 
@@ -107,7 +107,7 @@ payload}` (our receiver reads `event`; Daily documents `type`; both are sent).
 HMAC-SHA256(`DAILY_WEBHOOK_SECRET`, raw body), which is what our EMR verifies (only when the
 secret is set). Daily's documented scheme is different — base64 HMAC-SHA256 over
 `"<X-Webhook-Timestamp>.<body>"` with the base64-decoded secret — so a real Daily webhook would
-fail our check; the mock signs the way our code checks. `x-webhook-timestamp` is sent too.
+fail our check; the emulator signs the way our code checks. `x-webhook-timestamp` is sent too.
 Retries: immediately, 5 s, 5 min, 30 min, 2 h; `GET /__admin/webhooks`, `…/events`,
 `…/replay`, `…/flush` as usual.
 
@@ -117,12 +117,12 @@ Retries: immediately, 5 s, 5 min, 30 min, 2 h; `GET /__admin/webhooks`, `…/eve
 | --- | --- |
 | `POST /__admin/rooms/:name/session` | `{participants: [{userId, userName?}], durationSec, transcript?: [{s, t, ts, te}], sessionId?, recording?}` writes the transcript JSON to S3 at `{roomName}/{sessionId}.json` (SigV4 `PutObject` to the `--s3-endpoint` / `transcripts` target; a synthetic transcript alternating between participants when none is given), clears presence, then emits `transcription.stopped` (and `recording.ready-to-download` unless `recording: false`). Answers `{sessionId, s3Key, transcript: "s3://…" \| null, events}`; 502 when S3 refuses. The transcript text is never kept. |
 | `PUT /__admin/rooms/:name/presence` | `{participants: [{userId, userName?, joinedAt?}]}` — who `GET …/presence` reports. |
-| `POST /__admin/tokens/decode` | `{token, apiKey?}` → `{decodable, header, claims, properties, signatureValid, room, joinable, problems, warnings}`: signature (against `apiKey` or `apiKeys`), the backend's strict claim set, `ud` ≤ 36, domain id, ms timestamps, and the token and room `nbf`/`exp` windows on the mock clock (owners may enter before the room's `nbf`). |
+| `POST /__admin/tokens/decode` | `{token, apiKey?}` → `{decodable, header, claims, properties, signatureValid, room, joinable, problems, warnings}`: signature (against `apiKey` or `apiKeys`), the backend's strict claim set, `ud` ≤ 36, domain id, ms timestamps, and the token and room `nbf`/`exp` windows on the emulator clock (owners may enter before the room's `nbf`). |
 | `GET /__admin/rooms`, `GET /__admin/rooms/:name` | Rooms with config, presence and session metadata. |
 | `GET /__admin/warnings` | Tolerated oddities (millisecond timestamps, tokens for rooms that do not exist). |
 | `PUT /__admin/settings` | `{apiKeys?, domainId?, roomUrlBase?}` for the calling namespace (`GET` masks keys). |
 
-Time rules run on the mock clock (`POST /__admin/clock`): token/room `nbf` and `exp`, and
+Time rules run on the emulator clock (`POST /__admin/clock`): token/room `nbf` and `exp`, and
 therefore the backend's 13 h room-creation delay and 30-min guardrail window as seen by Daily.
 
 Fault presets (`POST /__admin/faults {"preset": "<name>", "count"?: n}`): `room_not_found`
@@ -147,8 +147,8 @@ Fault presets (`POST /__admin/faults {"preset": "<name>", "count"?: n}`): `room_
 
 | Export | Kind | Description |
 | --- | --- | --- |
-| `DailyAPI` | class | The in-process mock: `fetch(request)`, `reset()`, `inspectToken(token, keys?)`, `setPresence(name, participants)`, `endSession(name, input)`, `rooms()`. Options: `sqlite`, `now`, `namespace`, `settings`, `onWebhook`, `transcripts`. |
-| `createRuntime` | function | The mock with the full service contract. Options: `webhooks: {url, secret, retryDelaysMs?, fetch?}`, `transcripts: {endpoint, bucket, region?, accessKeyId?, secretAccessKey?, keyPattern?, fetch?}`, `settings`, `clock`, `seed`, `adminKey`, `onLog`. |
+| `DailyAPI` | class | The in-process emulator: `fetch(request)`, `reset()`, `inspectToken(token, keys?)`, `setPresence(name, participants)`, `endSession(name, input)`, `rooms()`. Options: `sqlite`, `now`, `namespace`, `settings`, `onWebhook`, `transcripts`. |
+| `createRuntime` | function | The emulator with the full service contract. Options: `webhooks: {url, secret, retryDelaysMs?, fetch?}`, `transcripts: {endpoint, bucket, region?, accessKeyId?, secretAccessKey?, keyPattern?, fetch?}`, `settings`, `clock`, `seed`, `adminKey`, `onLog`. |
 | `DAILY_PRESETS` | object | Every named fault preset. |
 | `DAILY_NAMESPACE` | string | The service name, `"daily"`. |
 | `WEBHOOK_PATH` | string | `"/v1/webhooks/daily"`, our EMR receiver's route. |

package/SUPPORT.md

@@ -3,10 +3,10 @@
 Generated from `openapi.yaml`; do not edit by hand.
 
 - operations in spec: **9**
-- supported by the mock: **9**
+- supported by the emulator: **9**
 - parity enabled: **9**
 
-| operationId | route | mock | parity | notes |
+| operationId | route | emulator | parity | notes |
 | --- | --- | --- | --- | --- |
 | `ListRooms` | `GET /v1/rooms` | ✅ supported | ✅ |  |
 | `CreateRoom` | `POST /v1/rooms` | ✅ supported | ⚠️ unsafe (opt-in) |  |