Repository navigation
feat: release SDK 1.2 workflows, tool streams and LSP - #28
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SDK consumers can now compose approved command jobs into bounded workflows, reuse deterministic results and connect operator-owned tools and language servers through public contracts. The 1.2.0 release adds DAG validation, per-step grants, durable CAS checkpoints and explicit new-attempt recovery; scoped content fingerprints, TTL/LRU cache and incremental execution; portable bounded output parsing plus a fixed Node process runner; and an optional stdio LSP 3.17 bridge covering 15 SDK language features.
Seven optional exports include TypeScript declarations, eleven schemas and independent installed examples. The tool-output parser works in the browser; workflow/cache/process/LSP execution is Node-only. Synthetic tools are SDK-authored and redistributable. Actual checks use TypeScript 5.9.3 and the community language server 5.3.0 as development dependencies, leaving the SDK with zero runtime dependencies. Unversioned server diagnostics, socket transports, dynamic capabilities and server commands remain explicitly unsupported. DDS application integration is separate.
Validation:
Security audit and vulnerability validation remain deferred under the owner's instruction. Functional contract tests and stable API status do not imply security audit or DDS product acceptance.