Release FixMap v0.8.9 reliability sweep - #628
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
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.
What changed
funcdeclarations never count as definition sites, so Go repos lose the 24-point definition boost #500 through bug: detectPackageManager only reads root lockfiles, so a Yarn/pnpm workspace gets npm test routes #627, excluding already-closed bug: fixmap_compare is the only MCP tool that does not reject unknown arguments despite declaring additionalProperties: false #542 and bug: the word "please" alone flips a specific task to vague, hard-capping every file to low confidence #599/fixmapsetup and the complete feature catalog, Validate, strict Verify warning gates, MCP/Action cache controls, and cross-language/workspace hardeningWhy
The published v0.8.8 package had a large confirmed reliability backlog across CLI, core, MCP, Action, CI, evidence, documentation, and the website. This release resolves the full reviewed scope and adds traceable regression proof.
Verification
npm run ciThe issue-to-fix-to-test ledger is in
docs/releases/v0.8.9-issue-verification.md.