chore: release v0.2.0

First matured release after the initial dogfood loop on NRS-4365.
Consolidates lessons from the 0.1.x rapid-iteration cycle plus the
final 'shorthand-as-display-text in Jira' refinement that gives both
clickability and shorthand readability.

Highlights: stronger severity vocabulary, sanity-scan step, Jira-
specific rendering rules, Pillar F refinements (F4 split, F6 upgrade,
new F1.5 description currency), two-comment pattern with TL;DR,
list format for findings, GitHub/GitLab shorthand link convention.

See CHANGELOG.md [0.2.0] for the full summary.

Author: CybotTM

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "peer-qa-review",
-  "version": "0.1.7",
+  "version": "0.2.0",
   "description": "Round-1 IT QA runbook: peer review of completed work before customer acceptance or internal close. Lifecycle, checklist, severity vocabulary, comment template, edge cases, anti-patterns. Generic for any IT/Ops team.",
   "repository": "https://github.com/netresearch/peer-qa-review-skill",
   "license": "(MIT AND CC-BY-SA-4.0)",

CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.0] - 2026-04-27
+
+First matured release after the initial dogfood loop on NRS-4365. The 0.1.x series was a rapid-iteration cycle (each round catching a different class of bug); 0.2.0 consolidates the stable result.
+
+### Highlights since 0.1.0
+
+- **Stronger severity vocabulary** — explicit anti-patterns including "do not use `(x)` for reviewer-side limitations" and "internal inconsistency between findings list and verdict" (`severity.md`).
+- **Sanity-scan step** before posting — re-read your own QA comment for severity inconsistencies, F7 violations, transition-name vs verdict mismatches, and Pillar P attestations contradicted by the comment itself (`comment-template.md`).
+- **Jira-specific rendering rules** — `(-)` renders as 🚫 forbidden, not "n/a"; severity tokens in prose render as icons mid-sentence; both call out in `severity.md`.
+- **Pillar F refinements** — F4 split into F4a (structured issue links via the issue-link feature, verified against the API not description prose) and F4b (external work artefacts); F6 worklog upgraded `(i)` → `(!)` (audit/billing/capacity is not a courtesy); new F1.5 description currency (does the description still describe what was actually delivered?).
+- **Two-comment pattern** for long reviews — the structured comment is the audit trail; an optional TL;DR addressed to the implementer with `[~username]` mention and numbered action items keeps actionability visible without burying the audit-trail header (`comment-template.md`).
+- **List format for pillar findings** — bulleted lists (`*` / `**`) instead of bare severity-icon lines, for proper wrap-indent of long findings (`comment-template.md`).
+- **GitHub / GitLab shorthand** for trusted shared-namespace projects — `owner/repo#123` (GitHub issue or PR), `group/project!456` (GitLab MR), `group/project@sha` (commits). In Jira, wrap as `[shorthand|url]` for clickability with shorthand-as-display-text (this is *not* the display-text-link anti-pattern; opaque display text was the original target). On GitHub/GitLab, the bare shorthand auto-links natively.
+- **Methodology lesson** — every iteration round caught a different *class* of bug. Source-only review consistently misses what's only visible in the rendered output. When possible, fetch and look at the rendered HTML before declaring done.
+
+### Internal links
+
+- `references/severity.md` — full vocabulary, anti-patterns, examples
+- `references/checklist.md` — every check by pillar (F1–F8, R1–R6, I1–I4, D1–D4, B1–B3, C1–C3, P1–P6)
+- `references/comment-template.md` — comment template, link conventions, list format, two-comment TL;DR pattern, sanity scan
+
 ## [0.1.7] - 2026-04-27
 
 ### Changed

skills/peer-qa-review/SKILL.md

@@ -5,7 +5,7 @@ license: "(MIT AND CC-BY-SA-4.0). See LICENSE-MIT and LICENSE-CC-BY-SA-4.0"
 compatibility: "Requires a ticket system (Jira tested; works conceptually with Linear/GitHub Issues/etc.) and shell access for verification. Companion: jira-communication skill for ticket I/O."
 metadata:
   author: Netresearch DTT GmbH
-  version: "0.1.7"
+  version: "0.2.0"
   repository: https://github.com/netresearch/peer-qa-review-skill
 allowed-tools: Bash Read Write Edit
 ---

skills/peer-qa-review/references/comment-template.md

@@ -14,7 +14,21 @@ For your team's *trusted shared-namespace* GitHub / GitLab projects, prefer the
 | Commit | `owner/repo@7c12680` | `group/project@7c12680` |
 | Branch / pipeline / release / tag | full URL | full URL |
 
-**Trade-off**: this shorthand is **not** auto-linked in Jira (Jira only auto-links its own issue keys). Readers in Jira have to mentally construct the URL or copy-paste. Acceptable for internal projects where everyone knows the namespace; same trade you already accept for `NRS-4365`. In GitHub PRs / GitLab MRs the shorthand IS auto-linked, so it's a win in both UI surfaces.
+**In Jira specifically**: the shorthand alone is *not* clickable — Jira only auto-links its own issue keys. To get clickable links *and* shorthand readability in Jira, wrap the shorthand as **display text** in a Jira link macro:
+
+```jira
+[provision/ansible-role-vault!9|https://git.netresearch.de/provision/ansible-role-vault/-/merge_requests/9]
+[netresearch/peer-qa-review-skill#10|https://github.com/netresearch/peer-qa-review-skill/issues/10]
+```
+
+This renders as a clickable link reading `provision/ansible-role-vault!9` — the same anchor text GitHub/GitLab use natively. **This is *not* the display-text-link anti-pattern** (which targets opaque text like `[click here|url]`) — the shorthand IS the canonical reference, so using it as display text is the *opposite* of opaque.
+
+**On GitHub PRs / GitLab MRs**: the bare shorthand is already auto-linked by the platform, so write `provision/ansible-role-vault!9` (without the `[…|…]` wrapper) when authoring there.
+
+**Rule of thumb**:
+- *Authoring in Jira* → wrap: `[shorthand|url]`
+- *Authoring on GitHub/GitLab* → bare: `shorthand`
+- *Authoring anywhere ambiguous* → bare shorthand + full URL on the next line, or just use full URL.
 
 **Keep full URLs** for: