@viceme-ai/sdk 0.6.1 → 0.6.2

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/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # @viceme-ai/sdk
2
2
 
3
- ViceMe browser SDK for Shop-hosted engagement and origin-bound Website Work access.
3
+ ViceMe browser SDK for Shop-hosted engagement and Website Work access.
4
4
 
5
5
  The release PR atomically owns the package version, runtime manifest, and
6
6
  changelog update. During the current preview stage, publication does not
@@ -86,6 +86,16 @@ use. They expose `client.auth`, `client.access`, and `client.checkout`; login,
86
86
  explicit follow, and hosted checkout remain ViceMe-owned UI. The host never
87
87
  receives a general ViceMe session or payment credential. Tests can inject a
88
88
  deterministic transport and presenter through `@viceme-ai/sdk/testing`.
89
+ Calling `client.destroy()` cancels in-flight access requests, closes the active
90
+ SDK-owned sign-in or checkout layer, and rejects the interrupted call with
91
+ `CLIENT_DESTROYED`; late responses cannot restore the in-memory Work token.
92
+
93
+ The current Website Access release accepts any valid HTTP(S) host Origin and
94
+ does not require DNS TXT verification. Session tokens remain bound to the
95
+ Origin observed when they were issued, but that Origin is not compared with a
96
+ registered allowlist. The hosted checkout iframe likewise has no parent-Origin
97
+ `frame-ancestors` restriction; its signed launch context, expiry, official
98
+ Shop URL, and server-authoritative entitlement checks remain enforced.
89
99
 
90
100
  Website access login renders the work-bound WeChat QR code directly in the SDK
91
101
  layer. Paid access keeps desktop QR payment and WeChat JSAPI in that layer;