npm - dreative - Versions diffs - 0.5.1 → 0.5.3 - Mend

dreative 0.5.1 → 0.5.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (48) hide show

package/README.md +49 -27
package/dist/cli/audit.js +206 -0
package/dist/cli/audit.test.js +79 -0
package/dist/cli/docsCheck.js +163 -0
package/dist/cli/docsCheck.test.js +8 -0
package/dist/cli/index.js +45 -9
package/dist/server/preview.js +73 -73
package/dist/server/store.js +11 -0
package/dist/shared/artifacts.js +220 -0
package/dist/shared/design.js +45 -24
package/dist/shared/ruleSystem.js +220 -0
package/dist/shared/ruleSystem.test.js +262 -0
package/dist/shared/skillSystem.js +173 -0
package/dist/shared/skillSystem.test.js +110 -0
package/dist/ui/assets/{index--vztc_MR.js → index-CKwmbx2j.js} +13 -13
package/dist/ui/index.html +12 -12
package/package.json +5 -3
package/skill/dreative/DESIGN.md +144 -108
package/skill/dreative/PLAN.md +285 -116
package/skill/dreative/SKILL.md +237 -144
package/skill/dreative/frameworks/nextjs.md +13 -0
package/skill/dreative/frameworks/react-vite.md +12 -0
package/skill/dreative/frameworks/styling.md +14 -0
package/skill/dreative/frameworks/sveltekit.md +10 -0
package/skill/dreative/frameworks/vue-nuxt.md +12 -0
package/skill/dreative/recipes/3d-recipes.md +44 -0
package/skill/dreative/recipes/cinematic-recipes.md +19 -0
package/skill/dreative/recipes/immersive-recipes.md +18 -0
package/skill/dreative/recipes/media-recipes.md +60 -0
package/skill/dreative/recipes/motion-recipes.md +68 -0
package/skill/dreative/references/ARTIFACTS.md +196 -0
package/skill/dreative/references/REFLEX_FONTS.json +44 -0
package/skill/dreative/references/RULES.json +186 -0
package/skill/dreative/references/SKILL_CONTRACT.md +30 -0
package/skill/dreative/references/TIERS.md +44 -0
package/skill/dreative/schemas/plan.schema.json +309 -0
package/skill/dreative/schemas/verify.schema.json +75 -0
package/skill/dreative/skills/3d.md +94 -267
package/skill/dreative/skills/cinematic.md +56 -232
package/skill/dreative/skills/experimental.md +108 -95
package/skill/dreative/skills/immersive.md +61 -223
package/skill/dreative/skills/interaction.md +9 -1
package/skill/dreative/skills/media.md +149 -564
package/skill/dreative/skills/mobile.md +129 -117
package/skill/dreative/skills/motion.md +126 -256
package/skill/dreative/skills/refined.md +116 -102
package/skill/dreative/skills/ux.md +155 -144
package/dist/server/ai.js +0 -177

package/dist/ui/index.html CHANGED Viewed

@@ -1,13 +1,13 @@
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Dreative</title>
-    <script type="module" crossorigin src="/assets/index--vztc_MR.js"></script>
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>Dreative</title>
+    <script type="module" crossorigin src="/assets/index-CKwmbx2j.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/index-y0gVjC7u.css">
-  </head>
-  <body>
-    <div id="root"></div>
-  </body>
-</html>
+  </head>
+  <body>
+    <div id="root"></div>
+  </body>
+</html>

package/package.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "name": "dreative",
-  "version": "0.5.1",
-  "description": "Layout-first visual editor skill for coding CLIs: extract your app's UI into editable wireframes, tweak with drag-drop + ref images, then the agent applies the diff back to your code.",
+  "version": "0.5.3",
+  "description": "Frontend design skill for coding CLIs with typed planning, specialist treatments, verification, and an optional visual editor.",
   "type": "module",
   "bin": {
     "dreative": "dist/cli/index.js"
@@ -14,7 +14,9 @@
     "build": "npm run build:server && npm run build:ui",
     "prepublishOnly": "npm run build",
     "build:server": "tsc -p tsconfig.json",
-    "build:ui": "vite build",
+    "build:ui": "vite build",
+    "test": "npm run build:server && node --test dist/shared/*.test.js dist/cli/*.test.js",
+    "docs-check": "npm run build:server && node dist/cli/index.js docs-check",
     "dev": "concurrently \"tsx watch src/cli/index.ts --no-open\" \"vite\"",
     "start": "node dist/cli/index.js"
   },

package/skill/dreative/DESIGN.md CHANGED Viewed

@@ -2,8 +2,8 @@
 You MUST read this file before servicing any `propose-skeletons`, `propose-variants`,
 `design-page`, or `edit-element` request, and run §12 before every respond. It exists
-because LLM-designed UIs converge on one templated look. Every rule corrects a known
-model default; none is a suggestion. Requests may carry a `plan` (Dreative's
+because LLM-designed UIs converge on one templated look. Every rule corrects a known
+model default, but its category determines how it governs. Requests may carry a `plan` (Dreative's
 pre-computed decision: dials, per-section layout families, budgets, lints) — execute
 the plan, apply this doctrine to everything the plan doesn't specify. When
 `plan.skills` names specialist skills (`motion`, `3d`, `interaction`, `immersive`,
@@ -11,13 +11,16 @@ the plan, apply this doctrine to everything the plan doesn't specify. When
 `skills/<name>.md` files extend this doctrine for that request — read them first;
 where they go deeper than a section here, they win.
-Rules come in two tiers. **Hard gates** — preservation (§11), spatial integrity
-(§15), the layout hard rules (§5), banned tells (§10), runtime verification —
-are checked mechanically and never traded away. Everything else is **craft
-doctrine**: binding defaults you deviate from only with a reason you could
-defend to the user. When attention is scarce, gates outrank craft rules, and
-craft rules outrank stylistic preference — but a page that only clears gates
-and shows no point of view is still a failure of this file.
+Rules use the three categories in `references/RULES.json`. **Hard gates** cover
+objective failures—preservation, functionality, mobile/reduced motion, content
+visibility, spatial integrity, organic-subject honesty, fallbacks, assets, and
+real verification—and cannot be waived. **Evidence-backed defaults** are proven
+remedies for repeated dogfood failures; follow them or declare a planning-time
+alternative with measurable criteria and runtime evidence. **Creative
+provocations** force divergent exploration but do not become shipment checklists.
+When attention is scarce, hard gates outrank defaults, and defaults outrank
+stylistic preference—but a page that only clears gates and shows no point of
+view is still a failure of this file.
 ## 1. Register: the first decision
@@ -76,8 +79,9 @@ Never design by accretion, and never commit to the first concept. Three passes:
    `$RANDOM % 20 + 1`, or read digits off `date +%N`) and record the literal
    command AND its output in plan.md. The roll picks one **provocation** from
    the table below; at least ONE of the three explore concepts must take it
-   literally, and if that concept wins, the provocation ships — visibly, not
-   as a token gesture. Roll a second number (1–6) to pick a **forced-rotation
+   literally. If that concept wins, the provocation becomes a candidate;
+   experimental delivery selects only the strongest two or three peaks instead
+   of forcing every candidate to ship. Roll a second number (1–6) to pick a **forced-rotation
    axis** — 1 palette strategy · 2 type voice · 3 hero concept · 4 nav/page
    architecture · 5 signature driver · 6 set-piece family — and that axis must
    differ from anything in your ledger's last 3 entries AND from the most
@@ -136,6 +140,62 @@ build ("the hero feels generic", "too much motion"), append it to that
 build's entry as a one-line `lesson:` — and the commit pass reads lessons
 alongside choices, so the same critique never has to be given twice.
+**No-media builds: structure IS the media.** When a build ships zero
+imagery (no image-gen tool, product register, or the user chose
+placeholders), the ambition tier does NOT tier down — it transfers whole
+onto layout, type, and motion, and this is where no-media builds die: the
+executor, with no assets to arrange, collapses to the one layout it knows
+(a vertical list of rounded cards in a centered column) and ships slop that
+its own plan didn't describe. Hard rules for any expressive+ no-media build:
+1. **The compositional spine must survive to the screenshot.** Whatever
+   bespoke structure the plan named (a strip rack, a ledger, a switchboard,
+   a timetable) must be RECOGNIZABLE as that thing in the shipped page — its
+   physical vocabulary built for real: the holder edge, the notch, the rail,
+   the perforation, the column rules. If a stranger shown the screenshot and
+   the blueprint's layout-family words couldn't match them, the build
+   restyled a card list and called it the spine — that is a depth-honesty
+   failure (§11), not a detail.
+2. **Bespoke drawn/procedural artifacts carry the missing media role.** With no photography, the page
+   earns visual richness from things MADE for it: a live canvas (meter,
+   field, trace), custom SVG structure (rules, notches, connectors, dials —
+   drawn, not icon-font), procedural texture/grain, a data-driven ornament.
+   A no-media page whose only visuals are borders and border-radius has no
+   media plan at all.
+3. **Type does structural work.** Multi-scale composition (oversized
+   numerals/designators against small mono metadata), real hierarchy per §6
+   — not one font-size row layout repeated N times.
+4. **Motion budget spends on the structure**, not on entrance fades: the
+   spine's own physicality (things racked, tossed, slid, stamped) is the
+   choreography. Motion.md's treatment and verification rules apply.
+5. **Choose a rendering layer only when it earns its cost.** No imagery can
+   justify Canvas/WebGL when a live procedural or data-driven surface is the
+   concept, but award ambition does not require one. Spatial typography,
+   layered DOM/SVG composition, masks, or other subject-grounded systems may be
+   stronger. Vocabulary to draw from when rendering is warranted
+   (subject-grounded, not decorative): oscilloscope/waveform traces driven by
+   real events · topographic contour lines drifting · dot-matrix/LED field
+   that spells live state · plexus line-network connecting related items ·
+   isometric grid that lights under the cursor · scan sweep across data
+   rows · ASCII/character rain in the brand's glyphs · particle flow along
+   the layout's own rails · generative engraving borders · a physical sim
+   (springs, gravity) on the UI's actual objects.
+6. **Layout creativity means spatial composition, not relocated chrome.**
+   Moving the nav to the bottom, a novel tab bar, an unusual dock — that is
+   furniture rearrangement, and if it's the build's ONLY inventive move the
+   build failed. The invention must live in how the CONTENT is composed:
+   asymmetric multi-scale grids, overlapping planes, diagonal/rotated flow,
+   sections that share edges and interlock — while staying rigorously
+   modern and clean (generous space, disciplined alignment, few colors).
+   "Clean" and "insane motion" are the same build: calm composition,
+   spectacular behavior.
+The slop tests above apply to the RENDERED page: "dark theme + rounded
+cards + one accent color" fails the competitor sentence for every no-media
+product tool at once — and shipped exactly that once (user verdict on
+record: "pure ai slop… I would not want something like that again"). Treat
+these rules as a shipped-failure postmortem, not theory.
 **Hero thesis:** open with the most characteristic thing in the subject's world —
 a headline, an image, a live demo, an interactive moment. Whatever form fits.
@@ -160,20 +220,27 @@ a headline, an image, a live demo, an interactive moment. Whatever form fits.
 ## 3. Typography
-**Font selection procedure (brand register, never skip):**
-1. Write three physical-object brand-voice words ("warm, mechanical, opinionated" —
-   never "modern" or "elegant").
-2. List the three fonts you'd reach for by reflex. Reject any on the ban list below.
-3. Pick for the brand as a physical object (museum caption, 1970s terminal manual,
-   concert poster, mid-century receipt). Reject the first thing that "looks designy".
-4. If the final pick matches the original reflex, start over.
-**Reflex-reject fonts (training-data defaults, banned as defaults):** Fraunces,
-Newsreader, Lora, Crimson (all), Playfair Display, Cormorant (all), Syne, IBM Plex
-(all), Space Mono, Space Grotesk, Inter, DM Sans/Serif, Outfit, Plus Jakarta Sans,
-Instrument Sans/Serif. Inter/system stacks ARE legitimate in the product register
-and for trust briefs. When an existing app already uses one, identity-preservation
-wins — keep it.
+**Font selection procedure (brand register, never skip):**
+1. Write three physical-object brand-voice words ("warm, mechanical, opinionated" —
+   never "modern" or "elegant").
+2. Read the last three display fonts from the design ledger and generate at least
+   three candidates for this brand, including continuity candidates when an
+   existing identity or design system matters.
+3. Mark candidates found in `references/REFLEX_FONTS.json`. A reflex font is not
+   bad or prohibited; it is a frequently unexamined choice that needs a specific
+   reason if it wins.
+4. Pick for the brand as a physical object (museum caption, 1970s terminal manual,
+   concert poster, mid-century receipt), supplied reference, product metrics,
+   language coverage, variable-font capability, or performance constraint.
+5. Record candidates and the winner in `plan.fontDecision`. If the winner is a
+   reflex font, record the concrete justification and at least one registry
+   category in `reasonKinds`. If it repeats one of the last three display fonts,
+   add a stronger repeat justification.
+Valid reflex-font reason: "Inter is already embedded throughout this authenticated
+product, preserves its density metrics and translated layout, and changing it
+would damage brand continuity." Invalid reason: "Inter looks clean and modern."
+The goal is to stop reflex selection, not to declare common fonts inherently bad.
 **Serif discipline:** "creative/premium brief = serif" is the most-tested AI tell.
 Default is sans display. Serif only when the brief is genuinely editorial/luxury/
@@ -292,10 +359,17 @@ sites win on composition, not decoration; this is where that happens.
 - Product register: responsive behavior is structural (collapse sidebar, responsive
   table), not fluid type.
-## 6. Motion
-Every animation answers "what does this communicate?" — hierarchy, storytelling,
-feedback, or state change. "It looked cool" = delete it.
+## 6. Motion
+Every animation answers "what does this communicate?" — hierarchy, storytelling,
+feedback, or state change. "It looked cool" = delete it.
+Motion has three roles. **Decorative motion** reveals, responds, or adds ambient
+life. **Structural motion** controls hierarchy, pacing, pinning, and composition
+handoffs. **Transformational motion** changes imagery/type/objects into a new
+form or the next scene. Expressive/award pages evaluate key moments for the last
+two roles; opacity, translate, scale, and slight parallax are not automatically
+enough merely because they animate.
 **The 100/300/500 rule:** 100-150ms instant feedback (press, toggle) · 200-300ms
 state changes (menu, tooltip, hover) · 300-500ms layout changes (accordion, modal)
@@ -312,9 +386,12 @@ micro-interactions; the uniform fade-and-rise on every scrolled section is the
 saturated AI tell. Some brands skip entrance motion entirely — restraint as voice.
 Product = 150-250ms, state-conveying only, zero page-load choreography.
-**Mechanics:** animate transform/opacity by default; blur/backdrop-filter/clip-path/
-masks/shadow allowed when they materially improve the effect, bounded to small areas,
-verified smooth. Never casually animate width/height/top/left/margins (use FLIP or
+**Mechanics:** use transform/opacity for ordinary local state when they fit, but
+do not make them the unexamined expressive default. Select CSS, GSAP timelines,
+ScrollTrigger, SVG, masks, `clip-path`, DOM fragments, Canvas, WebGL/shaders,
+sequences, video, Lottie, or 3D by visual result, cost, responsiveness, and
+available assets. Use the simplest mechanism capable of making the intended
+transformation convincing. Never casually animate width/height/top/left/margins (use FLIP or
 grid-template-rows). Sibling stagger `calc(var(--i) * 50ms)` capped at ~500ms total.
 IntersectionObserver (unobserve after firing), CSS scroll-driven animations, or
 Motion/GSAP scroll tools — `window.addEventListener("scroll")` is a hard ban. Reveals
@@ -343,65 +420,22 @@ library (Phosphor/Radix/Tabler/HugeIcons; Lucide only on request), one strokeWid
 globally. Logo walls: real SVG marks (`https://cdn.simpleicons.org/<slug>`) or
 generated monograms — logos only, no category captions, below the hero.
-### Generated media (probe your environment, then use it)
-Before designing, check what media generation your environment actually offers —
-image-gen tools, video-gen tools, or a CLI that can produce them — and treat any
-capability found as a first-class design material, not a nice-to-have:
-- **Images**: generate hero photography, product/context shots, and textures at
-  the section's exact aspect ratio, prompted for the brand's physical subject
-  and the page's light temperature so they grade into the palette. Generate the
-  grain tile and any masks/mattes too instead of hand-rolling SVG.
-- **Video**: a generated 5–10s seamless loop is one of the biggest single UI
-  upgrades available — use it as: a hero background (muted, `autoplay loop
-  playsinline`, poster frame, `prefers-reduced-motion` swaps to the poster);
-  the budget "living surface" (a pre-rendered fluid/particle/atmosphere loop
-  instead of a GPGPU sim — cinematic.md's budget recipe); hover-preview loops
-  on work cards; or an image-sequence for scroll-scrubbed narratives (export
-  frames, scrub per motion.md).
-- **Integrate with motion, don't just embed** — a raw `<video>`/`<img>` dropped
-  in a section is not the treatment. Generated media enters the page THROUGH the
-  motion system; pick 1–2 treatments per page from this vocabulary (or invent in
-  its spirit), matched to the register:
-  - **Pixel/dither reveal**: video or image materializes from coarse blocks —
-    a shader that lerps sample resolution from ~24px mosaic to full res (or a
-    stepped `image-rendering: pixelated` downscale swap for the budget path),
-    driven by scroll progress or hover. Reads as digital-craft; dark-tech and
-    editorial registers.
-  - **Floating media**: images hover in depth with slow damped drift (±6-10px,
-    4-8s loops, each at a different phase), subtle parallax by depth layer, and
-    a soft contact shadow — the immersive "paper sheets in space" look without
-    WebGL. Cap at 3-5 floaters per view.
-  - **Mask-shaped video**: the loop plays inside display type (`background-clip:
-    text` / SVG mask on a 10vw+ headline), an arch/circle clip-path, or the
-    brand mark — the video becomes typography/identity rather than a rectangle.
-  - **Scroll-scrubbed sequence**: generated frames scrubbed by scroll for
-    assemble/morph/rotate narratives (motion.md's canvas product story).
-  - **Velocity-touched media**: scroll/drag velocity stretches, RGB-splits, or
-    ripples the media plane for a beat, settling with damped decay
-    (cinematic.md §2) — needs the WebGL media-plane sync.
-  - **Hover-woken loops**: stills that crossfade into their video loop on
-    hover/focus (240ms), pause + rewind-to-poster on leave; works as generated
-    "living thumbnails" on work/product cards.
-  - **Curtain/split reveal**: media enters behind a 2-4 panel wipe or an
-    expanding inset clip (`clip-path: inset(40% 30%) → inset(0)`), timed with
-    the section's line-mask type reveal so image and headline arrive as one
-    choreographed beat.
-  Whatever the treatment, honor the floors: reduced-motion gets the poster
-  frame, hover treatments have focus equivalents, and the effect is justified
-  in one sentence like any other motion (§6).
-- Discipline: same rationing as everything else — one video loop per view,
-  compress hard (H.264/AV1, ≤ 2–4MB per loop, no audio track), lazy-load below
-  the fold, and never let generated media replace REAL product screenshots or
-  the client's actual photography when those exist.
-- If no generation capability exists, say so and fall back down the §7 priority
-  list — never fake a video with a div animation.
-- `skills/media.md` is this section's deep dive: the production pipeline
-  (prompting for the page's light, compression targets, frame sequences), the
-  full DOM-tier and WebGL media-plane treatment vocabulary, and the
-  entrance/idle/response reasoning frame. Read it whenever generated media or
-  motion-integrated imagery ships.
+### Generated media (probe your environment, then use it)
+Before designing, check what media generation your environment actually offers —
+image-gen tools, video-gen tools, or a CLI that can produce them — and treat any
+capability found as a first-class design material, not a nice-to-have. Generate
+for the section's exact ratio, physical subject, and light temperature. Preserve
+real product screenshots and supplied photography when they are authoritative.
+Do not choose a media treatment from a catalog here. First record three original
+brand-native concepts in `conceptExploration`; then read `skills/media.md` for
+principles. Open `recipes/media-recipes.md` only afterward for feasibility,
+implementation, performance, or fallback guidance, and log that access in
+`recipeAccess`. A raw `<video>` or `<img>` is not a treatment: the chosen media
+system must develop the concept and retain poster/static, focus/touch, reduced-
+motion, low-power, and loading fallbacks. If generation is unavailable, use the
+§7 source priority instead of simulating media with decorative divs.
 ### Surface & light — material identity for every layer
@@ -411,8 +445,8 @@ ambition every major surface (page background, hero, cards/panels, media
 frames) carries at least one deliberate material cue, and the page declares
 ONE light direction that everything obeys:
-- **Grain/noise** — a 1-3% opacity noise overlay (tileable PNG or SVG
-  `feTurbulence`, one shared asset) kills gradient banding and digital
+- **Grain/noise** — a 1-3% opacity tileable PNG/WebP noise overlay (one shared
+  asset; never `feTurbulence`) kills gradient banding and digital
   flatness; vary its intensity by section as part of the pacing curve.
 - **Light consistency** — pick the light's direction once; every shadow,
   edge-highlight, gradient hotspot, and 3D/scene light agrees with it. Tint
@@ -652,8 +686,9 @@ the output is not done.
 3. Zero em/en-dashes visible. Zero banned tells from §10.
 4. One accent + one tinted-neutral family + one theme + one radius system + one
    icon family, locked page-wide; matches sibling pages of this project.
-5. Fonts: not on the reflex-reject list (or justified by existing brand); scale
-   ratio committed; body ≥16px at 45-75ch; caps tracked; data tabular.
+5. Fonts: three candidates considered; registry matches marked; any reflex winner
+   has a specific registered reason; scale ratio committed; body ≥16px at
+   45-75ch; caps tracked; data tabular.
 6. Every CTA/form/placeholder passes WCAG AA; no CTA wraps; no duplicate CTA intent.
 7. Hero: ≤2-line headline, ≤20-word subtext, ≤4 elements, real visual, CTA above
    fold; centered only if variance ≤ 4 or manifesto brief.
@@ -707,11 +742,11 @@ On touch, whatever hover revealed must be visible by default or reachable by
 tap — never lost. Custom cursors simply don't exist on touch; don't ship their
 DOM/listeners there.
-**Pinned/scrubbed sections**: pinning is fragile on mobile (URL-bar resize
+**Pinned/scrubbed sections**: pinning is fragile on mobile (URL-bar resize
 fires viewport changes mid-pin; iOS momentum scroll skips scrub frames).
-Strategies in preference order: (1) keep the pin but shorten it (≤ 1.5
-viewports) and drive it with `position: sticky`, never JS pinning; (2) unpin —
-the same content as stacked sections with simple in-view reveals;
+Strategies in preference order: (1) keep the pin but shorten it and drive it
+with `position: sticky` when reliable; (2) redesign the same idea as a shorter
+mask, layered-parallax, or state handoff sequence rather than merely disabling it;
 (3) `ScrollTrigger.matchMedia()` / a `matchMedia` branch that swaps the whole
 choreography. Never let a desktop pin length ride on a phone.
@@ -738,15 +773,16 @@ clamps DOWN gracefully (hero ≥ 2rem, body stays ≥ 16px — iOS zooms inputs
 under 16px); sticky navs shrink rather than stack; test the three widths 320 /
 768 / 1280 mentally before responding.
-**Motion budget on mobile**: entrance choreography total ≤ 600ms (vs 900ms
-desktop), at most 1 scroll-driven sequence per page, marquees pause when
-off-screen. Battery is a design constraint: continuous rAF loops must idle
-when nothing animates.
-## 14. Typography sourcing (kill the Inter-everywhere default)
+**Motion budget on mobile**: shorten travel and timelines according to content,
+viewport, and measured device cost. Preserve one defining idea when feasible;
+marquees pause off-screen and continuous rAF loops idle when nothing animates.
+Battery is a design constraint, not a reason to erase the concept.
-The reflex-reject list (§3) says what NOT to reach for; this is where to reach
-instead. All fonts below are free (Google Fonts or Fontshare/ITF). The
+## 14. Typography sourcing (escape the first reflex)
+Use this section only after the brand-register exercise in §3 has produced
+several candidates; it is a sourcing aid, not a rejection or approved-font list.
+All fonts below are free (Google Fonts or Fontshare/ITF). The
 commercial fonts real award sites use — verified: unseen.co sets **Saol
 Display Light/Italic + Neue Montreal**; unseen's Blossom lab sets **SangBleu
 Serif + PP Neue Montreal**; capsul-in-pro sets **Messina Sans** — are the
@@ -827,7 +863,7 @@ from the SCREENSHOT, not from the plan's prose: naming the object "eclipse",
 "thermal horizon", or "roast core" in the plan does not make a translucent
 sphere read as one — if the verify screenshot shows a ball floating over a
 photo, it fails regardless of what the plan swore it wasn't. At hero scale
-the answer must be a nameable thing (see 3d.md §3: abstract coded forms are
+the answer must be a nameable thing (see 3d.md §2: generic abstract forms are
 supporting-only and can never be the promoted signature object).
 **Interactive elements never overlap other interactive elements.** Not at any