🚀 Release

[taras]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@tisyn/kernel@0.17.0

Minor Changes

• cfa66c7: Payload-sensitive replay support: EffectDescription gains optional input and sha fields, and two new helpers — payloadSha(value) computes bytesToHex(sha256(utf8(canonical(value)))) (isomorphic Node + browser via @noble/hashes); payloadIdentity(value) returns { input, sha } derived from a single canonical snapshot, guaranteeing the pair stays self-consistent under in-place mutation of the original value.

  Breaking pre-1.0: YieldEvent.description now carries input and sha for all payload-sensitive effects. Stored journal entries that omit sha for payload-sensitive effects now raise DivergenceError on replay (no legacy compatibility path). The two non-canonicalizable runtime-direct effects — stream.subscribe and __config — continue to omit both fields per scoped-effects spec §9.5.8.

  Adds @noble/hashes dependency.

Patch Changes

• @tisyn/ir@0.17.0
• @tisyn/validate@0.17.0

@tisyn/runtime@0.17.0

Minor Changes

• cfa66c7: Replay matching is now payload-sensitive. Chain-dispatched delegated dispatch records and compares against the post-max boundary descriptor (so a max middleware that transforms effectId or data produces a journal entry reflecting the transformed request); chain-dispatched short-circuit and runtime-direct dispatch use the source descriptor. stream.next is payload-sensitive; stream.subscribe and __config are non-canonicalizable per the amended spec and continue to journal { type, name } only.

  Breaking pre-1.0:

  • Workflows whose stored journals omit sha for payload-sensitive effects will fail replay with DivergenceError. Re-run the live execution to rebuild the journal under the new shape.
  • Effects.around no longer intercepts the runtime-direct effects __config, stream.subscribe, or stream.next — they bypass the user-facing Effects chain per scoped-effects §3.1.1. Workflows that incidentally observed these effectIds in middleware logs will no longer see them.
  • __config YieldEvents now write { type, name } only (no input, no sha); replay treats missing sha on stored __config entries as expected, mirroring stream.subscribe.

  The motivating failure this resolves: a stored result for one input now correctly diverges instead of silently substituting against a different live input. See scoped-effects spec §9.5.3 / §9.5.5 / §9.5.8 / §9.5.10 and RD-PD-031 / RD-PD-091.

• 6c83c81: scope inside an invokeInline body now creates an ordinary child scope (own Effection scope, own bindings, own handler middleware, own CloseEvent under laneId.{m}) instead of throwing. The scope child uses its own coroutineId for both journal and owner identity; the inline lane itself still produces no CloseEvent. Closes Design inline invocation support for scope #136.

Patch Changes

• Updated dependencies [6c83c81]
• Updated dependencies [cfa66c7]
  • @tisyn/effects@0.3.2
  • @tisyn/kernel@0.17.0
  • @tisyn/agent@0.17.0
  • @tisyn/transport@0.17.0
  • @tisyn/durable-streams@0.17.0
  • @tisyn/ir@0.17.0
  • @tisyn/validate@0.17.0

@tisyn/agent@0.17.0

Patch Changes

• Updated dependencies [6c83c81]
• Updated dependencies [cfa66c7]
  • @tisyn/effects@0.3.2
  • @tisyn/kernel@0.17.0
  • @tisyn/ir@0.17.0

@tisyn/claude-code@0.14.2

Patch Changes

• Updated dependencies [6c83c81]
  • @tisyn/effects@0.3.2
  • @tisyn/agent@0.17.0
  • @tisyn/code-agent@0.3.2
  • @tisyn/transport@0.17.0
  • @tisyn/ir@0.17.0
  • @tisyn/protocol@0.17.0

@tisyn/cli@0.6.4

Patch Changes

• Updated dependencies [cfa66c7]
• Updated dependencies [6c83c81]
  • @tisyn/runtime@0.17.0
  • @tisyn/transport@0.17.0
  • @tisyn/durable-streams@0.17.0
  • @tisyn/compiler@0.17.0
  • @tisyn/ir@0.17.0

@tisyn/code-agent@0.3.2

Patch Changes

• Updated dependencies [6c83c81]
  • @tisyn/effects@0.3.2
  • @tisyn/agent@0.17.0
  • @tisyn/transport@0.17.0
  • @tisyn/ir@0.17.0
  • @tisyn/protocol@0.17.0

@tisyn/codex@0.3.2

Patch Changes

• Updated dependencies [6c83c81]
  • @tisyn/effects@0.3.2
  • @tisyn/agent@0.17.0
  • @tisyn/code-agent@0.3.2
  • @tisyn/transport@0.17.0
  • @tisyn/ir@0.17.0
  • @tisyn/protocol@0.17.0

@tisyn/compiler@0.17.0

Patch Changes

• @tisyn/ir@0.17.0
• @tisyn/validate@0.17.0

@tisyn/dsl@0.4.9

Patch Changes

• @tisyn/ir@0.17.0

@tisyn/durable-streams@0.17.0

Patch Changes

• Updated dependencies [cfa66c7]
  • @tisyn/kernel@0.17.0

@tisyn/effects@0.3.2

Patch Changes

• 6c83c81: Updated invokeInline JSDoc to reflect that scope inside an inline body is now supported (creates an ordinary child scope, see tisyn-inline-invocation-specification.md §11.7). Nested-resource rejection notice unchanged.
• Updated dependencies [cfa66c7]
  • @tisyn/kernel@0.17.0
  • @tisyn/ir@0.17.0

@tisyn/protocol@0.17.0

Patch Changes

• @tisyn/ir@0.17.0

@tisyn/transport@0.17.0

Patch Changes

• Updated dependencies [6c83c81]
• Updated dependencies [cfa66c7]
  • @tisyn/effects@0.3.2
  • @tisyn/kernel@0.17.0
  • @tisyn/agent@0.17.0
  • @tisyn/ir@0.17.0
  • @tisyn/protocol@0.17.0
  • @tisyn/validate@0.17.0

@tisyn/validate@0.17.0

Patch Changes

• @tisyn/ir@0.17.0

@tisyn/ir@0.17.0