v0.3.1 — scanner and ranking quality fixes
Published to npm as @aryam/fixmap@0.3.1 and @aryam/fixmap-core@0.3.1 before this release was cut, and verified cold: npx -y @aryam/fixmap@0.3.1 mcp starts and serves fixmap_plan correctly.
Fixed
- A nonexistent
--repopath now fails with a clear error and nonzero exit instead of an empty success report; the MCP tool returns an error result for the same case (#21). - Repository scans respect
.gitignorein git repositories viagit ls-files, so ignored build output such as.vercel/no longer outranks source files (#23). - Common stop words and stem fragments no longer count as content matches, deployment-related tasks rank root configuration such as
vercel.jsonandpackage.json, and lockfiles are excluded from ranking (#22). - An unresolvable diff ref with no
--issuefallback now exits nonzero instead of an empty success report (#25). - Working-tree diff specs such as
--diff HEADinclude untracked files in changed context (#26).
Added
- npm publish workflow using trusted publishing with provenance (#29).
- Package READMEs on the npm registry pages (#20).
Full changelog: v0.3.0...v0.3.1