Externalize i18n and FAQ frontend assets

REVIEW.md

@@ -6,23 +6,15 @@ This document tracks only active work. Completed work is intentionally omitted a
 
 Active maintainability risks (priority order):
 
-1. Externalized frontend content assets are still pending (Low)
-- Translation and FAQ payloads are still embedded in executable JS (`wwwroot/js/i18n.js:1`-`wwwroot/js/i18n.js:799`).
-- Impact: content changes require touching behavior modules and increase review noise.
+- None at the moment.
 
 ## B) Active task list
 
-[P2] Externalize i18n and FAQ content from executable JS
-- Problem: Severity `Low`, Category `Complexity/Documentation`. Translation and FAQ payloads are embedded in code.
-- Evidence: `wwwroot/js/i18n.js:1`-`wwwroot/js/i18n.js:799`.
-- Recommendation: move language dictionaries and FAQ markdown into versioned data assets with schema checks.
-- Acceptance criteria (testable): `i18n.js` holds behavior only; assets load and render identical user-facing text.
-- Effort / Risk: `M / Low`.
-- Dependencies (if any): frontend module split is helpful but optional.
+- None.
 
 ## C) Suggested execution order
 
-1. Externalize i18n/FAQ assets.
+1. Add new items when fresh risks are identified.
 
 ## D) Guardrails