chore: v1.7.2 changelog

[valentinozegna]

Summary

• CHANGELOG.md: 1.7.2 section from docs(cli): say who runs the server, not what running it does #180's Changelog section
• npm version patch --no-git-tag-version: 1.7.1 → 1.7.2

Patch bump: one help-copy correction.

Test plan

• CI green
• After merge: scripts/tag-release.sh --yes on main

[claude]

Claude finished @valentinozegna's task in 33s —— View job

---

Review: PR #181 — v1.7.2 changelog

• Gather context (diff, CLAUDE.md release process)
• Review CHANGELOG.md changes
• Review package.json / package-lock.json version bump
• Post summary review

Verdict: LGTM — clean, mechanical release PR. No inline comments; nothing to flag.

This follows the repo's release process (see CLAUDE.md) exactly:

• CHANGELOG.md gets a new ## [1.7.2] - 2026-08-23 section, correctly summarizing PR docs(cli): say who runs the server, not what running it does #180's CLI help-copy fix, in the same style/format as prior entries.
• package.json and package-lock.json are bumped 1.7.1 → 1.7.2 together, consistent with what npm version patch --no-git-tag-version produces.
• bun.lock is untouched, which is correct — it records no version for the workspace root, so a version-only bump shouldn't touch it.
• Patch bump is the right call: PR docs(cli): say who runs the server, not what running it does #180 was a help-text/docs correction, not a feature or breaking change — no minor/major bump needed.
• No code changes, so no functional bugs, security, or performance concerns apply here.
• Test plan checkboxes (CI green, tag-release.sh after merge) are appropriately left for post-merge follow-up.

Nothing else stands out — this is a textbook release PR per the repo's documented process.