feat(audit): merge audit trail and fixes

.coderabbit.yaml

@@ -24,7 +24,6 @@ reviews:
     - "!scripts/node_modules/**"
     - "!package-lock.json"
     - "!.husky/**"
-    - "!weekly-updates/**"
 
   path_instructions:
     # ── Patterns ──────────────────────────────────────────────────────────

.github/workflows/audit-check.yml

@@ -0,0 +1,29 @@
+# TEMPORARY workflow for the Q2 2026 content audit (PR #130).
+# Delete this file and scripts/audit-sync.js before merging feat/audit into master.
+
+name: Audit Tracker Check
+
+on:
+  push:
+    branches: [feat/audit]
+  workflow_dispatch:
+
+jobs:
+  audit-check:
+    runs-on: ubuntu-latest
+    name: QA-AUDIT.md sync check
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+
+      - name: Fetch master
+        run: git fetch origin master
+
+      - name: Setup Node.js
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
+        with:
+          node-version: '20'
+
+      - name: Check QA-AUDIT.md is in sync with origin/master
+        run: node scripts/audit-sync.js

CHANGELOG.md

@@ -4,6 +4,7 @@ All notable changes to the IPTF Map are documented here.
 
 ## [Unreleased]
 
+- chore: remove the dormant `weekly-updates/` directory and `scripts/weekly-summary.sh` (single entry, unused since 2026-01) ([#130](https://github.com/ethereum/iptf-map/pull/130))
 - docs(domains): reframe [Domains index](domains/README.md), [Payments](domains/payments.md), [Identity & Compliance](domains/identity-compliance.md), [Funds & Assets](domains/funds-assets.md), [Trading](domains/trading.md), and [Data & Oracles](domains/data-oracles.md) to cover public-sector, NGO, and resilience contexts alongside FIs; add [Civic Coordination & Governance](domains/governance.md) domain; add `governance` to the use-case schema enum ([#170](https://github.com/ethereum/iptf-map/pull/170), closes [#169](https://github.com/ethereum/iptf-map/issues/169))
 - refactor(use-cases): rename `## 2) Additional Business Context` to `## 2) Additional Context` across [_template](use-cases/_template.md) and 23 use-case cards; strip reader-facing "Confidential context" placeholder line from 20 private-* cards ([#170](https://github.com/ethereum/iptf-map/pull/170), closes [#169](https://github.com/ethereum/iptf-map/issues/169))
 - feat(use-case): [Resilient Civic Participation](use-cases/resilient-civic-participation.md) -- credentialed petition protocol with per-signer forward-secure ratcheting, blob-anchored signature batches, and a chain-state-only resolution SNARK (ECI, repository governance, workplace organising); adds [Approach: Civic Participation](approaches/approach-civic-participation.md) and generic patterns [Forward-Secure Pseudorandom Tree](patterns/pattern-forward-secure-pseudorandom-tree.md) and [Blob-Anchored State With KZG Dispute](patterns/pattern-blob-anchored-state-with-dispute.md) ([#165](https://github.com/ethereum/iptf-map/pull/165))

CONTRIBUTING.md

@@ -44,15 +44,6 @@ Example entry:
 - [New pattern name](patterns/pattern-slug.md) (#123)
 ```
 
-### Weekly Summaries
-
-Generate a weekly summary for sharing:
-
-```bash
-./scripts/weekly-summary.sh           # Last 7 days
-./scripts/weekly-summary.sh 2026-01-08 2026-01-15  # Custom range
-```
-
 ## CROPS Evaluation
 
 CROPS are the four non-negotiable properties defined by the Ethereum Foundation. They are indivisible: a solution that satisfies three out of four is not CROPS-aligned.

approaches/approach-civic-participation.md

@@ -1,7 +1,7 @@
 ---
 title: "Approach: Civic Participation"
-status: draft
-last_reviewed: 2026-05-13
+status: ready
+last_reviewed: 2026-06-24
 
 use_case: resilient-civic-participation
 related_use_cases: [resilient-identity-continuity]
@@ -115,7 +115,7 @@ This is a perspective for legal review by the deploying institution, not legal a
 
 ### Default
 
-For petitions whose threat model includes compelled disclosure, successor-regime inheritance, or operator breach, default to the **Resilient Civic Participation Protocol**. Durability and dispute coverage come from the bounty-funded Resolver and the on-chain Registry; the deploying institution carries no signer roster after the petition closes.
+For petitions whose threat model includes compelled disclosure, successor-regime inheritance, or operator breach, default to the Resilient Civic Participation Protocol. Durability and dispute coverage come from the bounty-funded Resolver and the on-chain Registry; the deploying institution carries no signer roster after the petition closes.
 
 ### Decision factors