feat(screenote): create explicitly named projects - #36
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.
Summary
Screenote capture and snapshot flows can now create an exactly named missing project when the user explicitly requests it, instead of stopping with instructions to create it elsewhere. Creation remains guarded against inferred names, ambiguity, duplicate exact matches, and
missing_projecterrors without explicit create intent; successful creation must return the requested project before uploads continue.The protected release probe now uses the pinned CLI's real
page listgrammar, so it will no longer fail on unsupported pagination flags. This also prepares the Screenote package surfaces and changelog for3.1.0.Validation
project createcreatedrabata.ioand returned project ID 24.