chore: v1.7.1 changelog

[valentinozegna]

Summary

• CHANGELOG.md: 1.7.1 section written from the Changelog sections of feat(cli): accept commands as words, and lay the help out as options and commands #175, feat(cli): document export-json and take an output path #176, docs: document the command line in docs/cli.md #177, docs: slim the README to the high level #178
• npm version patch --no-git-tag-version: 1.7.0 → 1.7.1

Patch bump: CLI ergonomics and docs; no tool or schema change.

Test plan

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

[claude]

Claude finished @valentinozegna's task in 1m 30s —— View job

---

Reviewing this PR

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

Summary

Posted the full review as a top-level comment via gh pr comment (no inline comments — see below). Verdict: clean, mechanical release PR, no blocking issues.

[claude]

Review: v1.7.1 release PR

Verdict: LGTM. This follows the repo's release process (see CLAUDE.md) exactly — no inline comments, nothing to fix.

What I checked:

• Diff is limited to CHANGELOG.md, package.json, package-lock.json — no code, matching the "release PRs contain no code" rule.
• Version bump is consistent across all three files: 1.7.0 → 1.7.1, and package-lock.json's root version was updated too (the exact thing npm version --no-git-tag-version is required for, vs. a hand-edit that would leave the lockfile stale).
• Cross-checked the CHANGELOG's 1.7.1 section against the actual ## Changelog blocks of feat(cli): accept commands as words, and lay the help out as options and commands #175, feat(cli): document export-json and take an output path #176, docs: document the command line in docs/cli.md #177, docs: slim the README to the high level #178 (fetched via gh pr view) — the wording matches each PR's own changelog entry verbatim, correctly attributed, nothing added or dropped.
• Date (2026-08-23) matches the merge date of the referenced PRs.
• Formatting (intro paragraph + ### Added/### Changed sections) is consistent with prior entries in the file (e.g. 1.7.0, 1.6.1).

One judgment call worth a sanity-check (not a blocker): this is a patch bump (1.7.0 → 1.7.1) even though the changelog has an ### Added section — new CLI command aliases (#175) and a newly-documented export-json command (#176) are new, backward-compatible functionality, which strict semver would usually call a minor bump. The PR body does explicitly justify the choice ("CLI ergonomics and docs; no tool or schema change"), which is exactly what CLAUDE.md asks the author to state — so process-wise this is satisfied. Worth double-checking that "no MCP tool/schema change" is really the bar this project uses to distinguish patch vs. minor (as opposed to "no new capability"), since 1.7.0 itself was bumped to minor for an analogous ### Added entry. If that's the established convention here, no change needed.

No test coverage concerns — this PR has no code to test, and tag-release.sh's pre-flight checks (CHANGELOG section present, lockfile version match, on main, clean tree) will catch anything structurally wrong at tag time.