chore: release 0.3.0 - #13
Merged
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
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.
The npm package is still at 0.2.0, so the merged skill, history, runtime, and agent-installation fixes are not available to npm users. This prepares 0.3.0, synchronizes the package and Codex plugin versions, and bundles the changelog with the upgrade instructions for explicit CLI model inheritance and Codex agent targets.
The release check found that npm omitted a packaging ignore file recorded in the runtime baseline, causing integrity checks to fail after installation. Moving that rule to the parent tools directory preserves dependency exclusion and leaves packaging metadata outside the reviewed runtime tree. The refreshed baseline retains every runtime file, and package validation now rejects any missing baseline file. The new check reproduced the original omission before the fix.
Validation: version synchronization, package checks, and both upstream checks pass. A nested dependency probe remains excluded from the package. Installing the actual tarball passes all 50 skill validations and the integrity baseline, plus selected skill and agent installation for all four Harnesses. Each copied recall helper runs independently. The underlying main commit passed the full CI matrix and 125 local tests with one expected Unix-only skip. Real diagnosis workflows completed in all four supported Harnesses; the changelog records the Codex reasoning and test-subprocess limitations.
After merge, publish the npm package and matching GitHub Release from the same commit, then verify the registry version and install the published package in a disposable directory.
Model: GPT-6
Harness: Codex