packages/runes/src/tags/error.ts is a leftover from refrakt's predecessor. It emits a bare <tr> of four <td>s from a Markdoc ValidationError, has never had a producer, and cannot be written by an author without crashing the build.
Delete it.
Tracking started Sep 10 — check back for trends.
It is outside every convention the project has built since it arrived:
Engine config entry in config.ts | none — there is no Error: key |
| CSS in Lumina | none — rf-error appears nowhere |
Entry in contracts/structures.json | none |
| Doc page | none — listed in PAGELESS and EXCLUDED_RUNES |
| Fixture | none |
| Producer | none, in any version in this repo's history |
No BEM block, no modifiers, no contract, no styling — yet it is present in refrakt inspect --list and in language-server completions as "Error reporting table", category Semantic. Invisible to every convention, visible in every autocomplete.
tags is built by runeTagMap(runes) (packages/runes/src/rune.ts:76), which applies no internal filter, so {% error %} is author-writable. The schema declares no required attributes and the transform dereferences immediately:
const err = attrs.error as ValidationError; const code = new Tag('td', {}, [err.id]);
createContentModelSchema calls options.transform(...) with no try/catch (packages/runes/src/lib/index.ts:548). So an author who finds error in autocomplete and writes {% error /%} gets Cannot read properties of undefined (reading 'id') and a dead build. A rune no author can write correctly is worse than no rune.
Consistent with this, the fixture corpus has no error fixture — one would fail fixture-corpus.test.ts's transform does-not-throw assertion.
Three further tells that it has never executed: type and lines are declared and never read; children: [tag, code, level, message] disagrees with properties: { code, tag, level, message }; and no header row exists anywhere, so the four columns are unlabelled.
SPEC-130 originally proposed giving this rune its input. That is withdrawn. A bare <tr> is invalid HTML outside a table and nothing emits a wrapper, so the rune presumes a caller that collects many findings into <table><thead>… — that is, a page-level report. Adopting it would pick that model because a leftover row exists, not because it is right; the better precedent is snippet's error fence, which reports at the site of the problem and already ships.
If a findings table is later wanted, it should be designed as one — a block-level container owning its table, header row, config entry and CSS.
packages/runes/src/tags/error.ts is deletedpackages/runes/src/index.ts:6) and catalog entry (:260) are removed'error' is removed from EXCLUDED_RUNES in packages/runes/src/reference.ts'error' is removed from PAGELESS in scripts/check-rune-docs.mjsnodes.error = Markdoc.nodes.error (packages/runes/src/index.ts:737) is left untouched — it is Markdoc's built-in parse-error node and unrelatednpm test passes, including check-rune-docs and the CSS coverage testsnpx refrakt contracts --check still reports up to date (the rune was never in the contract, so the count drops by one with no other diff)refrakt inspect --list no longer offers error, and neither does language-server completionDeletion, then let the exception lists shrink. Both EXCLUDED_RUNES and PAGELESS are maintained "known gaps" sets, and removing an entry from each is the signal that this is cleanup rather than suppression — the same reasoning check-rune-docs.mjs gives for keeping those sets honest in the first place.
Check the rune count in any prose that states one before landing: the docs carry several such claims and the contract header reports "(N runes)".
Breaking in name only. Removing a catalogued rune is nominally a breaking change, but no user can have a working {% error %} in their content — writing it crashes the build. The affected set is provably empty, so this is safe in a minor.
packages/runes/src/rune.ts:76 — runeTagMap, which is why the tag is author-reachablepackages/runes/src/lib/index.ts:548 — the unguarded options.transform call