Deploy v11.1.0

.claude/commands/prepare-release.md

@@ -101,6 +101,7 @@ These accounts should be filtered from the contributors list:
 - `github-actions`
 - `github-actions[bot]`
 - `actions-user`
+- `myelinated-wackerow`
 
 **Keep the structure intact**:
 - Keep section headers (⚡️ Changes, 🌐 Translations, 🐛 Bug Fix, etc.)

AGENTS.md

@@ -68,6 +68,7 @@ This is the official Ethereum.org website - a Next.js application that serves as
 
 - Use `interface` for object shapes, `type` for unions/intersections
 - Prefer explicit typing over `any` (ESLint enforces `fixToUnknown`)
+- **NEVER leave unused variables or parameters** - ESLint `unused-imports/no-unused-vars` will fail the Netlify build. The only allowed unused arg pattern is a single underscore `_`. Do NOT use `_prefixedNames` (e.g., `_foo`) - either use the variable or remove it from the signature entirely.
 - Use generic constraints for reusable components
 - Export types from dedicated files in `@/lib/types`
 
@@ -279,3 +280,10 @@ Required for Matomo integration:
 - **Platform**: Netlify (config in `netlify.toml`)
 - **Next.js Integration**: Uses `@netlify/plugin-nextjs` for seamless Netlify and Next.js compatibility
 - **Monitoring**: Matomo analytics integration
+
+## Internal Infrastructure
+
+The following external-looking services are managed by the ethereum.org team:
+
+- **`s3-dcl1.ethquokkaops.io`** — S3-compatible object storage for app screenshots and media. Used by the data layer to serve images for the `/dapps` and app listing pages. Downtime here means broken images on the live site.
+- **Netlify Blobs** (`@netlify/blobs`) — Key-value store used by the data layer to cache API responses. Accessed via `src/data-layer/storage.ts`.

README.md

@@ -100,6 +100,12 @@ pnpm install
 
 > Note: On Ubuntu or Debian you may need to run `sudo apt update && sudo apt install nodejs npm` before running `corepack enable` or `pnpm install`.
 
+4. Set up environment variables
+
+```sh
+cp .env.example .env.local
+```
+
 #### Migrating from yarn to pnpm
 
 If you previously used `yarn` to install dependencies, you can safely migrate to `pnpm` by running the following commands:

app/[locale]/apps/[application]/page-jsonld.tsx

@@ -1,4 +1,4 @@
-import { AppData, FileContributor } from "@/lib/types"
+import { AppCategory, AppData, FileContributor } from "@/lib/types"
 
 import PageJsonLD from "@/components/PageJsonLD"
 
@@ -8,6 +8,19 @@ import {
 } from "@/lib/utils/jsonld"
 import { normalizeUrlForJsonLd, slugify } from "@/lib/utils/url"
 
+// Map internal app categories to schema.org enumerated applicationCategory values
+// https://schema.org/applicationCategory
+const APPLICATION_CATEGORY_MAP: Record<AppCategory, string> = {
+  DeFi: "FinanceApplication",
+  Collectibles: "EntertainmentApplication",
+  Social: "SocialNetworkingApplication",
+  Gaming: "GameApplication",
+  Bridge: "UtilitiesApplication",
+  Productivity: "BusinessApplication",
+  Privacy: "SecurityApplication",
+  DAO: "BusinessApplication",
+}
+
 export default async function AppsAppJsonLD({
   locale,
   app,
@@ -71,15 +84,22 @@ export default async function AppsAppJsonLD({
         mainEntity: { "@id": `${url}#applications` },
       },
       {
-        "@type": "SoftwareApplication",
+        "@type": "WebApplication",
         "@id": `${url}#applications`,
         name: app.name,
         description: app.description,
         url: app.url,
         image: app.image,
-        applicationCategory: app.category,
+        applicationCategory:
+          APPLICATION_CATEGORY_MAP[app.category] ?? "UtilitiesApplication",
         applicationSubCategory: app.subCategory.join(", "),
         operatingSystem: "Web Browser",
+        offers: {
+          "@type": "Offer",
+          price: "0",
+          priceCurrency: "USD",
+          availability: "https://schema.org/OnlineOnly",
+        },
         author: [
           {
             "@type": "Organization",

app/[locale]/community/events/page-jsonld.tsx

@@ -45,7 +45,9 @@ function buildHubSchemaNodes(
   if (schema.address) {
     placeNode.address = {
       "@type": "PostalAddress" as const,
-      streetAddress: schema.address.streetAddress,
+      ...(schema.address.streetAddress && {
+        streetAddress: schema.address.streetAddress,
+      }),
       addressLocality: schema.address.addressLocality,
       ...(schema.address.postalCode && {
         postalCode: schema.address.postalCode,
@@ -56,7 +58,7 @@ function buildHubSchemaNodes(
 
   if (schema.containedInPlace) {
     placeNode.containedInPlace = {
-      "@type": "LocalBusiness" as const,
+      "@type": "Place" as const,
       name: schema.containedInPlace.name,
       ...(schema.containedInPlace.url && {
         url: schema.containedInPlace.url,
@@ -69,6 +71,8 @@ function buildHubSchemaNodes(
     "@id": seriesId,
     name: schema.eventSeriesName ?? "Open Ethereum Coworking Hours",
     description: schema.eventDescription,
+    startDate:
+      schema.schedule.startDate ?? new Date().toISOString().split("T")[0],
     isAccessibleForFree: true,
     url: hub.coworkingSignupUrl,
     eventStatus: "https://schema.org/EventScheduled",

app/[locale]/developers/tutorials/page-jsonld.tsx

@@ -87,12 +87,15 @@ export default async function TutorialsPageJsonLD({
             "@type": "ListItem",
             position: index + 1,
             name: tutorial.title,
-            url: tutorial.href,
+            url: normalizeUrlForJsonLd(locale, tutorial.href),
             item: {
               "@type": "Course",
               name: tutorial.title,
-              description: tutorial.description,
-              url: tutorial.href,
+              description:
+                tutorial.description.length > 60
+                  ? tutorial.description.slice(0, 57) + "..."
+                  : tutorial.description,
+              url: normalizeUrlForJsonLd(locale, tutorial.href),
               provider: ethereumFoundationOrganization,
               courseMode: "online",
               educationalLevel: tutorial.skill ?? "beginner",

app/[locale]/roadmap/_components/roadmap.tsx

@@ -103,6 +103,12 @@ const RoadmapPage = () => {
       description: t("page-roadmap-statelessness-description"),
       href: "/roadmap/statelessness",
     },
+    {
+      icon: <ExtraSecurityIcon className="size-7" />,
+      title: t("page-roadmap-zkevm-title"),
+      description: t("page-roadmap-zkevm-description"),
+      href: "/roadmap/zkevm",
+    },
   ]
 
   // TODO: MATOMO EVENTS

docs/solutions/integration-issues/sanitizer-test-research.md

@@ -56,6 +56,21 @@
 | 45 | "Ether" translated as "الإيثار" (altruism) | ar #17105 | Crowdin/MT translates "ether" as "الإيثار" (altruism, a real Arabic word) instead of "الإيثر" (transliteration). Same class as brand garble corrections. | Medium -- wrong term |
 | 46 | `normalizeBlockHtmlLines` splits single-line `<div>content</div>` | id i18n/id-03-23T2228 | EN: `<div>text</div>` (one line) -> sanitizer splits to `<div>text\n</div>` (two lines) -- `normalizeBlockHtmlLines` unconditionally splits closing block HTML tags to their own line, even when the opening tag is on the same line (inline usage). MDX treats the split content as a paragraph and fails: "Expected a closing tag for `<div>` before the end of `paragraph`". Found in 6 files across 5 languages (id, tr, pt-br, ja, es). | Critical -- breaks MDX compilation |
 
+| 47 | Unquoted frontmatter value with YAML-special characters | it #17841 | `description: Una spiegazione degli account di Ethereum: le loro strutture dati...` -- colon-space (`: `) inside unquoted YAML value triggers `YAMLParseError: Nested mappings are not allowed`; existing `quoteFrontmatterNonAscii` only quotes values with non-ASCII chars, missing pure-ASCII values with YAML-special sequences | Critical -- breaks build |
+
+| 48 | `collapseInlineHtmlFromEnglish` matches across code fences and newlines | it #17841 | Inside ````tsx` fence: `<div>{error?.message}</div>\n \n</div>` -- regex `\s*</div>` crosses the blank line and collapses a separate `</div>` onto the previous line, producing `<div>{error?.message}</div></div>`. Two bugs: (1) no code fence protection, (2) `\s*` matches newlines allowing cross-line grabs | High -- corrupts code examples |
+| 49 | Lowercased MDX component name | de #17842 | `<emoji text=":tada:" size={1} />` instead of `<Emoji .../>` -- translation pipeline lowercases the PascalCase MDX component tag; MDX component names are case-sensitive, so the lowercased tag won't resolve to the registered component | Critical -- breaks rendering |
+| 50 | `removeOrphanedClosingTags` strips valid cross-line `</em>` | de #17842 | `<em>\ntext</em></li>` -- `<em>` is on line N, `</em>` is on line N+1; line-by-line counting sees no opener on line N+1 and strips `</em>` as orphaned, breaking MDX compilation. Regression from sanitizer's own orphan removal logic. | Critical -- breaks MDX compilation |
+
+| 49 | Orphaned `</em>` BEFORE `<a>` in HTML list items | pl #17445 | `<li></em><a href="...">EIP-145</a> - <em>text</li>` -- `</em>` appears before its opener `<em>`; `removeOrphanedClosingTags` sees balanced open/close counts on the line so doesn't remove it | Critical -- breaks MDX compilation |
+| 50 | Smart quote double-wrapping in YAML frontmatter | pl #17445 | `summaryPoint1: ""text""` -- value had smart quotes `\u201C...\u201D`; `quoteFrontmatterNonAscii` saw non-ASCII, didn't recognize smart quotes as existing quoting, wrapped in straight quotes producing double-wrapping | Critical -- breaks YAML parsing |
+| 51 | Extra spaces around `=` in JSX attributes | pl #17445 | `<a href = "https://...">` -- Crowdin introduces spaces around `=` in href and other JSX attributes; no sanitizer function normalizes this | High -- may break strict MDX parsers |
+| 52 | Orphaned opening backtick with missing closer | pl #17445 | `` `<nazwa opcodu>(...). `` -- opening backtick with no closing backtick; `repairUnclosedBackticks` needs English comparison and may miss cases where English also has backticks but the translated line lost one | High -- exposed MDX tags |
+| 53 | Crowdin misplaces closing backtick before JSX fragment closer | sw #17521 | EN: `` (`<> ... </>`) `` -> SW: `` (`<> ...` </>) `` -- Crowdin moves closing backtick before `</>`, then `escapeMdxAngleBrackets` escapes the exposed `</>` as `\</>`. Fix: detect `` `<content>` </>) `` pattern and move closing backtick to include `</>` | Critical -- breaks MDX display |
+| 54 | Double punctuation after orphaned tag removal | sw #17521 | `kutoa.</em></em>.` -> `kutoa..` -- `removeOrphanedClosingTags` strips orphaned `</em>` tags but leaves behind double periods where the tag sat between two periods. Fix: collapse `..` to `.` after orphan removal | Low -- cosmetic but noticeable |
+| 55 | Escaped quotes `\"` in MDX JSX attributes | sw #17521 | `<ButtonLink variant=\"outline-color\" href=\"/roadmap/\">` -- Crowdin backslash-escapes quotes in JSX attributes; valid in JSON but breaks MDX compilation | Critical -- breaks build |
+| 56 | Translated interpolation placeholders in JSON | sw #17521 | EN: `{days}` -> SW: `{siku}` -- Crowdin translates the variable name inside `{}` braces; the app expects the English key name | Critical -- breaks rendering |
+
 ## Patterns Already Handled by Sanitizer (Confirmed Working)
 
 These patterns are covered by existing fix functions and should have regression tests:
@@ -99,6 +114,12 @@ These patterns are covered by existing fix functions and should have regression
 - **Translated inline code warning** (`warnTranslatedInlineCode`) — warns when inline code span count drops significantly OR when orphaned backticks are detected on a line; signals Crowdin translated content inside backticks (pt-br PR #17122)
 - **LLM artifact token stripping** (`stripLlmArtifactTokens`) — strips `<bos>`, `<eos>`, `<s>`, `</s>`, `<pad>`, `<unk>`, `<mask>` tokens from prose; these leak from machine translation pipelines and break MDX compilation (mr PR #17730)
 - **Block HTML inline usage preserved** (`normalizeBlockHtmlLines`) — no longer splits `<div>content</div>` when both tags are on the same line; only splits multi-line block closing tags to their own line. Fixes MDX "Expected a closing tag before end of paragraph" error (id i18n/id-03-23T2228, pattern #46)
+- **Lowercased MDX component names** (`fixLowercasedMdxComponents`) — `<emoji>` -> `<Emoji>` restores PascalCase from English source; translation pipelines occasionally lowercase custom component tags, and MDX component names are case-sensitive (de PR #17842, pattern #49)
+- **Orphaned closer-before-opener** (`removeOrphanedClosingTags`) — `</em><a>...<em>text</em>` now correctly removes the leading `</em>` even when open/close counts are equal on the line; uses left-to-right balance scanning instead of simple count comparison (pl PR #17445, pattern #50)
+- **Smart quote double-wrapping prevention** (`quoteFrontmatterNonAscii`) — replaces smart/curly quotes (U+201C/U+201D/U+201E/U+201F) with straight `"` before checking if YAML value needs quoting, preventing `""text""` double-wrapping (pl PR #17445, pattern #51)
+- **JSX attribute spacing** (`fixJsxAttributeSpacing`) — normalizes `href = "..."` to `href="..."` inside HTML/JSX tags; Crowdin sometimes introduces spaces around `=` in attributes (pl PR #17445, pattern #52)
+- **Escaped backtick inside inline code** (escaped-backtick fix) — `\`` replacement now skips inline code spans to preserve `\` as legitimate content in `` `\` ``; previously stripped the backslash leaving empty backticks `` `` `` (bn PR #17866, pattern #53)
+- **Block component regex over-matching** (`fixBlockComponentLineBreaks`) — `Alert` regex no longer matches `AlertTitle`/`AlertEmoji` etc.; added negative lookahead `(?![A-Za-z])` after component name to prevent prefix matching (bn PR #17866, pattern #54)
 
 ## Recommendations for Future Sanitizer Iteration
 

docs/solutions/logic-errors/post-import-sanitizer-cjk-punctuation-not-fixed.md

@@ -0,0 +1,95 @@
+---
+title: "Sanitizer Bug: CJK Punctuation Not Auto-Fixed in Non-CJK Locales"
+date: 2026-03-25
+category: logic-errors
+component: src/scripts/i18n/post_import_sanitize.ts
+tags:
+  - i18n
+  - sanitizer
+  - cross-script
+  - cjk
+  - punctuation
+  - urdu
+severity: medium
+symptoms:
+  - "CJK ideographic full stop U+3002 appearing in Urdu (ur) translation files"
+  - "detectCrossScriptContamination warns but does not fix cross-script punctuation"
+  - "Detection pattern for non-CJK locales excludes CJK punctuation range U+3000-U+303F"
+root_cause: |
+  Two gaps in cross-script handling:
+  1. Detection patterns for non-CJK locales (ar, ur, hi, etc.) only covered CJK Unified
+     Ideographs (U+4E00-U+9FFF) but NOT CJK Symbols and Punctuation (U+3000-U+303F).
+     The ideographic full stop U+3002 falls in the latter range, so it was not detected.
+  2. detectCrossScriptContamination() only emits warnings -- it never modifies content.
+     Even if the character were detected, it would not be fixed automatically.
+resolution: |
+  Added fixCrossScriptPunctuation() that replaces CJK ideographic full stop U+3002
+  with locale-appropriate equivalents outside code fences:
+  - ar/ur: U+06D4 (Arabic full stop)
+  - hi/mr/bn: U+0964 (Devanagari danda)
+  - Latin/Cyrillic/other non-CJK: ASCII period
+  - CJK locales (ja, ko, zh, zh-tw): no-op (U+3002 is correct)
+  Wired into both processMarkdownFile and processJsonFile pipelines, placed before
+  detectCrossScriptContamination so warnings reflect post-fix state.
+  11 unit tests added.
+related:
+  - docs/solutions/integration-issues/sanitizer-test-research.md
+  - docs/solutions/integration-issues/post-import-sanitizer-bugs-found-japanese-review.md
+discovered_in: "PR #17854 (Urdu full translation)"
+files_affected:
+  - public/content/translations/ur/developers/docs/standards/tokens/erc-1363/index.md
+  - src/intl/ur/glossary-tooltip.json
+---
+
+# Sanitizer Bug: CJK Punctuation Not Auto-Fixed in Non-CJK Locales
+
+## Problem
+
+During review of PR #17854 (Urdu translation), two instances of CJK ideographic full stop
+(`U+3002`) were found in Urdu files where the Urdu full stop (`U+06D4`) was expected:
+
+- `erc-1363/index.md` line 191: inside a Solidity code comment
+- `glossary-tooltip.json` line 165: in the zk-proof definition value
+
+These are classic Gemini cross-script leak artifacts -- the model occasionally copies
+punctuation from CJK training data into non-CJK output.
+
+## Root Cause
+
+The sanitizer had `detectCrossScriptContamination()` which warned about foreign characters,
+but:
+
+1. **Detection gap**: The `ur` detector pattern was `[\u0900-\u097F\u4E00-\u9FFF\u0400-\u04FF]`,
+   covering CJK ideographs but NOT CJK punctuation (`\u3000-\u303F`). The full stop `U+3002`
+   is in the punctuation range, so it was invisible to the detector.
+
+2. **No auto-fix**: Even if detected, the function only pushes to the warnings array. It never
+   modifies content.
+
+## Fix
+
+Added `fixCrossScriptPunctuation(content, locale)` that:
+
+- Processes content line-by-line with fence tracking (same pattern as `escapeMdxAngleBrackets`)
+- Skips code fences and inline code spans
+- Maps `U+3002` to the locale-appropriate full stop
+- Returns `{ content, fixCount }` like all other fix functions
+
+Locale mapping:
+
+| Locale Group | Replacement | Unicode |
+|-------------|-------------|---------|
+| ar, ur | Arabic full stop | U+06D4 |
+| hi, mr, bn | Devanagari danda | U+0964 |
+| ja, ko, zh, zh-tw | No-op (correct) | U+3002 |
+| All other | ASCII period | U+002E |
+
+## Tests
+
+11 tests in `tests/unit/sanitizer/standalone-fixes.spec.ts`:
+- Per-locale replacement (ur, ar, hi, de, ru)
+- CJK locale no-op (ja, zh)
+- Code fence skipping
+- Multiple occurrences
+- Empty locale guard
+- No-op when clean

docs/solutions/logic-errors/post-import-sanitizer-span-wrapped-backticks.md

@@ -0,0 +1,68 @@
+---
+title: Fix <span dir="ltr"> wrapping backtick inline code in RTL translations
+date: 2026-03-25
+category: logic-errors
+component: Translation post-import sanitizer
+tags:
+  - mdx
+  - rtl
+  - bidi
+  - inline-code
+  - sanitizer
+  - translation
+  - span-dir-ltr
+severity: high
+recurring: true
+languages_affected:
+  - ar
+  - ur
+files_modified:
+  - src/scripts/i18n/post_import_sanitize.ts
+  - tests/unit/sanitizer/standalone-fixes.spec.ts
+---
+
+# Fix `<span dir="ltr">` wrapping backtick inline code in RTL translations
+
+## Problem Symptom
+
+In RTL translation files (Arabic, Urdu), inline code wrapped in markdown backticks was rendered as broken text instead of properly formatted code. The MDX output contained patterns like:
+
+```
+<span dir="ltr">`APPLY(S,TX) -> S'`</span>
+```
+
+MDX cannot nest markdown syntax (backticks) inside JSX (`<span>` tags). The backtick content renders as literal broken text instead of an inline code block.
+
+## Root Cause Analysis
+
+Two sources produce this invalid pattern:
+
+1. **Sanitizer's own RTL fixes**: `fixBareRtlDates` and `fixBareRtlEquations` wrap bare LTR content (dates, math equations) in `<span dir="ltr">...</span>` for BiDi correctness. While the `RTL_SKIP_PATTERN` regex is designed to skip inline code, edge cases can result in backtick content being wrapped.
+
+2. **Gemini translations**: The LLM translator sometimes produces `<span dir="ltr">` wrappers around backtick content directly in its output.
+
+In both cases, the `<span dir="ltr">` wrapper is redundant because inline code in backticks is already inherently LTR (rendered in a monospace Latin font by the browser).
+
+## Fix Applied
+
+Added a new sanitizer function `fixSpanWrappedBackticks` that:
+
+1. Splits content on code fences (to avoid modifying fenced code blocks)
+2. Finds all instances of `<span dir="ltr">` followed by backtick content followed by `</span>`
+3. Replaces with just the backtick content (stripping the span wrapper)
+4. Handles optional whitespace between the span tags and the backtick content
+
+The function is placed in the pipeline immediately after `fixBareRtlDates` and `fixBareRtlEquations`, so it cleans up after them. It also handles cases where Gemini produced the pattern directly.
+
+### Regex pattern
+
+```typescript
+/<span dir="ltr">\s*(`[^`]+`)\s*<\/span>/g
+```
+
+This matches `<span dir="ltr">` + optional whitespace + backtick-delimited content + optional whitespace + `</span>`, and replaces with just the backtick content (capture group 1).
+
+## Verification
+
+- Unit tests added in `tests/unit/sanitizer/standalone-fixes.spec.ts`
+- Tests cover: basic unwrapping, multiple occurrences, non-backtick spans left alone, bare backticks left alone, whitespace handling, no-op case, correct fixCount, code fence skipping