Repository navigation
Beta.2: import protocol studies and separate draft completion from run readiness - #97
Open
assassin808 wants to merge 2 commits into
Open
assassin808 wants to merge 2 commits into
assassin808 wants to merge 2 commits into
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.
Protocol-only community studies currently fail to import, while saved protocol drafts can be reported as unfinished because completion still requires program.json. Accept hash-verified protocol releases and certify draft structure independently from simulation readiness, preserving the legacy path.
Validation: full offline suite 330 passed / 2 skipped before final small follow-ups; final affected-suite and byte-bound restart/import tests pass; TypeScript checks and production desktop/web builds pass; built web main-process server has 5 passing fixture tests. Windows CI and final packaged release verification are required before publication. See docs/protocol-launch-fixes.md for boundaries, including extraction completeness and real-model acceptance not certified by draft checks.