Merge pull request #1012 from sammajayi/feat/voting-deadline-reminders

feat: notify token holders before governance voting deadline closes

Author: Anuoluwapo25

.github/workflows/contracts.yml

@@ -16,6 +16,9 @@ jobs:
       - name: Setup stable Rust toolchain
         uses: dtolnay/rust-toolchain@stable
 
+      - name: Add WASM target
+        run: rustup target add wasm32v1-none
+
       - name: Run contract tests
         run: |
           set -euo pipefail

.github/workflows/e2e.yml

@@ -15,7 +15,7 @@ jobs:
 
       - uses: actions/setup-node@v4
         with:
-          node-version: 20
+          node-version: 22
           cache: npm
 
       - name: Install dependencies

.github/workflows/security-scan.yml

@@ -14,7 +14,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: '22'
           cache: 'npm'
       - name: Install dependencies
         run: npm ci --legacy-peer-deps --force

.size-limit.json

@@ -1,17 +1,17 @@
 [
   {
-    "name": "Main Next.js Chunk",
-    "path": ".next/static/chunks/main-*.js",
-    "limit": "150 kB"
+    "name": "Main Bundle",
+    "path": "dist/assets/*.js",
+    "limit": "250 kB"
   },
   {
     "name": "Framework/Vendor Chunks",
-    "path": ".next/static/chunks/framework-*.js",
-    "limit": "100 kB"
+    "path": "dist/assets/framework-*.js",
+    "limit": "150 kB"
   },
   {
     "name": "CSS Assets",
-    "path": ".next/static/css/**/*.css",
+    "path": "dist/assets/*.css",
     "limit": "50 kB"
   }
-]
+]

I18N_COMPLETION.md

@@ -1,19 +1,26 @@
 # i18n Internationalization Completion Summary
 
 ## Problem Solved
-The LearnVault application had full i18next configuration but extremely poor translation coverage:
+
+The LearnVault application had full i18next configuration but extremely poor
+translation coverage:
+
 - **English (en.json)**: 103 keys ✅ Complete
 - **Spanish (es.json)**: 103 keys → **was partial, now complete** ✅
 - **French (fr.json)**: 3 keys → **was 3%, now 100%** ✅
 - **Swahili (sw.json)**: 4 keys → **was 4%, now 100%** ✅
-- **Pashto (ps.json)**: Empty pseudo-locale (confusing, now removed from imports)
+- **Pashto (ps.json)**: Empty pseudo-locale (confusing, now removed from
+  imports)
 
-Users selecting these languages would see broken UI (untranslated keys) instead of a functional app.
+Users selecting these languages would see broken UI (untranslated keys) instead
+of a functional app.
 
 ## Changes Made
 
 ### 1. Configuration Updates
+
 **File**: `src/i18n.ts`
+
 - ✅ Added `es` (Spanish) to `supportedLngs` array
 - ✅ Removed unused `ps` (Pashto pseudo-locale) from imports and resources
 - **Before**: `supportedLngs: ["en", "fr", "sw"]`
@@ -22,11 +29,13 @@ Users selecting these languages would see broken UI (untranslated keys) instead
 ### 2. Translation Files
 
 #### Spanish (es.json) - 103 keys
+
 - **Status**: Already had 103 keys (complete!) but wasn't marked as supported
 - **Action**: Now officially supported
 - **Coverage**: 100% parity with en.json
 
 #### French (fr.json) - 3 → 103 keys
+
 - **Before**: Only had 3 nav keys (contractExplorer, dashboard, courses)
 - **After**: Complete professional French translations covering:
   - Navigation (16 keys)
@@ -38,37 +47,49 @@ Users selecting these languages would see broken UI (untranslated keys) instead
 - **Coverage**: 100% parity with en.json
 
 #### Swahili (sw.json) - 4 → 103 keys
-- **Before**: Only scattered keys (home.heroTitle, nav.{contractExplorer,dashboard,courses}, usdc.{getTestUSDC,minting,mintSuccess,mintError,tooltip})
+
+- **Before**: Only scattered keys (home.heroTitle,
+  nav.{contractExplorer,dashboard,courses},
+  usdc.{getTestUSDC,minting,mintSuccess,mintError,tooltip})
 - **After**: Complete Swahili translations using proper East African terminology
 - **Coverage**: 100% parity with en.json
 
 ### 3. CI/CD Validation
 
 #### New Script: `scripts/validate-i18n.mjs`
+
 Automated validation that ensures:
+
 - All supported locales (es, fr, sw) have complete key parity with en.json
 - No unexpected locale files are present
 - Fails the build if translations are incomplete
 - Warns about extra keys in locale files
 
 #### Updated: `package.json`
+
 Added new npm script:
+
 ```json
 "i18n-check": "node scripts/validate-i18n.mjs"
 ```
 
 #### Integration with CI
+
 The `frontend-ci.yml` workflow already includes:
+
 ```yaml
 - name: i18n key parity check
   run: npm run i18n-check
 ```
+
 This will now properly validate all translations before PRs can be merged.
 
 ### 4. Documentation
 
 #### New File: `docs/i18n-setup.md`
+
 Comprehensive guide covering:
+
 - Supported languages and status
 - Architecture and configuration
 - How to use translations in components
@@ -81,22 +102,30 @@ Comprehensive guide covering:
 ## Impact
 
 ### For Users
+
 - ✅ French speakers: Get a fully functional interface in their language
 - ✅ Swahili speakers: Get a fully functional interface in their language
 - ✅ Spanish speakers: Already had translations, now officially supported
 - ✅ All other languages: Fall back to English (as designed)
 
 ### For Developers
-- ✅ **Key parity enforcement**: CI will fail if new keys are added to en.json without updating all locales
+
+- ✅ **Key parity enforcement**: CI will fail if new keys are added to en.json
+  without updating all locales
 - ✅ **Clear process**: Documentation explains how to add/update translations
 - ✅ **Automated validation**: No need to manually check for missing keys
-- ✅ **Accessible codebase**: All 24 components using useTranslation now have proper translations
+- ✅ **Accessible codebase**: All 24 components using useTranslation now have
+  proper translations
 
 ### For the Project
-- ✅ **Aligns with mission**: "Designed specifically with African learners in mind" - now with French & Swahili
+
+- ✅ **Aligns with mission**: "Designed specifically with African learners in
+  mind" - now with French & Swahili
 - ✅ **Trust**: No more language switcher that silently breaks the UI
-- ✅ **Maintainability**: Future contributors can't accidentally create translation gaps
-- ✅ **Quality**: Professional native-speaker translations (not machine-generated)
+- ✅ **Maintainability**: Future contributors can't accidentally create
+  translation gaps
+- ✅ **Quality**: Professional native-speaker translations (not
+  machine-generated)
 
 ## Testing
 
@@ -115,25 +144,33 @@ npm run lint && npm run typecheck && npm run test:coverage
 
 ## Pashto (ps.json) Note
 
-The original `ps.json` file was generated by `generate-pseudo-locale.mjs` for testing purposes (to identify missing translation keys by wrapping text in `[[...]]`). It was never actually used as a language:
+The original `ps.json` file was generated by `generate-pseudo-locale.mjs` for
+testing purposes (to identify missing translation keys by wrapping text in
+`[[...]]`). It was never actually used as a language:
+
 - Never imported in `src/i18n.ts`
 - Never listed in `supportedLngs`
 - Not relevant to the project's African focus
 
-The script still works fine - it just generates this file in the background. The important fix is removing ps from the i18n config so it can't be accidentally enabled.
+The script still works fine - it just generates this file in the background. The
+important fix is removing ps from the i18n config so it can't be accidentally
+enabled.
 
 ## Migration Checklist for Teams Using LearnVault
 
 - [ ] Pull latest changes
 - [ ] Review new translations in `src/locales/{es,fr,sw}.json`
 - [ ] Test language switching in the UI (use LanguageSelector component)
 - [ ] Verify `npm run i18n-check` passes locally
-- [ ] Add translations for any new keys following the workflow in `docs/i18n-setup.md`
-- [ ] Update CI/CD pipeline if using a fork (frontend-ci.yml already has the check)
+- [ ] Add translations for any new keys following the workflow in
+      `docs/i18n-setup.md`
+- [ ] Update CI/CD pipeline if using a fork (frontend-ci.yml already has the
+      check)
 
 ## Future Improvements
 
 Potential enhancements for consideration:
+
 1. Add translator credits/attribution for es, fr, sw translations
 2. Set up crowdsourced translation management (e.g., Crowdin, Weblate)
 3. Add RTL language support (e.g., Arabic for North Africa)

README.md

@@ -572,7 +572,8 @@ expect all participants to uphold these standards.
 
 - [Glossary](docs/glossary.md) — Key terms, tokens, and contracts explained in
   plain English
- - [Contract events](docs/contract-events.md) — Documented on-chain event names, payloads, and example payloads for the indexer
+- [Contract events](docs/contract-events.md) — Documented on-chain event names,
+  payloads, and example payloads for the indexer
 
 ---