chore(deps): upgrade LiveView to 1.2, gettext to 1.0, LiveDashboard and dns_cluster

[darwin67]

This is stacked on #82. It covers the Elixir upgrades that need a mix.exs constraint change.

Commit	Change	Notes
dns_cluster	0.2 → 0.3.1	Adds SRV queries and fixes {basename, query} lookups. Textbin passes a plain query or :ignore.
gettext	0.26 → 1.0	No breaking changes. The app already uses the Gettext.Backend style.
phoenix_live_view	1.1.33 → 1.2.12	Security: 1.2.7 fixes CVE-2026-58228 (GHSA-5cgh-g58j-m9cq), a scheme validation bypass in Phoenix.LiveView.Utils. The 1.1 changelog lists no backport. 1.1.33 already had the CVE-2026-64941 redirect fix.
style:	HEEx reformat	The 1.2 HTML formatter keeps an empty element's closing tag inline. Two templates change, so mix format --check-formatted stays green.
phoenix_live_dashboard	0.8.7 → 0.9.1	Dev-only, mounted at /dev/dashboard.
build: lumis	~> 0.3 → ~> 0.7.0	Holds lumis back. See below.

lumis is held at 0.7, not upgraded

From 0.9, lumis no longer bundles parsers. Each language is a separate lumis_wasm_* Hex package that wasmtime compiles at runtime. A language without its package renders as plain text and only logs a warning. I tried 0.10.3: every sample (Elixir, JS, Python, Rust, JSON, SQL, YAML) came back uncoloured, with no error. Lines also become <span> instead of <div>, and the line-number CSS and two tests depend on the <div>.

The old ~> 0.3 would have let mix deps.update --all make that jump silently, so this PR tightens it to ~> 0.7.0. Doing the upgrade properly means choosing:

• which parser packages to ship (the Syntax field is free text, and 0.7 bundles ~110 languages);
• a writable LUMIS_DATA_DIR for the compiled-module cache in the read-only container;
• which parsers to warm at boot.

That belongs in its own PR.

Verification

• mix precommit passes (582 tests). The suite also passes with S3 storage against SeaweedFS.
• mix deps.unlock --check-unused is clean, and mix deps.get reports no packages with advisories.
• LiveView 1.2's JS client in Chromium against the dev server, with no console or page errors:
  • log in;
  • create a paste through the phx-change/phx-submit form, with push_navigate to its page;
  • navigate live back to the list, then search;
  • delete, then restore from the Deleted tab;
  • load the settings and orgs pages;
  • drop and reconnect the socket.
• LiveDashboard's home, OS data, metrics, processes and Ecto stats pages load and connect with no client errors.
• The suite raises no new LiveView test warnings, including 1.2's new missing-form-id check. Every form has an id.

🤖 Generated with Claude Code

https://claude.ai/code/session_019fnjMN7WpEjQJD2zveakV6

---

Generated by Claude Code