ci(changelog-review): validate new triage-only workflow shape

[claude]

Context

PR #1302 restructured the changelog-review workflow into a triage-only phase. The test plan items were not verified before merging (they require a live dispatch run after #1301 settled the tracked version to 2.1.138).

Test checklist

• Validate YAML parse + actionlint locally (actionlint .github/workflows/changelog-review.yml)
• Dry-run via workflow_dispatch with force_full_review=true — confirm:
  • Claude creates exactly one tracking issue (label: changelog-review) with grouped per-rule-file sections
  • Claude opens exactly one PR containing only .claude-code-version-check.json
  • No rule files are modified (triage-only constraint)
• Run a second dispatch (without force_full_review) and confirm skip-if-exists fires (no new issue/PR created when one already exists for the current range)

Why

These validation steps were listed in the PR #1302 test plan but depend on a live run after the version tracking file settled at 2.1.138. The current tracked version should produce a small or zero gap — ideal for validating the new shape without noise from a 62-version catch-up.

Related

• PR ci(changelog-review): refactor to triage-only + skip-if-exists #1302 (new workflow shape)
• PR docs(rules): apply Claude Code changelog review 2.1.76 → 2.1.138 #1301 (recovery of 2.1.76 → 2.1.138 rule edits)

[laurigates]

Validation steps (manual workflow_dispatch)

The triage-only shape from PR #1302 is in place; what's left is the live run. These steps need to be triggered from the GitHub UI or gh workflow run (an agent session without gh CLI access can't fire workflow_dispatch).

Run 1 — forced full review

1. Go to Actions → Claude: Changelog review → Run workflow.
2. Set force_full_review to true (default branch main).
3. Trigger and wait for the run to finish.

Verify on this run:

• Exactly one tracking issue is created (look in the open issues list with a label like changelog-review or whatever the workflow tags).
• Exactly one PR is opened, and its diff contains only .claude-code-version-check.json — no rule files (.claude/rules/*.md), no skill files, no plugin source.
• No commits land directly on main.
• Workflow logs show the triage phase running and the rule-edit phase explicitly skipped.

Run 2 — re-run, expect skip

4. Re-trigger Run workflow with the same parameters (without merging the PR from Run 1).
5. Verify:

• Run 2 detects the existing tracking issue and exits early (no new tracking issue, no new PR).
• Logs show the "existing tracking issue found, skipping" path.

After validation

• Tick the test plan boxes on PR ci(changelog-review): refactor to triage-only + skip-if-exists #1302 and close it if not already merged.
• This unblocks ci(changelog-review): extract as reusable workflow once shape is proven #1304 (extract to reusable workflow at laurigates/.github) and ci(changelog-review): track per-call token efficiency over time #1305 (token-efficiency tracking).

Notes

• If Run 1 modifies rule files or omits the tracking issue, the triage-only shape has regressed — stop and investigate before re-running.
• Run 2's skip behaviour depends on the existing-issue check using the right query (label + state=open). If Run 2 creates a duplicate tracking issue, the check needs tightening.

---

Generated by Claude Code