chore(release): 0.6.17 — Cursor preToolUse blocking enforcement

[giancolombi]

Bumps node + python (+ lockfile) to 0.6.17 and promotes the [Unreleased] entry → [0.6.17].

Ships #60 — Cursor preToolUse blocking enforcement (init --agent cursor blocks non-compliant writes by default; --cursor-mode warn keeps surface-only). Release metadata only, no code changes.

To publish

Merge, then create GitHub Release v0.6.17 → publish.yml runs the test matrix and publishes to npm + PyPI.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This is a release-only PR bumping all four package manifests from 0.6.16 → 0.6.17 and promoting the [Unreleased] changelog entry to [0.6.17] - 2026-06-09. No source code changes are included.

• Version updated consistently across node/package.json, node/package-lock.json, and python/pyproject.toml.
• CHANGELOG.md adds the [0.6.17] entry with the Cursor preToolUse blocking enforcement notes, but the footer reference-link block (bottom of file) was not updated — [0.6.15], [0.6.16], and [0.6.17] are missing diff links and [Unreleased] still compares from v0.6.14...HEAD.

Confidence Score: 4/5

Safe to merge after fixing the CHANGELOG footer links; all package version bumps are consistent and correct.

The version bump itself is clean and consistent across all four files. The one real defect is that the CHANGELOG footer reference-link block was not updated: three already-released versions have no clickable diff links, and the [Unreleased] anchor will keep comparing from v0.6.14 rather than v0.6.17 until corrected. This affects changelog navigation for anyone reading it on GitHub or npm but does not affect the published packages themselves.

CHANGELOG.md — the footer reference-link block needs three new entries and the [Unreleased] anchor updated.

Important Files Changed

Filename	Overview
CHANGELOG.md	Promotes [Unreleased] → [0.6.17] but the footer reference-link block is stale: three released versions (0.6.15, 0.6.16, 0.6.17) have no diff links and the [Unreleased] anchor still points at v0.6.14...HEAD.
node/package.json	Version bumped from 0.6.16 → 0.6.17; no other changes.
node/package-lock.json	Top-level version and packages[""] version both updated to 0.6.17; lockfile is consistent.
python/pyproject.toml	Version bumped from 0.6.16 → 0.6.17; no other changes.

Comments Outside Diff (1)

1. CHANGELOG.md, line 221-232 (link)

   Stale footer comparison links

   The reference-link block at the bottom of the file has not been updated since 0.6.14. Three released versions (0.6.15, 0.6.16, 0.6.17) have no diff links, and the [Unreleased] anchor still compares from v0.6.14...HEAD — so clicking any of the newer version headings in the rendered changelog will silently go nowhere, and the [Unreleased] diff will include months of already-released commits.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: CHANGELOG.md
   Line: 221-232
   
   Comment:
   **Stale footer comparison links**
   
   The reference-link block at the bottom of the file has not been updated since `0.6.14`. Three released versions (`0.6.15`, `0.6.16`, `0.6.17`) have no diff links, and the `[Unreleased]` anchor still compares from `v0.6.14...HEAD` — so clicking any of the newer version headings in the rendered changelog will silently go nowhere, and the `[Unreleased]` diff will include months of already-released commits.
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
CHANGELOG.md:221-232
**Stale footer comparison links**

The reference-link block at the bottom of the file has not been updated since `0.6.14`. Three released versions (`0.6.15`, `0.6.16`, `0.6.17`) have no diff links, and the `[Unreleased]` anchor still compares from `v0.6.14...HEAD` — so clicking any of the newer version headings in the rendered changelog will silently go nowhere, and the `[Unreleased]` diff will include months of already-released commits.

_{Reviews (1): Last reviewed commit: "chore(release): 0.6.17 — Cursor preToolU..." | Re-trigger Greptile}