mithril-lynx 2.0.0 → 2.0.2

package/FETCH_INVESTIGATION.md

@@ -70,7 +70,7 @@ y los `.d.ts` reales instalados en
 `fetch` está declarado como método del objeto `Lynx` dentro de
 `types/background-thread/` — **solo existe en el hilo background**, no
 en `common/` ni `main-thread/`. Encaja con la arquitectura entera de
-`mithril-lynx-v2` (toda la vista corre en background) — no hace falta
+`mithril-lynx` (toda la vista corre en background) — no hace falta
 ningún puente cross-thread para esto.
 
 ### 2.2 La firma real, completa, sin recortar
@@ -290,7 +290,7 @@ cancelación y timeout reales, que en la primera pasada de esta
 investigación parecían imposibles — funciona.
 
 **Recomendación**: implementar el subconjunto confirmado como
-`mithril-lynx-v2/request`, documentando explícitamente (no escondiendo)
+`mithril-lynx/request`, documentando explícitamente (no escondiendo)
 los 4-5 puntos sin equivalente, con una sugerencia directa de usar
 `lynx.fetch` nativo para esos casos puntuales.
 

package/README.md

@@ -53,6 +53,14 @@ renderApp({ root: () => m(Counter) });
 
 `m.request`, reimplemented as a wrapper over Lynx's own `fetch`. See [`REQUEST.md`](./REQUEST.md) for the full API, and [`FETCH_INVESTIGATION.md`](./FETCH_INVESTIGATION.md) for the complete option-by-option gap analysis against the real `m.request` spec, backed by real-device evidence rather than docs/types alone (which were wrong twice during that investigation).
 
+## Custom fonts
+
+Use a plain CSS `@font-face` rule — not `lynx.addFont()` (that JS API only fires post-mount, too late to win the first-frame race). Three gotchas, all confirmed on real hardware and inherited unchanged from the previous mithril-lynx (none of this is architecture-specific):
+
+- **The font file must be `.ttf`, not `.woff2`** — a `.woff2` `@font-face` compiles fine but the native text renderer silently never applies it.
+- **`font-family` set on `:root` (or any ancestor) does not cascade to descendants by default** — `pluginLynxConfig({ enableCSSInheritance: true })` turns that on.
+- **A declarative `@font-face` resolves synchronously on the first native `__FlushElementTree()` call**, and that cost scales with how many text nodes resolve it — up to +2s of cold start on a mid/low-end device. Filed upstream as [lynx-family/lynx#9431](https://github.com/lynx-family/lynx/issues/9431). The workaround is a native-side prefetch hook, not a JS-level fix — see [`ANDROID_APK_GUIDE.md`](./ANDROID_APK_GUIDE.md) Part D for the full procedure, or scaffold it directly with `create-mithril-lynx`'s `--with-font <file.ttf>` flag.
+
 ## Known gaps
 
 - **`m.trust`** — not present. Stripped from `mithril-runtime` at the source, and Lynx's Element PAPI has no innerHTML-equivalent injection point to reimplement it against anyway (same permanent gap v1 documented).
@@ -72,3 +80,4 @@ Runs against `@lynx-js/testing-environment`'s real Element PAPI simulation via `
 - `.omo/plans/m-route-en-memoria.md` — how `m.route` was designed and verified for an in-memory, URL-less environment.
 - `.omo/plans/m-request-fetch-lynx.md` — the `m.request`-vs-`fetch` investigation plan and its execution log.
 - [`ROUTE.md`](./ROUTE.md), [`REQUEST.md`](./REQUEST.md), [`FETCH_INVESTIGATION.md`](./FETCH_INVESTIGATION.md) — user-facing reference docs for the two Lynx-specific reimplementations.
+- [`ANDROID_APK_GUIDE.md`](./ANDROID_APK_GUIDE.md) — building a native Android host and APK from scratch, Gradle-CLI only, including the `.ttf` cold-start hack from "Custom fonts" above. Automated end to end by `create-mithril-lynx --android`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mithril-lynx",
-  "version": "2.0.0",
+  "version": "2.0.2",
   "description": "Mithril.js on Lynx: real mithril/render/render.js driven through a Lynx-backed fake DOM, with an explicit single commit hook (no conditional global flush) and three reload modes (data-light, structural-light, full). A complete rewrite of the previous mithril-lynx (0.0.x).",
   "license": "MIT",
   "type": "module",

package/plugin.d.ts

@@ -1,8 +1,8 @@
 import type { RsbuildPlugin } from "@lynx-js/rspeedy";
 
-export interface PluginMithrilLynxV2Options {
+export interface PluginMithrilLynxOptions {
 	targetSdkVersion?: string;
 	liveReload?: boolean;
 }
 
-export function pluginMithrilLynxV2(options?: PluginMithrilLynxV2Options): RsbuildPlugin;
+export function pluginMithrilLynx(options?: PluginMithrilLynxOptions): RsbuildPlugin;

package/plugin.js

@@ -1,24 +1,26 @@
 // plugin.js
 //
 // Rspeedy/Rsbuild plugin wiring the two-bundle build (main-thread/Lepus +
-// background/JS) for mithril-lynx-v2 apps. Adapted from mithril-lynx v1's
-// plugin.js — this file is build TOOLING, not the redraw/reload mechanism
-// that motivated the v2 rewrite (see mithril-lynx-v2-desde-cero.md §2: v1's
-// bugs lived in the shim/commit/reload layer, never here), so it is reused
-// with fixes rather than rewritten from nothing. Two real changes from v1:
+// background/JS) for mithril-lynx apps. Adapted from the previous
+// mithril-lynx's plugin.js — this file is build TOOLING, not the
+// redraw/reload mechanism that motivated the rewrite (see
+// mithril-lynx-v2-desde-cero.md §2: the old bugs lived in the
+// shim/commit/reload layer, never here), so it is reused with fixes
+// rather than rewritten from nothing. Two real changes from the old one:
 //
 // 1. (F0.2 fix, the actual point of this file's existence in the plan)
 //    `RuntimeWrapperWebpackPlugin`'s `test` regex now also matches
-//    `.hot-update.js` chunks. v1's regex (`${name}/background\.js$`)
+//    `.hot-update.js` chunks. The old regex (`${name}/background\.js$`)
 //    matched the initial background ASSET path (nested under
 //    `.rspeedy/<name>/`, with a slash) but never the flat, double-
 //    underscore-named hot-update chunk (`<name>__background.<hash>.hot-
 //    update.js`) — confirmed with a plain regex test against both real
-//    filenames, not a guess. That gap is the entire reason v1 needed a
-//    runtime monkey-patch of `lynx.requireModuleAsync` in its dev-reload
-//    client; v2's client has no such patch (see src/dev-reload-client.js).
+//    filenames, not a guess. That gap is the entire reason the old
+//    version needed a runtime monkey-patch of `lynx.requireModuleAsync`
+//    in its dev-reload client; this one's client has no such patch (see
+//    src/dev-reload-client.js).
 //
-// 2. Only ONE rendering mode exists (v2 plan §2 non-goals: no main-thread-
+// 2. Only ONE rendering mode exists (plan §2 non-goals: no main-thread-
 //    owned/data-channel modes) — so there is no mode-detection logic here,
 //    `dev.hmr` is unconditionally on in dev, and every entry always gets a
 //    background chunk.
@@ -31,7 +33,7 @@ import { fileURLToPath } from "node:url";
 import { RuntimeWrapperWebpackPlugin } from "@lynx-js/runtime-wrapper-webpack-plugin";
 import { LynxEncodePlugin, LynxTemplatePlugin } from "@lynx-js/template-webpack-plugin";
 
-const PLUGIN_NAME = "mithril-lynx-v2-template-webpack";
+const PLUGIN_NAME = "mithril-lynx-template-webpack";
 const STYLE_CANDIDATES = ["style.css"];
 
 const DEV_RELOAD_CLIENT_PATH = path.join(
@@ -105,7 +107,7 @@ function packageRootOf(resolvedFile, expectedName) {
 	return null;
 }
 
-export function pluginMithrilLynxV2(options = {}) {
+export function pluginMithrilLynx(options = {}) {
 	const targetSdkVersion = options.targetSdkVersion ?? "3.5";
 	const liveReload = options.liveReload ?? true;
 
@@ -114,8 +116,9 @@ export function pluginMithrilLynxV2(options = {}) {
 		setup(api) {
 			api.expose(Symbol.for("LynxTemplatePlugin"), { LynxTemplatePlugin });
 
-			// One mode only -> dev.hmr is unconditionally on in dev (v1 had to
-			// detect renderer-mode-vs-not here; v2 has no "not").
+			// One mode only -> dev.hmr is unconditionally on in dev (the old
+			// version had to detect renderer-mode-vs-not here; there is no
+			// "not" to detect anymore).
 			api.modifyRsbuildConfig({
 				handler: (config, { mergeRsbuildConfig }) => mergeRsbuildConfig(config, { dev: { hmr: true } }),
 				order: "post",
@@ -134,13 +137,12 @@ export function pluginMithrilLynxV2(options = {}) {
 			});
 
 			api.modifyBundlerChain((chain, { isDev, environment }) => {
-				// Force a single resolved copy of "mithril-runtime" and
-				// "mithril-lynx-v2" — a `file:`-linked local package can
-				// otherwise resolve a second physical copy with its own
-				// module-level state (this exact class of bug bit v1 twice:
-				// mithril's emptyAttrs singleton, and mithril-lynx's own
-				// per-app render state — see mithril-lynx/plugin.js's
-				// comments for the on-device symptom).
+				// Force a single resolved copy of "mithril-runtime" — a
+				// `file:`-linked local package can otherwise resolve a
+				// second physical copy with its own module-level state
+				// (this exact class of bug bit the previous mithril-lynx:
+				// mithril's own emptyAttrs singleton, and that framework's
+				// own per-app render state).
 				try {
 					const appRequire = createRequire(path.join(process.cwd(), "package.json"));
 					const mithrilDir = path.dirname(appRequire.resolve("mithril-runtime/package.json"));
@@ -148,17 +150,16 @@ export function pluginMithrilLynxV2(options = {}) {
 				} catch {
 					// App has no local "mithril-runtime" resolvable from its own root.
 				}
-				// Note: v1 also force-aliased its OWN package name here (a
-				// second copy of mithril-lynx would mean two disconnected
-				// renderers with separate module-level state — see
-				// mithril-lynx/plugin.js's comment for the on-device
-				// symptom). v2's per-app state lives inside closures created
-				// by `renderApp()`/`setupRenderer()` calls, not module-level
-				// variables — same class of bug can't reappear the same way,
-				// so this dedup isn't reproduced here. Revisit if a
-				// multi-copy scenario (npm link, a component library
-				// nesting its own copy) turns up the same symptom in
-				// practice.
+				// Note: the old mithril-lynx also force-aliased its OWN
+				// package name here (a second copy would mean two
+				// disconnected renderers with separate module-level state).
+				// This framework's per-app state lives inside closures
+				// created by `renderApp()`/`setupRenderer()` calls, not
+				// module-level variables — the same class of bug can't
+				// reappear the same way, so this dedup isn't reproduced
+				// here. Revisit if a multi-copy scenario (npm link, a
+				// component library nesting its own copy) turns up the same
+				// symptom in practice.
 
 				const rawEntries = Object.entries(chain.entryPoints.entries() ?? {});
 				chain.entryPoints.clear();
@@ -174,8 +175,8 @@ export function pluginMithrilLynxV2(options = {}) {
 					const cssSource = findSibling(dir, STYLE_CANDIDATES);
 					if (bgSource == null) {
 						throw new Error(
-							`[mithril-lynx-v2] entry "${name}": no sibling background.ts/background.js found next to ${mtSource}. ` +
-								"mithril-lynx-v2 has exactly one rendering mode and it always needs a background entry — see the plan's §2 non-goals.",
+							`[mithril-lynx] entry "${name}": no sibling background.ts/background.js found next to ${mtSource}. ` +
+								"mithril-lynx has exactly one rendering mode and it always needs a background entry — see the plan's §2 non-goals.",
 						);
 					}
 
@@ -231,7 +232,7 @@ export function pluginMithrilLynxV2(options = {}) {
 					);
 
 					console.info(
-						`[mithril-lynx-v2:build] entry="${name}" hmr=true liveReload=${liveReload} ` +
+						`[mithril-lynx:build] entry="${name}" hmr=true liveReload=${liveReload} ` +
 							`bgEntry=${bgEntry} mtEntry=${mtEntry} targetSdk=${targetSdkVersion}`,
 					);
 				}

package/src/apply-patch.js

@@ -13,8 +13,8 @@
 // content) is not a guess — it's the same contract `mithril-lynx/CONTRACT.md`
 // + `mithril-lynx/src/lynx-mithril-shim.js` already validated on a real
 // device (see mithril-lynx/DEVICE_VERIFICATION.md). Reusing a validated
-// mapping here is exactly the kind of "concept, not code" reuse the v2 plan
-// allows (§2 non-goals) — the bug we're rewriting away lives in the
+// mapping here is exactly the kind of "concept, not code" reuse the plan
+// allows (§2 non-goals) — the bug this rewrite fixes lives in the
 // commit/reload layer (commit.js, reload/*.js), never in this mapping.
 
 import { Op } from "./patch-protocol.js";
@@ -138,7 +138,7 @@ export function createPatchApplier(pageId, { onEvent } = {}) {
 					// as a test failure rather than a mystery on-device.
 					if (name === "*") {
 						throw new Error(
-							"[mithril-lynx-v2] Clearing the whole `style` object at once is not implemented yet (F3 TODO) — set individual properties to \"\" instead.",
+							"[mithril-lynx] Clearing the whole `style` object at once is not implemented yet (F3 TODO) — set individual properties to \"\" instead.",
 						);
 					}
 					__AddInlineStyle(handles.get(id), name, "");
@@ -169,7 +169,7 @@ export function createPatchApplier(pageId, { onEvent } = {}) {
 					break;
 				}
 				default:
-					throw new Error(`[mithril-lynx-v2] Unknown patch opcode: ${opcode}`);
+					throw new Error(`[mithril-lynx] Unknown patch opcode: ${opcode}`);
 			}
 		}
 		__FlushElementTree();

package/src/channel.js

@@ -15,8 +15,8 @@
 // v1's renderer/background.js and renderer/main-thread.js dispatching to
 // and listening on each other via exactly this pairing.
 
-export const patchEventName = "MithrilLynxV2:Patch";
-export const eventFromMainThreadEventName = "MithrilLynxV2:Event";
+export const patchEventName = "MithrilLynx:Patch";
+export const eventFromMainThreadEventName = "MithrilLynx:Event";
 export const renderPageEventName = "__RenderPage";
 export const destroyLifetimeEventName = "__DestroyLifetime";
 

package/src/commit.js

@@ -1,24 +1,24 @@
 // src/commit.js
 //
 // The single, explicit, non-conditional flush contract — this is the actual
-// fix for the regression that motivated the whole v2 rewrite (see
+// fix for the regression that motivated the whole rewrite (see
 // mithril-lynx-v2-desde-cero.md §3.4 and mithril-lynx/AGENTS.md's "Estado
-// actual" section for the v1 postmortem).
+// actual" section for the old implementation's postmortem).
 //
-// v1's bug in one sentence: whether a redraw actually reached the main
+// The old bug in one sentence: whether a redraw actually reached the main
 // thread depended on `typeof globalThis.__FlushElementTree === "function"`
 // — a question whose answer depended on thread/test/mode ordering. That is
 // a race condition baked into the architecture, not an edge case to patch.
 //
-// v2's rule: there is exactly one commit callback for the lifetime of one
-// `renderApp()` call (see background.js). It is installed explicitly, once,
-// by the code that owns the render — never discovered implicitly by
+// The rule here: there is exactly one commit callback for the lifetime of
+// one `renderApp()` call (see background.js). It is installed explicitly,
+// once, by the code that owns the render — never discovered implicitly by
 // whoever happens to ask first. Asking to commit before installing one is a
 // programmer error and throws immediately and loudly, on the same tick,
 // with a message that says exactly what's missing — never a silently
-// frozen screen (which is what v1 did instead).
+// frozen screen (which is what the old implementation did instead).
 
-const NOT_MOUNTED = Symbol("mithril-lynx-v2:not-mounted");
+const NOT_MOUNTED = Symbol("mithril-lynx:not-mounted");
 
 export function createCommitController() {
 	let commitFn = NOT_MOUNTED;
@@ -33,7 +33,7 @@ export function createCommitController() {
 		install(fn) {
 			if (commitFn !== NOT_MOUNTED) {
 				throw new Error(
-					"[mithril-lynx-v2] commit callback already installed. " +
+					"[mithril-lynx] commit callback already installed. " +
 						"A shim instance is single-use: one renderApp() call, one " +
 						"commit callback, for the lifetime of that background " +
 						"context. If you're re-mounting for a reload, create a new " +
@@ -55,7 +55,7 @@ export function createCommitController() {
 		commit() {
 			if (commitFn === NOT_MOUNTED) {
 				throw new Error(
-					"[mithril-lynx-v2] commit() called before renderApp() mounted " +
+					"[mithril-lynx] commit() called before renderApp() mounted " +
 						"the app. This is always a bug in the framework's own " +
 						"wiring, never something app code can trigger by accident " +
 						"— app code never calls commit() directly.",

package/src/dev-reload-client.js

@@ -114,7 +114,7 @@ function invokeCdpReload() {
 			if (!data) return;
 			try {
 				var parsed = JSON.parse(data);
-				if (parsed.error) console.error("[mithril-lynx-v2] Page.reload failed:", parsed.error.message);
+				if (parsed.error) console.error("[mithril-lynx] Page.reload failed:", parsed.error.message);
 			} catch (e) {
 				// response is not JSON — ignore
 			}
@@ -129,7 +129,7 @@ function reload(reason) {
 	if (socket) socket.close();
 	if (!invokeCdpReload()) {
 		console.warn(
-			"[mithril-lynx-v2] Live reload unavailable: NativeModules.LynxDevToolSetModule.invokeCdp was not found.",
+			"[mithril-lynx] Live reload unavailable: NativeModules.LynxDevToolSetModule.invokeCdp was not found.",
 		);
 	}
 }
@@ -191,7 +191,7 @@ function handleMessage(rawMessage) {
 	try {
 		message = JSON.parse(rawMessage);
 	} catch (e) {
-		console.warn("[mithril-lynx-v2] Ignoring an invalid dev-server message.");
+		console.warn("[mithril-lynx] Ignoring an invalid dev-server message.");
 		return;
 	}
 
@@ -219,7 +219,7 @@ function handleMessage(rawMessage) {
 			}
 			break;
 		case "errors":
-			console.warn("[mithril-lynx-v2] Build failed; waiting for the next successful build.", message.data);
+			console.warn("[mithril-lynx] Build failed; waiting for the next successful build.", message.data);
 			break;
 	}
 }
@@ -230,11 +230,11 @@ function connect(retries) {
 
 	socket = new WebSocket(socketURL(options));
 	socket.onmessage = function (event) { handleMessage(event.data); };
-	socket.onerror = function (error) { console.error("[mithril-lynx-v2] Dev server connection error:", error); };
+	socket.onerror = function (error) { console.error("[mithril-lynx] Dev server connection error:", error); };
 	socket.onclose = function () {
 		if (reloading) return;
 		if (retries >= 10) {
-			console.error("[mithril-lynx-v2] Unable to reconnect to the dev server.");
+			console.error("[mithril-lynx] Unable to reconnect to the dev server.");
 			return;
 		}
 		var delay = 1000 * Math.pow(2, retries) + Math.random() * 100;

package/src/fake-dom.js

@@ -21,7 +21,7 @@
 // Mithril's render.js at all — it only replays the recorded ops through
 // `apply-patch.js`, which calls the real Element PAPI directly. That split
 // is the point of the whole architecture (see
-// mithril-lynx-v2/.omo/plans/mithril-lynx-v2-desde-cero.md §3.1): only ONE
+// .omo/plans/mithril-lynx-v2-desde-cero.md §3.1): only ONE
 // side needs to be "a DOM", the other side only needs to be "a PAPI patch
 // applier".
 
@@ -186,7 +186,7 @@ export class LynxElement extends LynxContainerNode {
 			// CSS-text parser. Documented limitation, not a silent bug.
 			if (typeof console !== "undefined") {
 				console.warn(
-					"[mithril-lynx-v2] Assigning a CSS text string to `style` is not supported; use a style object.",
+					"[mithril-lynx] Assigning a CSS text string to `style` is not supported; use a style object.",
 				);
 			}
 			return;
@@ -265,7 +265,7 @@ export class LynxElement extends LynxContainerNode {
 		// already-empty-or-not container.
 		if (value !== "") {
 			if (typeof console !== "undefined") {
-				console.warn("[mithril-lynx-v2] Non-empty `textContent` assignment is not supported.");
+				console.warn("[mithril-lynx] Non-empty `textContent` assignment is not supported.");
 			}
 			return;
 		}
@@ -280,7 +280,7 @@ export class LynxElement extends LynxContainerNode {
 		// mithril-lynx/AGENTS.md history) rather than silently doing nothing
 		// with no signal.
 		if (typeof console !== "undefined") {
-			console.warn("[mithril-lynx-v2] `m.trust()` / innerHTML is not supported on Lynx elements.");
+			console.warn("[mithril-lynx] `m.trust()` / innerHTML is not supported on Lynx elements.");
 		}
 	}
 

package/src/mount-redraw.js

@@ -11,7 +11,7 @@
 //
 // Deliberately NOT a queue/pubsub of multiple mounted apps (real Mithril's
 // mount-redraw.js supports that because a browser page can `m.mount()`
-// several independent roots) — mithril-lynx-v2 has exactly one `renderApp()`
+// several independent roots) — mithril-lynx has exactly one `renderApp()`
 // for the app's whole lifetime (plan §3.1), so "the current redraw
 // function" is a single slot, not a list.
 //

package/src/request.js

@@ -36,7 +36,7 @@ function checkUnsupported(options) {
 	for (const [name, matches] of UNSUPPORTED) {
 		if (matches(options)) {
 			throw new Error(
-				`[mithril-lynx-v2/request] "${name}" is not supported — Lynx's fetch has no equivalent ` +
+				`[mithril-lynx/request] "${name}" is not supported — Lynx's fetch has no equivalent ` +
 					"(see FETCH_INVESTIGATION.md for exactly why). This throws instead of silently " +
 					"behaving differently from what you asked for.",
 			);
@@ -78,7 +78,7 @@ export function createRequestor(fetchImpl) {
 
 		if (typeof FormData !== "undefined" && options.body instanceof FormData) {
 			throw new Error(
-				"[mithril-lynx-v2/request] FormData bodies are not supported — Lynx has no FormData " +
+				"[mithril-lynx/request] FormData bodies are not supported — Lynx has no FormData " +
 					"at runtime (confirmed absent, see FETCH_INVESTIGATION.md). Use lynx.fetch directly " +
 					"if you have another way to send this data, or restructure it as plain JSON.",
 			);

package/src/route.js

@@ -13,7 +13,7 @@
 // `hasBeenResolved` gate) so porting route-using app code only requires
 // swapping the import, not relearning the control flow. The one
 // unavoidable signature change: `m.route(root, defaultRoute, routes)`
-// loses `root` — there is no DOM node to point it at in v2's architecture
+// loses `root` — there is no DOM node to point it at in this architecture
 // (a single `renderApp()` for the app's whole lifetime, plan §3.1) — see
 // the plan §5.2 for why that's a deliberate, documented deviation rather
 // than a fake DOM node just to keep the arg count.
@@ -100,7 +100,7 @@ export function createRoute() {
 	/**
 	 * @param {string} defaultRoute - Both the fallback for an unmatched path
 	 *   AND the screen the app starts on — there is no browser URL to read
-	 *   an initial path from, so this is the one path v2 always starts at
+	 *   an initial path from, so this is the one path the app always starts at
 	 *   (the closest in-memory equivalent of React Router's
 	 *   `initialEntries={["/"]}`).
 	 * @param {Record<string, unknown>} routes - Same shape as real

package/test/end-to-end.test.ts

@@ -11,8 +11,8 @@ import { createPatchApplier } from "../src/apply-patch.js";
 // call anywhere in the view below) produces a second patch that updates
 // the real tree again.
 //
-// This is the direct replacement for mithril-lynx v1's
-// `test/renderer-integration.test.ts` — same intent, rewritten for the v2
+// This is the direct replacement for the previous mithril-lynx's
+// `test/renderer-integration.test.ts` — same intent, rewritten for this
 // architecture (see mithril-lynx-v2-desde-cero.md §F1's acceptance
 // criterion: this must pass from the first commit, never be fixed later).
 

package/test/route-hot-reload.test.ts

@@ -14,7 +14,7 @@ describe("route.js + stable-host: a same-path re-resolve patches in place, never
 	it("swapping the live-bound view (module.hot.accept's job) produces only a SetText, no Create/Remove", () => {
 		lynxTestingEnv.switchToMainThread();
 		const capturedOps: unknown[][] = [];
-		lynx.getJSContext().addEventListener("MithrilLynxV2:Patch", (event: any) => {
+		lynx.getJSContext().addEventListener("MithrilLynx:Patch", (event: any) => {
 			capturedOps.push(event.data);
 		});
 

package/test/route.test.ts

@@ -21,7 +21,7 @@ function setupRealTree() {
 	// on the main-thread side so ops can be applied and the resulting real
 	// tree inspected.
 	lynxTestingEnv.switchToMainThread();
-	lynx.getJSContext().addEventListener("MithrilLynxV2:Patch", (event: any) => {
+	lynx.getJSContext().addEventListener("MithrilLynx:Patch", (event: any) => {
 		capturedOps.push(event.data);
 		lynxTestingEnv.switchToMainThread();
 		applier.applyPatch(event.data);

package/test/setup.ts

@@ -1,9 +1,9 @@
 // test/setup.ts
 //
 // The minimal gap-fill on top of @lynx-js/testing-environment's own PAPI
-// polyfill — same idea as mithril-lynx v1's testing.js, scoped down to only
-// what v2's apply-patch.js actually calls so far (no gestures/lists yet,
-// see the v2 plan's non-goals). `@lynx-js/testing-environment` already
+// polyfill — same idea as the previous mithril-lynx's testing.js, scoped
+// down to only what apply-patch.js actually calls so far (no gestures/lists
+// yet, see the plan's non-goals). `@lynx-js/testing-environment` already
 // implements __CreateView/__CreateText/__CreateElement/__CreateRawText/
 // __AppendElement/__InsertElementBefore/__RemoveElement/__SetAttribute/
 // __SetClasses/__AddInlineStyle/__FlushElementTree/__GetElementUniqueID —

package/test/structural-reload.test.ts

@@ -5,7 +5,7 @@ import { createVirtualBackend } from "../src/backends/virtual-backend.js";
 import { createLynxDocument } from "../src/fake-dom.js";
 import renderFactory from "mithril/render/render.js";
 
-// Tests the v2 plan's §3.6 hypothesis directly, WITHOUT a device: does
+// Tests the plan's §3.6 hypothesis directly, WITHOUT a device: does
 // re-rendering the SAME root/document with a structurally different tree
 // (a sibling inserted next to an unrelated, focused-in-spirit node) reuse
 // the unrelated node's id — i.e. does it survive as the SAME element,
@@ -20,7 +20,7 @@ import renderFactory from "mithril/render/render.js";
 // `<input>` keeps keyboard focus and in-progress text is a device-only
 // question (F4's real acceptance criterion).
 
-describe("structural re-render reuses unrelated nodes (v2 plan §3.6 hypothesis)", () => {
+describe("structural re-render reuses unrelated nodes (plan §3.6 hypothesis)", () => {
 	it("does not recreate a sibling `input`-like node when a new node is inserted next to it", () => {
 		const backend = createVirtualBackend();
 		const document = createLynxDocument(backend);
@@ -35,7 +35,7 @@ describe("structural re-render reuses unrelated nodes (v2 plan §3.6 hypothesis)
 		// Mithril's own (unkeyed-diff) middle-insertion trap to not apply —
 		// without keys, an unkeyed diff treats "insert in the middle" as
 		// "index 1 changed tag" and recreates everything from that index on,
-		// which is a real Mithril behavior, not a v2 bug. The un-keyed case
+		// which is a real Mithril behavior, not a bug here. The un-keyed case
 		// is deliberately NOT what this test asserts.
 		let showExtra = false;
 		function view() {