chore: bump quarry to v1.14.0 in marketplace

[claude-puntlabs]

Note

Low Risk
Low risk: this only updates metadata in the plugin marketplace manifest to point quarry at a new tagged release, with no runtime logic changes in this repo.

Overview
Updates .claude-plugin/marketplace.json to bump the quarry plugin entry from v1.13.0 to v1.14.0 (both the Git ref and the declared version), so the marketplace resolves the newer release.

^{Reviewed by Cursor Bugbot for commit cefd290. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Copilot]

Pull request overview

Bumps the quarry plugin entry in the Punt Labs Claude Code marketplace catalog to the latest released version.

Changes:

• Update punt-labs/quarry source ref from v1.13.0 to v1.14.0
• Update the cataloged plugin version from 1.13.0 to 1.14.0

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This is a user-facing marketplace catalog change (plugin version bump). Per CLAUDE.md, PRs that change user-facing behavior must include a CHANGELOG.md entry under ## [Unreleased]; please add an entry describing the quarry bump before merge.

[claude]

🔴 This PR bumps quarry from v1.13.0 to v1.14.0 but is missing a required CHANGELOG entry. Per CLAUDE.md: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.' Add a line like '- quarry bumped to v1.14.0' under the [Unreleased] Changed section in CHANGELOG.md before merging.

Extended reasoning...

What the bug is: CLAUDE.md contains an explicit merge gate: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.' This PR bumps quarry from v1.13.0 to v1.14.0 in .claude-plugin/marketplace.json but the diff contains no corresponding CHANGELOG.md entry.

The specific code path: The only file changed in this PR is .claude-plugin/marketplace.json, updating ref from "v1.13.0" to "v1.14.0" and version from "1.13.0" to "1.14.0" (lines 135–144). CHANGELOG.md is untouched.

Why existing code doesn't prevent it: There is no automated CI check enforcing CHANGELOG entries — this is a documented manual convention. CLAUDE.md says entries must be written in the PR branch before merge, not retroactively.

The impact: Users who install quarry from the marketplace catalog will receive v1.14.0 instead of v1.13.0 with no documented explanation of what changed. This violates the project's transparency standard and CLAUDE.md explicitly classifies this as a merge blocker.

How to fix it: Add a single line to CHANGELOG.md under the [Unreleased] → Changed section:

- quarry bumped to v1.14.0

This follows the exact pattern already established for other plugins: 'beadle bumped to v0.7.0', 'ethos bumped to v0.2.0'.

Step-by-step proof:

1. CLAUDE.md states: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.'
2. A marketplace plugin version bump is user-facing: any user running the marketplace installer will receive quarry v1.14.0 instead of v1.13.0.
3. The PR diff shows only .claude-plugin/marketplace.json changed — no CHANGELOG.md modification.
4. The CHANGELOG.md [Unreleased] section already contains entries for other bumps, confirming the convention applies.
5. CLAUDE.md also states 'There is no such thing as a pre-existing issue,' so the fact that prior PRs (chore: bump ethos to v3.8.0 in marketplace #193–chore: bump biff to v1.10.0 in marketplace #196) also skipped CHANGELOG entries does not excuse this omission.
6. Conclusion: the PR violates the documented merge gate and must not be merged until a CHANGELOG entry is added.