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

package/CHANGELOG.md

@@ -5,6 +5,18 @@ recorded here.
 
 ## Unreleased
 
+## 1.0.0-rc.35
+
+### Breaking
+
+- Exercise the organization contract from `@whooshbang/contracts@1.0.0-rc.23`
+  with `@whooshbang/sdk@1.0.0-rc.32` (FXO-2337). Mock administration routes,
+  response fields, fixture authorities and closure confirmation now use
+  organization terminology, including `/v1/organization`, `organization_id`
+  and `close-organization`.
+- Remove the former tenant route and field spellings without aliases. Update
+  consumer fixtures and SDK validators together with the integration.
+
 ## 1.0.0-rc.34
 
 - Upgrade the Hono runtime to 4.13.7 so consumers do not inherit the security

package/README.md

@@ -2,7 +2,7 @@
 
 Deterministic, in-memory WhooshBang V1 mock for local contract tests.
 It implements the WhooshBang-owned release candidate without a cloud
-account, network service, database, or production provider.
+organization, network service, database, or production provider.
 
 Run the current release candidate directly from the public npm registry:
 
@@ -31,9 +31,13 @@ const response = await mock.fetch(
 );
 ```
 
-The mock also executes the account-scoped administration contract. Use
+The organization contract batch pairs mock `1.0.0-rc.35` with contracts
+`1.0.0-rc.23` and SDK `1.0.0-rc.32`. Install that batch together after
+publication; the tenant rename has no old-route or old-field aliases.
+
+The mock also executes the organization-scoped administration contract. Use
 `humanSession` (or `otherHumanSession` for isolation tests) with
-`GET /v1/account`, `GET/POST /v1/projects`, and
+`GET /v1/organization`, `GET/POST /v1/projects`, and
 `GET /v1/projects/{project_id}`. Project creation atomically returns synthetic
 `test` and `live` environments and one `Default` notifier for each.
 
@@ -54,7 +58,7 @@ unavailable, and unsubscribe copy is rejected just as it is by the service.
 
 Subscriber data exports are available at
 `GET /v1/projects/{project_id}/subscribers/{subscriber_id}/data-export` through
-an account grant, account credential, or human session. The project-wide operation refuses a
+an organization grant, organization credential, or human session. The project-wide operation refuses a
 one-environment project credential, requires `subscriptions:read`,
 `messages:read`, and `machine-clients:read`, and returns a JSON attachment with
 caching disabled.
@@ -63,11 +67,11 @@ synthetic recipient-response and delivery records to exercise all three
 provenance sections; it does not reconstruct a complete activity history.
 WhooshBang-controller audit and service-log data are listed as exclusions.
 
-The same account authorities erase a subscriber through
+The same organization authorities erase a subscriber through
 `DELETE /v1/projects/{project_id}/subscribers/{subscriber_id}` when they carry
 all three corresponding write scopes. Repeats return the same empty `204`.
-`POST /v1/account/close` accepts only an administrator human session and the
-exact `close-account` confirmation; its repeat-safe result names any synthetic
+`POST /v1/organization/close` accepts only an administrator human session and the
+exact `close-organization` confirmation; its repeat-safe result names any synthetic
 customer-managed provider resource that still needs manual retirement.
 
 Project credentials also execute the customer-endpoint lifecycle under
@@ -133,16 +137,16 @@ reuses a published code and is told apart by `field_errors[].code`: a rejected
 credential is `request_invalid` with `provider_credential_invalid`, an occupied
 webhook is `request_invalid` with `webhook_takeover_required`, a replacement
 for another bot is `request_invalid` with `provider_identity_mismatch`, a bot
-any account already connected is `idempotency_conflict` with
+any organization already connected is `idempotency_conflict` with
 `provider_identity_claimed`, and rotating a WhooshBang-operated credential is
 `idempotency_conflict` with `credential_not_customer_owned`. The identity claim
-is global on purpose — a bot connected by one account is refused to every
+is global on purpose — a bot connected by one organization is refused to every
 other — and archiving or purging releases it, so a customer can always
 reconnect a bot it owns. Purge is repeat-safe and destroys custody; the mock
 does not drive the `provider_outcome_unknown` and `provider_retryable` arms.
 
 A `customer_managed` create has Telegram make a brand new bot on the
-administrator's own account. It carries no credential field at all, because the
+administrator's own Telegram account. It carries no credential field at all, because the
 new bot's token travels provider to service and never through a browser, a
 clipboard, this request, or any response. The connection comes back `pending`
 carrying a `setup`: a link the administrator opens, the moment it stops
@@ -234,9 +238,9 @@ All credentials are synthetic local fixtures:
 
 | Exported key | Bearer token | Identity |
 | --- | --- | --- |
-| `humanSession` | `human-session-token` | default account administrator |
-| `otherHumanSession` | `human-other-session-token` | isolated account administrator |
-| `account` | `account-credential-token` | default account API credential |
+| `humanSession` | `human-session-token` | default organization administrator |
+| `otherHumanSession` | `human-other-session-token` | isolated organization administrator |
+| `organization` | `organization-credential-token` | default organization API credential |
 | `projectTest` | `project-test-token` | default test project |
 | `liveProject` | `project-live-token` | default live project |
 | `projectA` | `project-a-token` | isolated test project A |

package/dist/core.d.ts

@@ -17,7 +17,7 @@ export declare const CONTRACT_MOCK_FIXTURE_ENVIRONMENTS: Readonly<{
     readonly testEnvironmentId: "environment_project_synthetic_test";
 }>;
 export declare const CONTRACT_MOCK_FIXTURE_CREDENTIALS: Readonly<{
-    readonly account: "account-credential-token";
+    readonly organization: "organization-credential-token";
     readonly grant: "oauth-grant-token";
     readonly humanSession: "human-session-token";
     readonly otherGrant: "oauth-grant-other-token";