Add REC-02, the download badge (1.28.1)

.github/conformance.yml

@@ -6,8 +6,8 @@
 # The badge in .github/badges/ is generated from this file. Change the evidence
 # first, then this record, then regenerate. Never the other way round.
 
-standard_version: "1.28.0"
-assessed_on: "2026-09-22"
+standard_version: "1.28.1"
+assessed_on: "2026-09-25"
 state: "Healthy"
 evidence: "docs/self-assessment.md"
 

CHANGELOG.md

@@ -6,6 +6,16 @@ recorded here.
 Versions follow the compatibility policy in the
 [Repository Quality Standard](docs/repository-quality-standard.md).
 
+## 1.28.1 - 2026-09-25
+
+- Added `REC-02`: a live total-download badge for repositories that publish
+  downloadable release assets, linked to the releases page. It is a
+  recommendation, so it is not part of the badge block `P08` requires and adds
+  no condition to it.
+- Released as patch: a recommendation produces no result, so no recorded result
+  can change. This is the first change to use the rule
+  [Recommendations](docs/repository-quality-standard.md#recommendations) states.
+
 ## 1.28.0 - 2026-09-22
 
 - Added [Recommendations](docs/repository-quality-standard.md#recommendations):

docs/repository-quality-standard.md

@@ -1,6 +1,6 @@
 # Repository Quality Standard
 
-- Version: 1.28.0
+- Version: 1.28.1
 - Last reviewed: 2026-09-21
 - Review cadence: every six months, even when nothing changes
 
@@ -2075,6 +2075,7 @@ which is how the same decision gets made differently in every repository.
 | | Recommendation |
 |---|---|
 | <a id="rec-01"></a>REC-01 | Name the performance-sensitive paths a change should be reviewed against, and how they are measured — a benchmark, a profiling routine, or a documented review pass. This was criterion `S14` until 1.28.0. It is worth doing and it is not worth assessing: whether a path is performance-sensitive is a judgement no fixed line decided consistently, so the criterion measured whether a sentence existed rather than whether the practice did. [A performance-review agent](../packages/performance-review/README.md) is one way to run such a review. |
+| <a id="rec-02"></a>REC-02 | Where a repository publishes downloadable release assets, show a live total-download count and link it to the releases page: `[![Downloads](https://img.shields.io/github/downloads/OWNER/REPOSITORY/total?label=downloads)](https://github.com/OWNER/REPOSITORY/releases)`. It is not part of the badge block `P08` requires and adds no condition to it. GitHub counts asset downloads rather than unique users or installations, and checksum downloads are included in the total, so read it as a direction and not a figure. |
 
 ## Changing This Standard
 

docs/self-assessment.md

@@ -1,7 +1,7 @@
 # Self-Assessment: trsdn/.github
 
-- Standard version: 1.28.0
-- Assessed on: 2026-09-22
+- Standard version: 1.28.1
+- Assessed on: 2026-09-25
 - State: **Healthy**
 - Record: [`.github/conformance.yml`](../.github/conformance.yml)
 

standard.yml

@@ -3,7 +3,7 @@
 # Generated by scripts/standard.py from
 # docs/repository-quality-standard.md. Do not edit by hand.
 
-version: "1.28.0"
+version: "1.28.1"
 last_reviewed: "2026-09-21"
 
 prefixes:

templates/conformance.yml

@@ -20,7 +20,7 @@
 # The badge is generated from this file. Change the evidence first, then this
 # record, then regenerate. Never the other way round.
 
-standard_version: "1.28.0"
+standard_version: "1.28.1"
 assessed_on: "YYYY-MM-DD"
 state: "Needs work"
 evidence: "docs/self-assessment.md"