A required content-model field that matched nothing is reported

SPEC-186 D4: a required field, group or member that took no node is reported content-missing, and a child a required field skips is no longer dropped.

main View source

Criteria completion

Tracking started Nov 1 — check back for trends.

Relationships

ID:SPEC-186Status:accepted

A content model reads groups, nested blocks and trailing parts, and reports what is missing

ID:v0.47.0Status:active

v0.47.0 — Quotations and the content model

ID:WORK-701Status:ready

Promote content-missing to an error

Priority:lowComplexity:trivial

main current done

claude/milestone-v0-44-0-ism7ni done main done

Acceptance Criteria

A required field, group or member that took no node is reported content-missing, naming the field and the rune
A child skipped by a required field stays for the next field, and is reported content-unmatched only if nothing takes it
A sweep of site/content, the SEO fixtures and the composed fixtures lists every content-missing, and each is fixed or its field made optional
content-missing is a warning in this release; its promotion to an error is a follow-up item

References

SPEC-186: D4.

Resolution

Completed: 2026-11-03

Branch: claude/milestone-v0-44-0-ism7ni

What was done

packages/runes/src/lib/resolver.ts:
- noteMissing records required fields that took no node on the sink: a skipped required field, one reached after the children ran out, a failed required group, an unreserved required position: last, and nested members, dotted;
- findMissingFields;
- a required non-match no longer advances past (drops) the child.
packages/runes/src/lib/index.ts: content-missing findings at CONTENT_MISSING_LEVEL = 'warning'.
packages/content/src/validate.ts: content-missing in DEFAULT_VALIDATION_IDS.
Tests: resolver tests updated for D4.2 plus a new ran-out case; the validate id list test.
Docs: content-models guide, configuration reference.
WORK-701 created: the promotion to an error.

Sweep

refrakt validate on the main, staging and plan sites; SEO fixtures (53), core rune fixtures (41), plugin fixtures and composed-storytelling fixtures, each validated with its own tags.
Zero content-missing. A positive control (a playlist with no title) reported one, so the harness was live. Nothing needed fixing or making optional.

Notes

The behaviour change: content after an unmatched node that no later field can take is now reported rather than read by a later field. That is D4.2 as specified, and the sweep found no page where it occurs.