docs(release): standardize release and contributor writing

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,8 @@
+<!-- Follow CONTRIBUTING.md and docs/RELEASE_WRITING.md. Complete required fields and remove optional empty sections. -->
+
 ## Purpose
 
-Describe the problem and the observable outcome.
+Describe the problem, trigger, and observable outcome in plain English unless the project selects another language. Use sentence case, concrete facts, and no decorative headings. Rewrite this description to match the final diff before review.
 
 ## Scope
 

.github/release.yml

@@ -1,17 +1,20 @@
+# Generated notes are a draft; edit against CHANGELOG.md before publication.
 changelog:
   exclude:
     labels:
       - 'release: skip-notes'
-    authors:
-      - dependabot
   categories:
     - title: Added
       labels: ['type: feature']
-    - title: Fixed
-      labels: ['type: bug', 'type: security']
     - title: Changed
-      labels: ['type: performance', 'type: refactor', 'type: dependency']
-    - title: Documentation
-      labels: ['type: documentation']
+      labels: ['type: performance', 'type: refactor', 'type: dependency', 'type: documentation']
+    - title: Deprecated
+      labels: ['type: deprecation']
+    - title: Removed
+      labels: ['type: removal']
+    - title: Fixed
+      labels: ['type: bug']
+    - title: Security
+      labels: ['type: security']
     - title: Other changes
       labels: ['*']

.github/workflows/release.yml

@@ -33,6 +33,9 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
+      - name: Test release-note formatting
+        run: node --test scripts/release-notes.test.mjs
+
       - name: Verify release tag
         env:
           TAG_NAME: ${{ github.event_name == 'push' && github.ref_name || inputs.tag }}
@@ -76,13 +79,12 @@ jobs:
           TAG_NAME: ${{ github.event_name == 'push' && github.ref_name || inputs.tag }}
         run: |
           VERSION="${TAG_NAME#v}"
-          DISPLAY_VERSION=$(node --input-type=module -e "const parts=process.argv[1].split('.'); console.log(parts[2] === '0' ? parts.slice(0, 2).join('.') : parts.join('.'))" "$VERSION")
           CHROME_ARCHIVE=".output/elements-$VERSION-chrome.zip"
 
           if gh release view "$TAG_NAME" >/dev/null 2>&1; then
             gh release edit "$TAG_NAME" \
               --target "${{ github.sha }}" \
-              --title "Elements $DISPLAY_VERSION" \
+              --title "Elements $VERSION" \
               --notes-file ".output/release-notes.md" \
               --draft=false
             gh release upload "$TAG_NAME" \
@@ -91,7 +93,7 @@ jobs:
           else
             gh release create "$TAG_NAME" \
               --target "${{ github.sha }}" \
-              --title "Elements $DISPLAY_VERSION" \
+              --title "Elements $VERSION" \
               --notes-file ".output/release-notes.md" \
               "$CHROME_ARCHIVE"
           fi

CHANGELOG.md

@@ -6,6 +6,8 @@ All notable changes to Elements are documented in this file.
 
 ### Changed
 
+- Standardised commit messages, pull request reviews, changelogs, and release notes with shared contributor templates.
+
 - Adopted QenTerra repository standard 1.3.0 with the canonical Contact block and funding-surface prohibition.
 - Adopted the QenTerra public repository standard, including complete
   contribution, maintenance, release, Wiki, and contact documentation.
@@ -14,15 +16,15 @@ All notable changes to Elements are documented in this file.
 - Required pull requests, successful project and governance checks, resolved
   review conversations, linear history, and immutable release tags at GitHub.
 
+### Removed
+
+- Removed external donation configuration, badges, and README prose.
+
 ### Security
 
 - Updated the transitive `brace-expansion`, `nanoid`, and `postcss` resolutions
   to versions that clear the current high-severity npm audit gate.
 
-### Removed
-
-- Removed external donation configuration, badges, and README prose.
-
 ## [1.0.0] — 2026-07-29
 
 ### Added

CONTRIBUTING.md

@@ -26,6 +26,15 @@ there, then removes them after the gate. Set
 `ELEMENTS_KEEP_VERIFY_WORKSPACE=1` only when you need to inspect that external
 workspace.
 
+## Commit and review format
+
+Follow [Release writing](docs/RELEASE_WRITING.md) for commit grammar, PR and review
+comment templates, changelog entries, release notes, and publication updates.
+Write in English, use a specific Conventional Commit subject of at most 72
+characters, and keep one coherent outcome per change. Breaking changes include
+a migration footer. PR descriptions use the repository template's section order;
+review findings explain the condition, consequence, and requested change.
+
 ## Pull requests
 
 - Keep one change per pull request.