🔖 chore(release): prepare v0.15.2

[konih]

What

Release-prep commit for v0.15.2 (patch), per docs/RELEASE.md.

• charts/mkurator/Chart.yaml: version + appVersion 0.15.1 → 0.15.2
• CHANGELOG.md: regenerated via git-cliff --config cliff.toml --tag v0.15.2
• docs/INSTALL_AND_USE.md: VERSION= / chart refs bumped
• docs/UPGRADE.md: VERSION= bumped + new 0.15.1 → 0.15.2 path-table row

Why patch

No feat, no fix, no breaking (!) commit since v0.15.1. The only
changelog-visible entry is an internal dead-code removal in
internal/validation (384c6ea — the bare ValidateQueueManagerConnectionDelete
lost its last caller when the v1alpha1 webhook was dropped in Phase 8e). Nothing
reachable changed behaviour.

The rest of the delta is cliff-skipped: docs corrections (OPERATOR_RUNTIME,
ADR-0014), a goformat exclusion for generated files, and the mqweb
outage-recovery e2e test.

This release contains no user-facing change — it is a maintenance tag.

Gates (local, on this branch)

Gate	Result
task verify	✅ ok — no generated-artifact drift
task lint	✅ 0 issues (+ arch-lint OK)
task test:run	✅ pass — internal/ 92.7% (floor 90), api/ 92.5% (floor 75)

After merge

Tag is not pushed by this PR. Per the runbook, CI + Integration + E2E must all
be green on the post-merge main HEAD SHA (rebase merge ⇒ new SHA) before tagging.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[konih]

Parking this release — holding v0.15.2 until there are real user-facing fixes to ship.

The delta since v0.15.1 is maintenance only (one internal dead-code removal, docs corrections, a goformat exclusion, and the mqweb outage-recovery e2e test), so a tag now would publish a GHCR image and GitHub Release with no behaviour change for consumers.

Nothing here is lost — when real fixes land, the prep is ~2 minutes to redo and should be regenerated anyway (the changelog needs the new commits and a current date):

1. bump charts/mkurator/Chart.yaml version + appVersion
2. bin/git-cliff --config cliff.toml --tag vX.Y.Z -o CHANGELOG.md
3. bump VERSION refs in docs/INSTALL_AND_USE.md + docs/UPGRADE.md, add the UPGRADE path-table row

Worth keeping from this run: task changelog:write runs git-cliff bare and would emit [Unreleased] — pass --tag explicitly, as the v0.15.1 prep (2debb46) did. changelog-sync is still inactive (sync job skipped — App-ID secret unset), so it will not self-heal or clobber a tagged heading.