Version Packages

[github-actions]

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

@tangle-network/agent-interface@1.5.0

Minor Changes

• e04c96c: Add commandTurnEvents, execResultFromUnknown, and execOnlyEnvironmentCapabilities to @tangle-network/agent-interface/environment-provider.
  They own the three rules every workspace-only environment adapter needs: the order a turn's command is resolved in and the refusal when none resolves, how a sandbox SDK's untyped command result is read and the refusal when it carries no exit status, and the capability document of an adapter that runs commands and moves files but owns no agent profile, stream, session, or branch.

  The ComputeSDK, Daytona, and E2B adapters now call those three instead of keeping a private copy each.
  Their published capability documents, turn events, and refusal messages are unchanged.

• 6397cbb: Add deepFreeze to @tangle-network/agent-interface.
  It owns the rule that a validated value handed to a caller must not be writable afterwards, and it skips a value it has already visited so a self-referring value is frozen once instead of recursing until the stack runs out.

  snapshotAgentProfile, parseCertifiedContext, the Tangle adapter's capability document, and the Tangle adapter's environment metadata snapshot now call it instead of keeping a private copy each.
  Two of those copies had no such guard and exhausted the stack on a value that referred to itself.

• 655a60f: Add sameAgentRunControlRef to @tangle-network/agent-interface.
  It owns the question "do these two references name the same run", and answers it over the reference's canonical form rather than a list of field names, so a reference that gains a coordinate is compared on it without a caller having to remember.

  The two cancellation and control acknowledgement matchers and the cli-bridge adapter's retained control and native continuation checks now call it instead of comparing by hand.

Patch Changes

• 22070e6: Give the candidate evidence schemas one owner for the rule that a captured artifact must be the canonical bytes of its material.
  The execution-plan and outcome schema modules each built that check by hand, so the artifact-hash and empty-artifact refusals were stated twice; they now come from one place.
  The published schemas accept and refuse exactly the same values, with the same issue paths and messages.
• a0d7d70: Give the durable workspace checkpoint and fork schemas one owner for the two rules they share.
  refuseSelfConflict states once that a conflict answer must name a different existing request, and operationResourceIdentityMatches states once that the checkpoint or forked environment an answer carries must repeat the key and digest of the operation that made it.
  The four result and lookup schemas now call them instead of restating each rule.
  The public types, the accepted and refused values, and every issue path and message are unchanged.

@tangle-network/agent-provider-computesdk@0.4.0

Minor Changes

• bd76ed8: Refuse a command result that carries no exit status instead of reading it as exit zero.

  Exit zero is the one value that means a command succeeded. A sandbox SDK that answers with captured output but no exitCode or code was read as zero, so environment.exec() reported success for a command whose outcome was never measured, and a turn over that command finished with status: "completed". A failing build that printed to stdout and returned no status read as a build that worked.

  Such a result now throws, naming the SDK call whose answer could not be read. A turn fails loudly rather than completing on evidence nobody has.

Patch Changes

• e04c96c: Add commandTurnEvents, execResultFromUnknown, and execOnlyEnvironmentCapabilities to @tangle-network/agent-interface/environment-provider.
  They own the three rules every workspace-only environment adapter needs: the order a turn's command is resolved in and the refusal when none resolves, how a sandbox SDK's untyped command result is read and the refusal when it carries no exit status, and the capability document of an adapter that runs commands and moves files but owns no agent profile, stream, session, or branch.

  The ComputeSDK, Daytona, and E2B adapters now call those three instead of keeping a private copy each.
  Their published capability documents, turn events, and refusal messages are unchanged.

• Updated dependencies [22070e6]

• Updated dependencies [e04c96c]

• Updated dependencies [6397cbb]

• Updated dependencies [655a60f]

• Updated dependencies [a0d7d70]

  • @tangle-network/agent-interface@1.5.0

@tangle-network/agent-provider-daytona@0.4.0

Minor Changes

• bd76ed8: Refuse a command result that carries no exit status instead of reading it as exit zero.

  Exit zero is the one value that means a command succeeded. A sandbox SDK that answers with captured output but no exitCode or code was read as zero, so environment.exec() reported success for a command whose outcome was never measured, and a turn over that command finished with status: "completed". A failing build that printed to stdout and returned no status read as a build that worked.

  Such a result now throws, naming the SDK call whose answer could not be read. A turn fails loudly rather than completing on evidence nobody has.

Patch Changes

• e04c96c: Add commandTurnEvents, execResultFromUnknown, and execOnlyEnvironmentCapabilities to @tangle-network/agent-interface/environment-provider.
  They own the three rules every workspace-only environment adapter needs: the order a turn's command is resolved in and the refusal when none resolves, how a sandbox SDK's untyped command result is read and the refusal when it carries no exit status, and the capability document of an adapter that runs commands and moves files but owns no agent profile, stream, session, or branch.

  The ComputeSDK, Daytona, and E2B adapters now call those three instead of keeping a private copy each.
  Their published capability documents, turn events, and refusal messages are unchanged.

• Updated dependencies [22070e6]

• Updated dependencies [e04c96c]

• Updated dependencies [6397cbb]

• Updated dependencies [655a60f]

• Updated dependencies [a0d7d70]

  • @tangle-network/agent-interface@1.5.0

@tangle-network/agent-provider-e2b@0.4.0

Minor Changes

• bd76ed8: Refuse a command result that carries no exit status instead of reading it as exit zero.

  Exit zero is the one value that means a command succeeded. A sandbox SDK that answers with captured output but no exitCode or code was read as zero, so environment.exec() reported success for a command whose outcome was never measured, and a turn over that command finished with status: "completed". A failing build that printed to stdout and returned no status read as a build that worked.

  Such a result now throws, naming the SDK call whose answer could not be read. A turn fails loudly rather than completing on evidence nobody has.

Patch Changes

• e04c96c: Add commandTurnEvents, execResultFromUnknown, and execOnlyEnvironmentCapabilities to @tangle-network/agent-interface/environment-provider.
  They own the three rules every workspace-only environment adapter needs: the order a turn's command is resolved in and the refusal when none resolves, how a sandbox SDK's untyped command result is read and the refusal when it carries no exit status, and the capability document of an adapter that runs commands and moves files but owns no agent profile, stream, session, or branch.

  The ComputeSDK, Daytona, and E2B adapters now call those three instead of keeping a private copy each.
  Their published capability documents, turn events, and refusal messages are unchanged.

• Updated dependencies [22070e6]

• Updated dependencies [e04c96c]

• Updated dependencies [6397cbb]

• Updated dependencies [655a60f]

• Updated dependencies [a0d7d70]

  • @tangle-network/agent-interface@1.5.0

@tangle-network/agent-core@0.9.5

Patch Changes

• fad0d56: Re-export the resilience, telemetry, transport, types, and utils modules from the package root by name-forwarding instead of by hand-listing every symbol.
  Each of those five root blocks restated its module's full export list exactly, so 152 names were maintained in two places and a symbol added to a module and not to the root list was reachable through its own subpath but silently missing from the root.
  The names both entry points serve are unchanged.

• b1ec6c5: Fix decodeToken on the @tangle-network/agent-core/auth/browser entry point returning mojibake for any non-ASCII claim.
  atob answers one byte per code unit, so its result is the token's raw bytes and not yet text; the browser decoder returned that byte string directly, turning José 中文 into José 中æ. The bytes are now decoded as UTF-8.

  tokens-browser.ts becomes the one owner of the portable half of the token surface — base64url decoding, decodeToken, getTokenTTL, and isTokenExpiringSoon — and tokens.ts builds on it instead of keeping a second copy of each, so the auth and auth/browser entry points cannot read one token two ways.
  The browser decoder no longer reaches for Buffer when atob is missing; it uses only atob and TextDecoder, which both a browser and Node provide.

• Updated dependencies [22070e6]

• Updated dependencies [e04c96c]

• Updated dependencies [6397cbb]

• Updated dependencies [655a60f]

• Updated dependencies [a0d7d70]

  • @tangle-network/agent-interface@1.5.0

@tangle-network/agent-provider-cli-bridge@0.9.6

Patch Changes

• 655a60f: Add sameAgentRunControlRef to @tangle-network/agent-interface.
  It owns the question "do these two references name the same run", and answers it over the reference's canonical form rather than a list of field names, so a reference that gains a coordinate is compared on it without a caller having to remember.

  The two cancellation and control acknowledgement matchers and the cli-bridge adapter's retained control and native continuation checks now call it instead of comparing by hand.

• Updated dependencies [22070e6]

• Updated dependencies [e04c96c]

• Updated dependencies [6397cbb]

• Updated dependencies [655a60f]

• Updated dependencies [a0d7d70]

  • @tangle-network/agent-interface@1.5.0

@tangle-network/agent-provider-tangle@0.13.2

Patch Changes

• 6397cbb: Add deepFreeze to @tangle-network/agent-interface.
  It owns the rule that a validated value handed to a caller must not be writable afterwards, and it skips a value it has already visited so a self-referring value is frozen once instead of recursing until the stack runs out.

  snapshotAgentProfile, parseCertifiedContext, the Tangle adapter's capability document, and the Tangle adapter's environment metadata snapshot now call it instead of keeping a private copy each.
  Two of those copies had no such guard and exhausted the stack on a value that referred to itself.

• Updated dependencies [22070e6]

• Updated dependencies [e04c96c]

• Updated dependencies [6397cbb]

• Updated dependencies [655a60f]

• Updated dependencies [a0d7d70]

  • @tangle-network/agent-interface@1.5.0