Release/3.5.1

[bao-byterover]

No description provided.

[github-actions]

Claude finished @bao-byterover's task in 1m 32s —— View job

---

PR Review: Release/3.5.1

• Gather context and read changed files
• Review CHANGELOG.md changes
• Review package.json changes
• Post final review summary

---

Summary

This is a clean, minimal patch release PR bumping 3.5.0 → 3.5.1. The two changes are correct and well-scoped.

Overall score: 4 / 5

File	Assessment
CHANGELOG.md	Well-written entry. Content accurately reflects the MCP tool description improvements from #423. Consistent style with prior entries (no dates, same section structure).
package.json	Correct patch-version bump.

One finding

package-lock.json version is stale — the lockfile's top-level "version" field still reads 3.4.0, two releases behind. This was not introduced by this PR (the same was true for the 3.5.0 release), but it is worth fixing going forward. Running npm install --package-lock-only and committing the result as part of each release bump would keep it in sync.

nitpick · This does not block merging — it has no runtime impact — but it can mislead anyone who inspects the lockfile to check the version.

Fix this →

---

[github-actions]

nitpick: package-lock.json still shows "version": "3.4.0" (two releases behind — it wasn't updated in the 3.5.0 release either). While this doesn't affect runtime behavior, the lockfile top-level version field should mirror package.json for correctness and to avoid confusing anyone who checks it.

Consider running npm install --package-lock-only (or just npm install) to regenerate the lockfile with the correct version, then committing package-lock.json as part of release bumps going forward.