docs(standard): recommend release downloads badge

.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.11.1"
-assessed_on: "2026-09-02"
+standard_version: "1.11.2"
+assessed_on: "2026-09-16"
 state: "Healthy"
 evidence: "docs/self-assessment.md"
 

CHANGELOG.md

@@ -6,6 +6,15 @@ recorded here.
 Versions follow the compatibility policy in the
 [Repository Quality Standard](docs/repository-quality-standard.md).
 
+## 1.11.2 - 2026-09-16
+
+- Added a recommended dynamic total-download badge for repositories that publish
+  downloadable GitHub Release assets.
+- Clarified that the badge reports asset downloads, not unique users or
+  installations, and includes checksum downloads.
+- Patch release: this is optional guidance and does not change any `P08`
+  assessment result.
+
 ## 1.11.1 - 2026-09-02
 
 - Made

docs/repository-quality-standard.md

@@ -1,7 +1,7 @@
 # Repository Quality Standard
 
-- Version: 1.11.1
-- Last reviewed: 2026-09-02
+- Version: 1.11.2
+- Last reviewed: 2026-09-16
 - Review cadence: every six months, even when nothing changes
 
 This document is the public source of truth for repository quality across
@@ -836,6 +836,18 @@ Rules:
 A hardcoded `Swift 5.9` badge beside a manifest that has moved to 6.0 is the
 failure this section exists to prevent.
 
+Where a repository publishes downloadable GitHub Release assets, a live total
+download count is a useful optional signal. When maintainers choose to show it,
+use the release assets as the authority and link the badge to the releases page:
+
+```md
+[![Downloads](https://img.shields.io/github/downloads/OWNER/REPOSITORY/total?label=downloads)](https://github.com/OWNER/REPOSITORY/releases)
+```
+
+This badge is a recommendation, not part of the required badge block and not an
+additional condition for `P08`. GitHub counts asset downloads rather than unique
+users or installations, and checksum downloads are included in the total.
+
 Badge hosting is not a privacy question on GitHub. Markdown rendered on
 `github.com` loads every external image through GitHub's proxy, so the image host
 observes the proxy and not the reader. The `Y02` argument applies where that

docs/self-assessment.md

@@ -1,7 +1,7 @@
 # Self-Assessment: trsdn/.github
 
-- Standard version: 1.11.1
-- Assessed on: 2026-09-02
+- Standard version: 1.11.2
+- Assessed on: 2026-09-16
 - State: **Healthy**
 - Record: [`.github/conformance.yml`](../.github/conformance.yml)
 

standard.yml

@@ -3,8 +3,8 @@
 # Generated by scripts/standard.py from
 # docs/repository-quality-standard.md. Do not edit by hand.
 
-version: "1.11.1"
-last_reviewed: "2026-09-02"
+version: "1.11.2"
+last_reviewed: "2026-09-16"
 
 prefixes:
   A: "Archived"

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.11.1"
+standard_version: "1.11.2"
 assessed_on: "YYYY-MM-DD"
 state: "Needs work"
 evidence: "docs/self-assessment.md"