feat(drive): ship verified dynamic tool lifecycle example#45
Open
kitlangton wants to merge 1 commit into
Open
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.
What
Add generated state-machine coverage for
ToolProducerand ship a runnable dynamic-tool example covering progress, cancellation, and terminal completion.Before / After
Before: Dynamic tool lifecycle behavior had strong focused regressions, but no generated coverage across attachment replacement, reconnects, invocations, cancellation, settlement, and generation changes. The documented example was an inline happy path and was not shipped in the package.
After: An in-memory backend drives hundreds of deterministic generated operation sequences through the real producer, and consumers get a contract-checked packaged example with both completion and cancellation paths.
How
connectFrombackend subtypes.examples/dynamic-tool.ts, including input decoding, progress, cancellation handling, terminal completion, and a follow-up model response.opencode-drive.Scope
Limited to
ToolProducerlifecycle verification, its internal backend dependency, and dynamic-tool adoption material. No simulation protocol or CLI command shapes change, and publishing remains deferred.Testing
opencode-drive check ./examples/dynamic-tool.tspasses.bun run release:validatepasses: 31 Effect files / 204 tests, 57 CLI tests, lint, typecheck, and a 100-file package dry-run.61d7c10.