Repository navigation
Gate routine retargeting behind an approved tool (CL-7359) - #574
Merged
Merged
Conversation
TheGreatAxios
force-pushed
the
cl-7359-retarget-tool
branch
from
September 2, 2026 15:49
740a669 to
1f6c8d5
Compare
TheGreatAxios
marked this pull request as ready for review
September 2, 2026 16:09
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
1 participant
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.
Add routine_retarget (approval: "ask") taking { routineId, definitionAssetId }, calling the existing PATCH through @corbits/routines-tools' client. routine_update now rejects a definitionAssetId argument outright (arktype onUndeclaredKey("reject")), so the only way to retarget a routine at a different definition is through the approved routine_retarget tool. Bumped routines-tools to 0.0.10 and its pin in workflows/assistant.
Resolves CL-7359