Repository navigation
Refresh Check and Trace pins to Rubato-hosted CLI prereleases - #28
Merged
Merged
Conversation
Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
aharlap
marked this pull request as ready for review
October 19, 2026 19:41
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.
Refresh the macOS Check and Trace pins so installation from reviewed Rubato main includes the keyboard-trap fix from Praxity/praxity-check#30 and item-cue diagnostics from Praxity/praxity-trace#18. Both architectures use the same portable archives hosted on Rubato, following the existing tool-asset distribution route.
Rubato asset-only experimental prerelease contains exactly these two CLI archives, with no pack manifest or installer bootstrap:
praxity-trace-0.1.1-experimental.09fcaaf76-portable.tar.gz, source09fcaaf76841175d150210ec29c66d7ebab05cc3.SHA-256:
d5f8ef48f9277505996888322e11aa9f019d890e5f2a2052f590728925710265.praxity-check-0.6.0-alpha.c61b1cb3c-portable.tar.gz, sourcec61b1cb3ce3a4e7afb0a44f3dd70e82a52c1154d.SHA-256:
77fd9a2c8d9cdf1041341eef6b0bc564c0e560279b3bc520d95ec23fc42f79eb.Verification: existing packagers built clean exact source checkouts on hosted Ubuntu. Typecheck and packaging tests passed; Trace's item-cue tests also passed. Independently verified complete payload inventories, clean source metadata, portable targets and source licence, notice and skill files. Rehosted byte-for-byte copies of those tool prereleases on Rubato, downloaded the uploaded assets and checked their hashes against both build logs and GitHub asset digests. Anonymous downloads from the published Rubato URLs produce the same SHA-256 values. Both archives retain PolyForm Perimeter 1.0.1 and required third-party notices.
The original publisher dry-run assertion at
test/publish.test.mjs:90is unchanged. Pinning the Rubato-hosted copies fixes its failure without changing the publisher. The install-plan regression now selects the Rubato-hosted URLs for both macOS architectures.Validation:
npm run validateandnpm run validate:releasepassed. Full localnode --testpassed under WSL Ubuntu with Node 24.18.0: 544 tests, 543 passed, one existing Windows-only skip, zero failures, 220 seconds. Its source tree matches the committed tree exactly. The native Windows attempt hit 60-second MSYS installer-fixture timeouts and was stopped; test assertions and limits are unchanged. Hosted CI for the corrected commit is running, including native darwin-arm64 and darwin-x64 real installs.Build runs: Trace, Check. No new dependency, formal Rubato pack publication, stable-channel change or installer change. Latest remains
v0.1.1. Do not merge automatically.Review: controller check only (mechanical pin bump): asset SHA-256s verified against the release downloads; full node --test and macOS installs green on aed15e1.