Repository navigation
v0.4.4
Added
stale-path(warning, on by default): a repo path in backticks, such assrc/api/routes.tsorpackages/web/, that isn't in the repository any more. It only checks paths with two or more parts that end in an extension or a slash and whose top folder exists, and it skips globs, placeholders, fenced blocks, example sections and paragraphs about another repository. It only asks whether paths exist; it opens no file besides the steering file. On 26 public repos it reported 15 paths, and I checked each by hand: all 15 were real moved or deleted files.dead-command(warning, opt-in):npm run,npm test,pnpm,yarn,bun runandmakecommands whose script or target isn't defined. It readspackage.jsonand Makefile files, so it runs only with--include config(include: ["config"]inlint_steering). Withconfig,stale-pathalso reads.gitignorefiles and skips the paths they cover.
Changed
- The README leads with CI: the GitHub Action comes first, with a copy-paste workflow that lints pull requests and pushes to main that touch a steering file and uploads SARIF on push only.
Fixed
- The README's "How was it tested?" answer still said every real finding from 0.3.0 was kept in 0.4.0. 0.4.2 took that claim back in the changelog; the FAQ line is gone now too.
Details: packages/mcp/CHANGELOG.md and plugins/asitis/CHANGELOG.md.