You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Deliverable:**`GM_webSocket` with `@connect` enforcement and abort support.
57
-
58
-
59
53
## Under Consideration
60
54
61
55
-**UC-1. Safari via Native App Container**[S40, S41] — Safari lacks `userScripts` API. Requires separate Swift project. Reconsider when user demand justifies it.
@@ -301,13 +295,6 @@ _(All Now-tier items are credential/compliance blocked — see `Roadmap_Blocked.
301
295
> Duplicates against existing Now/Next/Later/UC/Rejected tiers were filtered.
302
296
> Each item carries impact (1-5), effort (S/M/L/XL), and tier recommendation.
303
297
304
-
### RD-2. Dashboard i18n DOM Translation Pass
305
-
-**Tier:** Next | **Priority:** P2 | **Impact:** 4 | **Effort:** L
306
-
-**Source:** README ("dashboard interface is currently English-only"), locale:check:strict failure (~70 keys/locale missing)
307
-
-**Problem:** Manifest and extension messages are localized in 8 languages, but the dashboard UI (~5,190 lines) is entirely English. This blocks international adoption during the once-in-a-decade MV3 window.
308
-
-**Deliverable:** Wire `dashboard-i18n-v2.js` (already has 600 keys in 8 languages) into dashboard DOM. Add missing ~70 keys per locale. Gate with `npm run locale:check:strict` passing in CI.
309
-
-**Acceptance:** Dashboard renders translated strings for all 8 locales. `locale:check:strict` exits 0. No untranslated hardcoded English strings in UI-visible dashboard elements.
| RD26-10 | W3C WebExtensions WG draft charter |https://w3c.github.io/charter-drafts/2025/webextensions-wg.html|
597
-
598
-
## Improvement Pass (2026-06-26)
599
-
600
-
> Items below identified by systematic code-level audit of build pipeline,
601
-
> test infrastructure, CSS architecture, and accessibility compliance.
602
-
> Deduplicated against all existing tiers and prior RD additions.
603
-
604
-
### Next
605
-
606
-
#### IMP-7. Coverage Threshold Ratchet
607
-
-**Priority:** P2 | **Effort:** L
608
-
-**Problem:** Coverage thresholds sit at lines 36%, functions 39%, branches 25%, statements 34% — the measured baseline. Critical service worker code (storage, sync, GM API) should have higher coverage to prevent regressions.
609
-
-**Deliverable:** Phase 1 (v3.12.0): raise to 45/48/32/42. Phase 2 (v3.13.0): raise to 55/58/40/52. Phase 3: raise to 65/68/50/62. Each phase requires writing tests to fill gaps before ratcheting.
610
-
-**Acceptance:** Each phase's thresholds pass in CI before the next phase begins.
0 commit comments