fix(changelog): move pr-review attribution entry back under Unreleased

[bborbe]

The fix: pr-review — every finding must now lead with a bold file reference bullet folded into the released ## v0.35.5 section, which does not contain the code change.

What happened

The releaser cut v0.35.5 at a9682cc for the go-testing-guide docs entry that was already sitting in ## Unreleased. That happened in the window between pushing #86 and merging it, so the rename ## Unreleased → ## v0.35.5 swept in an entry whose commit landed afterwards:

d0c4175  Merge pull request #86 (attribution)   ← the code change
bba71d9  require attribution on every pr-review finding
a9682cc  release v0.35.5                        ← tag cut HERE
1e56240  docs: go-testing-guide

Verified against the tag itself rather than the working tree:

grep 'must **be** the file reference' in v0.35.5:commands/pr-review.md  → 0
grep in HEAD:commands/pr-review.md                                      → 1

bullets in v0.35.5 TAG's changelog     → 1
bullets in master's v0.35.5 section    → 2

So v0.35.5 claimed a fix it does not ship. The pre-push fold guard was run on #86 and was clean at that moment — the fold happened after, which is precisely the overlap the sequencing rule warns about.

The fix

Move the entry back under ## Unreleased; the released section is restored to exactly what its tag contains, not edited into agreement with reality. After this change:

diff <(git show v0.35.5:CHANGELOG.md | sed -n '/^## v0.35.5/,/^## v0.35.4/p') \
     <(sed -n '/^## v0.35.5/,/^## v0.35.4/p' CHANGELOG.md)
→ IDENTICAL

The attribution fix then ships in the next release, which will genuinely contain it.

CHANGELOG only — no code touched.

[ben-s-pull-request-reviewer]

Now I have enough information for Step 4c-sel (CLASSIFY). Let me apply the selector-mode logic:

Changed files: CHANGELOG.md (1 file)

Step 4b-i candidates (judgment rules with glob matching CHANGELOG.md):

• changelog/conventional-prefix-required — owner: agent-auditor, trigger: CHANGELOG.md
• git-commit/feature-branch-no-tag — trigger: @commits (always candidate)
• git-commit/imperative-mood — trigger: @commits (always candidate)
• git-workflow/never-direct-commit-to-master — trigger: @commits (always candidate)

Step 4c-sel CLASSIFY:

Rule	Decision	Reason
changelog/conventional-prefix-required	skipped	applies_when checks unreleased bullets lack fix:/feat: prefix — the new bullet is fix:, so the condition does not hold
git-commit/feature-branch-no-tag	skipped	applies_when checks for git tag on feature branch — not applicable to this diff
git-commit/imperative-mood	skipped	applies_when checks commit message subjects — not a commit diff
git-workflow/never-direct-commit-to-master	skipped	applies_when checks direct commits to master — not a commit operation

Applicable set: ∅ — selector clean

Mechanical findings from pre-computed output: 0

Step 4d-sel: skipped — applicable set empty + no mechanical findings

---

Step 5: Consolidated Report

Must Fix (Critical): None.

Should Fix (Important): None.

Nice to Have (Optional): None.

Selector-mode traceability:

• Candidates: 4 rules matched by Step 4b-i glob filter
• Applicable: 0 rules selected by Step 4c-sel
• Skipped:
  • changelog/conventional-prefix-required → bullet has fix: prefix, condition not met
  • git-commit/feature-branch-no-tag → not a tag operation
  • git-commit/imperative-mood → not a commit message
  • git-workflow/never-direct-commit-to-master → not a direct commit

Notes:

• The change moves the fix: pr-review entry from ## v0.35.5 back to ## Unreleased, restoring the correct section placement after the prior PR incorrectly placed it under the versioned heading.
• LICENSE file is present (Step 3a verified).
• precommit skipped (selector mode) — CI covers lint+test.

Step 6: No test coverage gaps to address.

Step 7: Manual review of the diff confirms the change is correct — the fix: bullet is correctly placed under ## Unreleased and uses the proper conventional prefix. No issues found.

---

{
  "verdict": "approve",
  "summary": "Trivial structural fix that correctly restores the `fix: pr-review` changelog entry to `## Unreleased` from `## v0.35.5`. All candidates classified as non-applicable; mechanical funnel clean.",
  "comments": [],
  "concerns_addressed": []
}