v0.14.4 — Framework adapter parity with the SvelteKit reference

1. Site-level token-overrides CSS — composeSiteTokensCss generates a stylesheet from theme.presets, theme.tokens, theme.modes, and site.tints (SPEC-048 + SPEC-056). Outside SvelteKit those config fields are silently ignored.
2. SEO meta enrichment from site config — siteName, baseUrl, defaultImage, logo bake into og:site_name, absolute og:url, image fallback, and WebSite + Organization JSON-LD. Outside SvelteKit those fields are silently dropped.
3. CSS tree-shaking by used-rune analysis — the SvelteKit plugin emits only the per-rune CSS files for runes actually present in the corpus. Outside SvelteKit every site ships the full theme barrel.
4. Pipeline-stats build summary — the SvelteKit plugin prints a Phase 1/2/3/4 + warnings table at the end of every build. Other adapters either go silent or inherit the host framework's default output.
5. security (SecurityPolicy) + variables (Markdoc $name variables) plugin options — both are SvelteKit-only surfaces today even though loadContent accepts them.
6. Content HMR — only SvelteKit watches the content directory + sandbox examples and invalidates the loader cache on .md edits.

A patch milestone scoped to application work — no new design, no new contracts. Every capability ships in working form inside @refrakt-md/sveltekit; the job is extraction, sharing, and per-adapter wiring along the path each adapter natively uses.