From 0df2a65d786caeffb0eb8cc47ee169509b8b596f Mon Sep 17 00:00:00 2001 From: Benjamin Borbe Date: Sun, 27 Sep 2026 13:26:27 +0200 Subject: [PATCH] fix: restore ## Unreleased, which the #224 merge turned into a duplicate v0.149.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Merging #224 renamed its ## Unreleased section to ## v0.149.1, but that heading already existed: commit 011556d ("release v0.149.1") had renamed the section for the sibling change in #222, and tag v0.149.1 points at it. The result on master was two ## v0.149.1 headings, this branch's bullets under the first, and no ## Unreleased section at all. Because the release watcher keys on ## Unreleased, it reported reason=no-release-files and skipped the repo — so this change would never have been released. Repair direction is decided by the tag, not by where the merge put the entry: git tag --contains cd3f4953 returns nothing, so this work is in no tag and its bullets move back under ## Unreleased. The sibling's section stays where its tag put it. Verified: one ## v0.149.1 heading remains, this branch's two bullets sit under ## Unreleased, the sibling's bullet sits under ## v0.149.1, and the fold guard prints only '-## v0.149.1' / '+## Unreleased'. --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8bd68db..bfe7d00 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,7 +8,7 @@ Please choose versions by [Semantic Versioning](http://semver.org/). * MINOR version when you add functionality in a backwards-compatible manner, and * PATCH version when you make backwards-compatible bug fixes. -## v0.149.1 +## Unreleased - feat: `vault-cli task remove-metrics-session ` removes every `metrics_sessions` entry carrying the supplied session id from one task, preserving every other entry and every other frontmatter key, and deletes the key outright when the last entry goes. A call whose id matches nothing fails loudly and writes nothing, and an empty, non-UUID or path-bearing id is refused before the task is read. `task set`, `task add` and `task remove` keep refusing `metrics_sessions` unchanged. - fix: **the `task-auditor` agent's Task-Goal Alignment check no longer recommends a goal link its own alignment check would then score as an orphan.** When the goal can be marked complete without the task, the check now recommends theme-only linkage instead and says so explicitly, so the recommendation and the orphan verdict that follows it agree.