v0.32.0 — Narrowed rune schemas

createContentModelSchema merges all ~37 universal attributes unconditionally:

refrakt reference card prints:

Of the seven gated universal axes, four report when they are dropped and three say nothing:

body carries two meanings that were merged by accident of timing:

prominence works by re-pointing --rf-title-size, which [data-section="title"] reads:

packages/transform/refrakt.config.schema.json is hand-maintained and had drifted from the RefraktConfig / SiteConfig interfaces in @refrakt-md/types. Nothing guarded it, so seven discrepancies had accumulated — fields that exist in the types but are absent from the schema (and therefore missing from editor autocomplete and from the configuration docs), one field the schema advertised that the types no longer have, and two nested objects the schema actively rejected.Separately, refrakt config migrate kept its own hand-copied SITE_FIELDS array, which had drifted from the authoritative one in config-normalize.ts. The two lists describe inverse operations over the same field set — the normalizer mirrors site → top level, the migration moves top level → site — so a divergence strands fields.

The /docs vs /extend split is sound in principle — extend/index.md states it outright ("If you're here to author content... head to the Docs handbook"). But seven pages sat on the wrong side of the line, and the entity-registry concept had no author-facing home at all.