@whooshbang/contract-mock 1.0.0-rc.35 → 1.0.0-rc.37

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -5,6 +5,24 @@ recorded here.
5
5
 
6
6
  ## Unreleased
7
7
 
8
+ ## 1.0.0-rc.37
9
+
10
+ ### Added
11
+
12
+ - Exercise `@whooshbang/contracts@1.0.0-rc.25` with `@whooshbang/sdk@1.0.0-rc.34`.
13
+ The environment recipient policy answers `connectable_channels` from the
14
+ mock's own routes and connections, by the same test its recipient sessions
15
+ apply (FXO-2638).
16
+ - An unconfigured project's recipient brand is named "My App", as the service
17
+ now answers, rather than the project's internal name (FXO-2621).
18
+
19
+ ## 1.0.0-rc.36
20
+
21
+ ### Added
22
+
23
+ - Exercise `@whooshbang/contracts@1.0.0-rc.24` with `@whooshbang/sdk@1.0.0-rc.33`,
24
+ including the `internal_error` problem default (FXO-2612).
25
+
8
26
  ## 1.0.0-rc.35
9
27
 
10
28
  ### Breaking
package/README.md CHANGED
@@ -308,3 +308,16 @@ must send that exact token in `WhooshBang-Contract-Mock-Token`.
308
308
  Control routes are absent from OpenAPI and from the Worker-compatible entry.
309
309
  Never expose the CLI control listener or fixture credentials as a production
310
310
  service.
311
+
312
+ ## Customer email consent fixtures
313
+
314
+ The programmatic mock accepts `emailConsentAuthorities` for testing
315
+ `assertEmailConsent` and its environment-scoped SDK/MCP form. Each fixture names
316
+ `organizationId`, `projectId`, `environment`, `connectionId`, `domainId` and
317
+ `notifierId`, plus `mode`, `domainLifecycle`, `oauthHealthy`, `webhookPresent` and
318
+ `authorized`. Only a `customer_managed`, `active`, healthy and authorized fixture
319
+ permits assertion. Optional `held` and case-sensitive `blockedAddresses` exercise
320
+ sending restrictions. With no authority fixture the operation refuses safely.
321
+ The mock keeps original consent and actor evidence on retries and rejects
322
+ conflicting consent, future timestamps and noncanonical addresses. These are
323
+ local fixtures; they never create provider resources or send email.