zeekay 3156793826 fix(sdk): accept ZAP wire v2 (luxfi/zap v1.2.0) + drop-in gaps; engine: CAN-chain describe ...

The cloud embedded engine links luxfi/zap v1.2.0 via MVS, whose NewBuilder stamps
wire version 2; the TS SDK only accepted version 1 -> 'unsupported version 2'
against cloud's gated :9999. The generic object encoding is byte-identical across
v1/v2 (only the platformvm TxKind schema differs, which this SDK never uses) and
v1.2.0's Parse accepts v1, so: keep emitting v1 (both engines accept it), accept
BOTH 1 and 2 on read. Verified live against cloud v1.786.102.

Also (drop-in compat, from the social migration):
- export TokenProvider from the package root.
- proxyActivities<A>: open the generic so proxyActivities<SomeActivityClass>()
  type-checks; ProxyActivityOptions accepts cancellationType (no-op).
- engine.moreCurrentRun: a CONTINUED_AS_NEW run ranks below any other run of the
  same workflowId, so the completed tail of a continue-as-new chain resolves over
  its closed predecessor on a same-second StartTime (DescribeWorkflow by id).

2026-07-04 22:11:10 -07:00

126 KiB

Raw Permalink History

View Raw