feat(docs): document Goal Runs API - #15
Draft
Si40Code wants to merge 1 commit into
Draft
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.
Summary
s-eleven-monophonefieldWhy
The monorepo cleanup removes the historical Zudoku snapshot. Goal Runs landed in the canonical Developer API after the standalone docs repository was created, so the public source of truth must receive that content before the old snapshot is removed.
Impact
After this PR is merged,
docs.heycall-e.comwill publish the Goal Runs guide and Goals/Goal Runs API Reference through the existing OSS deployment workflow. Existing Calls, Webhooks, and stable 0.2 SDK documentation remain compatible.Validation
pnpm run validatellms.txt,llms-full.txt, and OpenAPI verificationRollout dependency
Merge this PR before the companion
s-eleven-monocleanup MR !108, which removesservices/seleven-mcp/sdks/docs-site. Merging this PR triggers the repository's normal production OSS deployment; this PR does not merge or deploy itself.