Follow the parser module rename in the coverage ignore list and guard against future orphaned entries

Author: kipcole9

CHANGELOG.md

@@ -10,6 +10,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 * Change the namespaces on the `leex` lexers and `yecc` parsers to avoid module name clash with `ex_cldr` versions. Thanks to @jerryluk for the PR. Closes #40.
 
+* The coverage ignore list follows the renamed lexer/parser modules, restoring measured coverage above the 90% CI threshold; a guard test now fails when an ignore-list entry names a module that no longer exists.
+
 ## [0.48.0] — July 8th, 2026
 
 ### Added

mix.exs

@@ -254,13 +254,13 @@ defmodule Localize.MixProject do
       Localizer.Rfc5646.Core,
       Localize.Number.PluralRule.Loader,
       Localize.Number.PluralRule.Transformer,
-      :rbnf_lexer,
-      :rbnf_parser,
-      :plural_rules_lexer,
-      :plural_rules_parser,
-      :decimal_formats_lexer,
-      :decimal_formats_parser,
-      :date_time_format_lexer
+      :localize_rbnf_lexer,
+      :localize_rbnf_parser,
+      :localize_plural_rules_lexer,
+      :localize_plural_rules_parser,
+      :localize_decimal_formats_lexer,
+      :localize_decimal_formats_parser,
+      :localize_date_time_format_lexer
     ]
   end
 

plans/demo_ideas.md

@@ -0,0 +1,41 @@
+# Conference demo ideas — Elixir/BEAM conference, 2027
+
+The organizers cultivate a "music festival" mood: light, relaxed, creative, energetic. The brief: a new project with a very cool demo and, ideally, audience participation. Four candidates, with a recommendation at the end.
+
+## 1. Emoji DJ — launch `localize_emoji` on stage
+
+Already on the roadmap ([plans/cldr-49.md](cldr-49.md) item 11): a sibling library for emoji search over CLDR annotations with boolean tag queries. Build it over the winter, launch it at the conference.
+
+**The demo.** A giant screen running a LiveView "emoji mixing desk". Type queries live — `face and (happy or mischievous) and not sad`, `"dark skin tone" and musician` — and the wall fills with results in the audience's languages, because annotations are per-locale. Then the drop: the audience joins by QR code, every phone becomes a search box, and matching emoji rain onto the big screen like festival crowd reactions, tagged with the locale that searched for them.
+
+**Why it fits.** Emoji are inherently light and playful; boolean query parsing is a satisfying little language-design story for a BEAM crowd; and the talk ends having shipped a real hex package the audience can add to a project before the next session. The October `ldml2json_v2` pipeline work is the data prerequisite, so the roadmap already points here.
+
+## 2. The Babel Wall — one app, every locale in the room, live
+
+A festival-themed LiveView app (lineup, set times, ticket prices, distances to stages) where each attendee joins on their phone and the app negotiates their locale from `Accept-Language` — the `best_match` story. The big screen is a wall of every locale currently in the room rendering the same screen: Arabic digits, Buddhist calendar dates, 24-hour vs 12-hour, currency symbol placement, km vs miles.
+
+**The demo moment.** "Let's add Japanese" — add one MF2 translation file live, hot-reload, and thirty phones in the room flip. Zero code change. Then a plural-rules quiz: everyone's phone shows "you have N messages" for their locale and the audience discovers together that Arabic has six plural forms.
+
+**Why it fits.** The strongest pure-Localize showcase — process-per-user locale is a genuinely BEAM-shaped design — and presence + PubSub with hundreds of phones is exactly what LiveView was born for.
+
+## 3. OTP Orchestra — the audience is the instrument
+
+Every phone that joins becomes a voice: a process emitting notes/samples, mixed through PubSub (or Membrane for real audio pipelines) into music played through the PA. Sections of the room get instruments by seating block; a conductor view mutes, solos, and layers the crowd. Latency compensation and back-pressure are the technical meat — GenStage as a rhythm section.
+
+**Why it fits.** Maximum festival energy — the room literally makes music together — and "a thousand processes are playing this song right now" is the most visceral BEAM demo there is. The localization tie is thinner (per-locale phone UI, note names per locale), so this trades maintainer authority for spectacle. Highest on-stage failure risk (live audio).
+
+## 4. The Great Collation Race
+
+Sorting as spectator sport. The audience submits words — names, band names, words from their languages — and the big screen animates the same list re-sorting live under different collations: default UCA, German phonebook, Swedish, zh-pinyin vs zh-stroke, numeric mode, backwards French accents. Bars slide past each other like a horse race; the audience bets on where "Öztürk" lands before each round.
+
+**Why it fits.** Collation is the most underexplained topic in software and the animation makes it instantly visible. Probably a 10-minute segment rather than a whole talk — which is why it composes well with ideas 1 or 2.
+
+## Recommendation
+
+**Idea 1 (Emoji DJ) as the spine, with idea 4 as a segment.** It is the only option that leaves a real artifact behind — a new library launched on stage, born from the existing roadmap — and emoji provide festival-mood visuals without manufactured whimsy. The participation mechanic is robust (worst case, people search emoji on their phones, which is already fun), whereas live audio has the highest failure risk. A successful talk doubles as `localize_emoji`'s launch day.
+
+## Timeline sketch
+
+* October 2026 — CLDR 49 cycle lands `ldml2json_v2` and the annotations data path (prerequisite).
+* Winter 2026/27 — build `localize_emoji` (package skeleton, normalizer, query DSL, LiveView demo shell).
+* Spring 2027 — talk outline, demo hardening (offline fallback, capacity test with simulated phones), collation-race segment.

test/localize/coverage_ignore_modules_test.exs

@@ -0,0 +1,27 @@
+defmodule Localize.CoverageIgnoreModulesTest do
+  use ExUnit.Case, async: true
+
+  # The coverage ignore list in mix.exs names modules by atom. A
+  # rename (e.g. the leex/yecc modules gaining the localize_ prefix)
+  # silently orphans an entry: the renamed module stops being
+  # excluded, counts as ~0% covered, and drags the total below the
+  # CI threshold with no pointer to the cause. This test makes the
+  # drift loud: every atom entry must be a loadable module.
+  test "every module atom in the coverage ignore list exists" do
+    ignored = Mix.Project.config()[:test_coverage][:ignore_modules]
+
+    missing =
+      for module <- ignored,
+          is_atom(module),
+          not Code.ensure_loaded?(module),
+          do: module
+
+    assert missing == [],
+           """
+           These coverage ignore_modules entries in mix.exs name modules
+           that do not exist (renamed or removed?): #{inspect(missing)}
+           Update the list or the renamed modules will count as
+           uncovered and drop the total below the CI threshold.
+           """
+  end
+end