Make Woolpack onboarding executable - #37
Merged
Merged
Conversation
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
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
uvxrender and strict-lint commands while checkout shims stay on workspace source0.1.1so the merged fix is release-readyVerification
15 passedintests/test_pack_lint.pypackages/woolpack/src/woolpack/scaffold.py13 PASS · 0 WARN · 0 ERRORuv lock --checkand locked sync passed with only the Woolpack lock entry changedwoolpack 0.1.1wheel and sdist built; Twine strict checks passedgit diff --checkand public-repo redaction scan passedDocumentation
Updated the product README, Woolpack package README, pack format guide, contributor flow, fallback submission template, AGENTS command contract, and the existing LLD version pin. No architecture diagram changed because module, data, and deployment boundaries are unchanged.
Known follow-up
PyPI
0.1.0is immutable and still prints the old bare follow-up commands. This PR prepares0.1.1but does not tag, release, or publish it. The external index and fallback validator pins should move only after0.1.1exists.Woolroom
maincurrently has an unrelated Ruff 0.16.4 failure across pre-existing files; that broad migration is intentionally outside this PR.