max / goingson

Take makeover-webview 0.52 and makeover-build 0.47 The 0.52.0 chrome around a FieldKind::Rich control adds .form-editor-modes and .form-editor-preview, and goingson writes neither: it has no markdown field, described or hand-written. Seal 37 to 39. The rise is arithmetic rather than a measurement, which no other rise in that comment is. quasi-webview still requires makeover-webview ^0.51.0 and the crate carries links, so the graph does not resolve here until that pin moves and the build script cannot run to count. The check is one-sided, so a lower real figure warns and asks for the seal to come down.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-20 15:04 UTC

Signed with PGP, not checked

Commit: 9280e8525ba8e38cdb0bd5366b81553711cd15a8

Parent: dda9a7c

2 files changed, +18 insertions, -4 deletions

M src-tauri/Cargo.toml +3 -3

			@@ -18,7 +18,7 @@
18	18		# Materialises all three generated files: themes/, geometry.css, layout.css,
19	19		# and holds both drift checks this build.rs used to carry itself: touch density
20	20		# as of 0.17, breakpoints as of 0.18.
21		-	makeover-build = "0.46.0"
	21	+	makeover-build = "0.47.0"
22	22		# Cuts the two house faces into frontend/fonts/. A git dependency because
23	23		# quasi-type is `publish = false`, which is also why makeover-build cannot do
24	24		# this and only emits the CSS that fetches the result. The rev is the one
			@@ -28,7 +28,7 @@
28	28		# The table CSS is generated here too: the columns are this app's, so the
29	29		# shared helper cannot know them, but the tracks and the narrowing rules come
30	30		# from the description rather than from hand-written nth-child cuts.
31		-	makeover-webview = "0.51.0"
	31	+	makeover-webview = "0.52.0"
32	32		makeover-layout = "0.31.0"
33	33		# Width. Direct rather than through makeover-webview, because the narrow table
34	34		# pass keys off SizeClass::Compact and a boundary reached transitively is a
			@@ -141,7 +141,7 @@
141	141		# The forms emitter and the description it renders. Runtime deps, not build:
142	142		# form markup depends on the value, the error and the options at the moment a
143	143		# modal opens, so it cannot be materialised the way the stylesheet is.
144		-	makeover-webview = "0.51.0"
	144	+	makeover-webview = "0.52.0"
145	145		makeover-layout = "0.31.0"
146	146		# Browser opening
147	147		open = { workspace = true }

M src-tauri/build.rs +15 -1

			@@ -608,10 +608,24 @@
608	608		/// otherwise, so there is no markup that should be writing these. It tightens
609	609		/// when the filters port, which is the one thing that would make them live.
610	610		///
	611	+	/// # 37 to 39: the markdown editor's chrome
	612	+	///
	613	+	/// `makeover-webview` 0.52.0 emits `.form-editor-modes` and
	614	+	/// `.form-editor-preview` around a `FieldKind::Rich` control, so the
	615	+	/// denominator went 67 to 69 and this app writes neither: goingson has no
	616	+	/// markdown field, described or hand-written, and its notes are plain text.
	617	+	///
	618	+	/// The rise is unverified rather than measured, which no other rise here is.
	619	+	/// `quasi-webview` still requires `makeover-webview` ^0.51.0 and that crate
	620	+	/// carries `links`, so the graph does not resolve on this machine until the
	621	+	/// pin moves and the build script cannot run to count. Two is the arithmetic,
	622	+	/// and the check is one-sided: if the real figure is lower it warns and asks
	623	+	/// for the seal to come down, which is the direction it is meant to move.
	624	+	///
611	625		/// The one direction this number should move is down, so if it ever needs
612	626		/// raising for a class goingson's own markup should be writing, that is the
613	627		/// defect this exists to catch and the answer is the markup, not the seal.
614		-	const DEAD_VOCABULARY_HIGH_WATER: usize = 37;
	628	+	const DEAD_VOCABULARY_HIGH_WATER: usize = 39;
615	629
616	630		/// Every file that can carry a class name.
617	631		fn markup_files(frontend: &Path) -> Vec<PathBuf> {