Sync dev with v0.2.0 main#5
Closed
sketchmind wants to merge 2 commits into
Closed
Conversation
- promote CLI self-description contract tightening from dev to main - keep release branch history linear through squash merge - CI passed for package and Python 3.11/3.12/3.13 test jobs
Add task authoring schema discovery, workflow patch templates, workflow/workflow-instance export and full edit flows, README onboarding updates, and 0.2.0 release metadata.
Owner
Author
|
Closing this direct main-to-dev PR because GitHub cannot create the merge commit cleanly after the prior squash history. Replacing it with a dedicated sync branch. |
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.
Sync the protected dev branch with the v0.2.0 release state from main after publishing.