on_the_money 0.7.1 → 0.7.2

package/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.7.2] — 2026-07-20
+
+### Changed
+
+- **HTML-106 promoted from warn to error tier.** The production trial closed with zero false positives across both consumers and one true positive (a `the()` write projecting into a slot that doesn't exist — dead state the deletion test exists to catch). Runs that previously reported-and-passed now fail on unconsumed global keys; consume the key or delete the write. The warn-tier machinery remains for future rules. (#136)
+- **HTML-107 pairs by CSS reference, not name coupling** (landed post-0.7.1 as #144): the state key revealing a span may be named anything — a reveal rule necessarily references the span it reveals, so the reference is the proof. Kills the false-positive class that condemned functional cross-named wiring. (#143)
+
 ## [0.7.1] — 2026-07-19
 
 Port feedback, same day: the first downstream migrations onto the 0.7.0 batteries surfaced three regressions. Issues #132–#135, #137; PRs #138–#142.

package/README.md

@@ -763,8 +763,8 @@ npx otm-lint --check ./src
 | **HTML-103** | `data-i18n-{var}` attr has no matching `{var}` placeholder in the dictionary template | The token is silently dropped at runtime. Either remove the unused attr or add `{var}` to the template. |
 | **HTML-104** | A global `the("key", ...)` write collides with a `data-text="key"` slot inside a `<template>` | Global writes walk the whole document and clobber every cloned instance. Rename the template slot key or the global key. |
 | **HTML-105** | `data-action` values and `on()` `[data-action="..."]` selector literals disagree | Both directions: a `data-action` no handler references is a dead control; a selector no element carries is an orphan handler. A generic `[data-action]` dispatch selector in JS waives the dead-control direction; `data-otm-dynamic` opts an element out. |
-| **HTML-106** *(warn)* | A globally written state key nothing consumes | The deletion test as lint: no CSS attribute selector, `[data-text]` slot, `"data-key"` JS string literal (e.g. MutationObserver `attributeFilter`), or `the("key")` read touches it — dead state or a missing CSS rule. Warn-level: reported, never fails the run. |
-| **HTML-107** | A `data-K-key="V"` reveal span with no `[data-K="V"]` state-CSS rule, or a CSS `[data-K-key="V"]` reference with no span | Either half missing means the message silently never shows (or the rule is dead wiring). Add the missing half or delete the orphan; `data-otm-dynamic` opts a span out of the span→CSS direction. |
+| **HTML-106** | A globally written state key nothing consumes | The deletion test as lint: no CSS attribute selector, `[data-text]` slot, `"data-key"` JS string literal (e.g. MutationObserver `attributeFilter`), or `the("key")` read touches it — dead state or a missing CSS rule. Promoted from warn to error after a zero-false-positive production trial. |
+| **HTML-107** | A `data-K-key="V"` reveal span no state-CSS rule references, or a CSS `[data-K-key="V"]` reference no element carries | Pairing is by CSS reference — the state key revealing a span may be named anything (`body[data-form-error="V"] [data-error-key="V"]` is fine). Either half missing means the message silently never shows (or the rule is dead wiring); `data-otm-dynamic` opts a span out of the span→CSS direction. |
 
 `otm-lint` walks `.html`, `.ejs` (cross-file rules only — per-file rules stay `.html`), `.js`, `.css`, and locale `.json` files. HTML files get the per-file rules above (template content included); `.js` files contribute `$.clone` references, `the()` write/read keys, and `data-action` selectors; `.css` files contribute attribute-selector consumption for HTML-106; locale dicts get loaded per HTML file's `<meta name="i18n">` for HTML-102/103. Default excludes: `node_modules`, `dist`, `.git`, dotdirs. Exit code is nonzero when error-level violations are found.
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "on_the_money",
-	"version": "0.7.1",
+	"version": "0.7.2",
 	"description": "Opinionated, attribute-driven, standards-oriented modern framework. Native browser APIs only. See README.md for the authoring context.",
 	"type": "module",
 	"main": "src/core/index.js",

package/src/linter/Linter.js

@@ -371,7 +371,6 @@ export default class Linter {
 				{ line: writer.line, column: 1 },
 				"HTML-106",
 				`State key "${key}" is written via the() but never consumed by a CSS attribute selector, a [data-text] slot, or a JS data-attribute reference — dead state or a missing CSS rule (the deletion test).`,
-				"warn",
 			);
 		}
 
@@ -405,13 +404,18 @@ export default class Linter {
 		}
 
 		// Inline <style> blocks ride along in the raw HTML sources.
+		// Pairing is by CSS *reference*, never by name coupling: the state key
+		// that reveals a span may be named anything (body[data-form-error="V"]
+		// revealing [data-error-key="V"] is fully functional) — a reveal rule
+		// necessarily references the span it reveals, so the ref IS the proof.
 		const styleTexts = [...cssSources, ...htmlSources];
-		const stateRules = new Set();
 		const spanRefs = [];
+		const refPairs = new Set();
 		for (const { file, source } of styleTexts) {
 			for (const m of source.matchAll(
 				/\[data-([a-z0-9-]+?)-key=["']?([\w-]+)["']?\]/g,
 			)) {
+				refPairs.add(`${m[1]} ${m[2]}`);
 				spanRefs.push({
 					group: m[1],
 					value: m[2],
@@ -419,21 +423,16 @@ export default class Linter {
 					line: Linter.#lineOf(source, m.index),
 				});
 			}
-			for (const m of source.matchAll(
-				/\[data-([a-z0-9-]+)=["']?([\w-]+)["']?\]/g,
-			)) {
-				if (!m[1].endsWith("-key")) stateRules.add(`${m[1]} ${m[2]}`);
-			}
 		}
 
 		for (const span of revealSpans) {
-			if (stateRules.has(`${span.group} ${span.value}`)) continue;
+			if (refPairs.has(`${span.group} ${span.value}`)) continue;
 			Linter.#addViolation(
 				violations,
 				span.file,
 				{ line: span.line, column: span.column },
 				"HTML-107",
-				`Reveal span data-${span.group}-key="${span.value}" has no state-CSS rule matching [data-${span.group}="${span.value}"] — the message can never show. Add the reveal rule, or delete the span, or mark it data-otm-dynamic.`,
+				`Reveal span data-${span.group}-key="${span.value}" is referenced by no state-CSS rule — the message can never show. Add a reveal rule selecting [data-${span.group}-key="${span.value}"], or delete the span, or mark it data-otm-dynamic.`,
 			);
 		}