feat(I203/M2): InvocationContext + streaming parity (post-I198/I199) #1
No reviewers
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
h-dv/ixt-sdk-nodejs!1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/i203-m2-invocation-streaming"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Mission I203 / M2 — Node.js SDK parity with Rust for InvocationContext (spec 21) + streaming (spec 23). Nested
ixt-publiceaf4205→117319c.InvocationContext(invocation.js: ActorIdentity/ActorSubject/MessageTarget/MetadataKeys);_handleMessagedecodesHandlePayload.context. Schemas consumed via hand-writtencapnp-tsStruct subclasses (the SDK doesn't run capnpc) — newschema-context.capnp.js+schema-streaming.capnp.jswith layouts derived fromcapnp compile. Fixed a pre-existing stale serialization test (JSON→Cap'n Proto since I140).streaming.js— StreamId/StreamData/StreamError, 6-variant StreamFrame union (encode+decode), StreamSender (sendData/close/cancel/error + credit/backpressure), StreamHandle (fromOpen+ InvocationContext decode), 4 InteractionKinds, 13-variant StreamErrorCode. No gold-plating.Tests:
npm testgreen — 62 (serialization 17, services 15, streaming 30). Byte-identical golden wire vectors with the Python/Rust SDKs (all 8 StreamFrame + 2 InvocationContext). Lockstep pin bump follows.🤖 Generated with Claude Code