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
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.
Adds the grouped cloning-provenance notebook, its reference inputs and view helpers, and guides covering the design-to-protocol workflow. The example inspects planned SBOL provenance, LabOP, compiler source maps, and target-independent protocol artifacts.
Validation: 255 tests passed on Python 3.12 with the optional robot SDKs installed; Ruff and mypy passed at this branch tip.
The final wheel and source distribution passed isolated installed-package checks and strict metadata validation. All 9 notebook code cells executed successfully in a fresh kernel, with 10 local links verified. Both command-line workflow examples also ran successfully.
Stack: 11/11, split from #1. Base:
marpaia/cloning-protocols. Each PR targets the preceding branch so its diff contains only this slice.Previous: #11