@quillmark/svelte 0.5.0 → 0.5.1

package/README.md

@@ -152,7 +152,7 @@ The package ships English and a seam to replace it. `strings` is keyed and **par
 		addCard: '+ Ajouter une carte'
 	}}
 	formatDiagnostic={(d) =>
-		d.code === 'validation::must_fill' ? `${d.path} est obligatoire` : undefined}
+		d.code === 'validation::type_mismatch' ? `${d.path} : type incorrect` : undefined}
 />
 ```
 
@@ -184,7 +184,7 @@ function recompileNow() {
 }
 ```
 
-`session.warnings` is a **getter on a handle Svelte does not track**: pull it per apply, or the editor shows the previous compile's diagnostics.
+`session.warnings` is a **getter on a handle Svelte does not track**: pull it per apply, or the editor shows the previous compile's errors.
 
 This shell layer is deliberately yours: the debounce value, what applies at once, and which surfaces refresh are host policy, so the package ships no scheduler over them. Three obligations ride with that: an edit of your own (an import, an undo, a direct `doc` write) recompiles by the same calls, since nothing polls the document; a compile owes the diagnostics re-read above, since nothing polls the session; and teardown clears the timer **before** freeing the handles, so a pending recompile never touches a freed session.
 

package/THEMING.md

@@ -4,11 +4,11 @@
 
 There are three depths to that. An app mounting into an unstyled page stops at the first; an app with a plate of its own starts at the second:
 
-|                   | You write             | You get                                                 |
-| ----------------- | --------------------- | ------------------------------------------------------- |
-| **Drop it in**    | nothing               | a mounted surface that looks right in a bare `<div>`    |
-| **Make it yours** | ten custom properties | the whole surface rescaled and recolored to your brand  |
-| **Match ours**    | one CSS import        | the page around the surface, drawn the way we draw ours |
+|                   | You write              | You get                                                 |
+| ----------------- | ---------------------- | ------------------------------------------------------- |
+| **Drop it in**    | nothing                | a mounted surface that looks right in a bare `<div>`    |
+| **Make it yours** | nine custom properties | the whole surface rescaled and recolored to your brand  |
+| **Match ours**    | one CSS import         | the page around the surface, drawn the way we draw ours |
 
 ## Drop it in
 
@@ -28,7 +28,7 @@ Nothing to import and nothing to set. The package pulls its own stylesheet, and
 
 ## Make it yours
 
-The whole contract is **ten CSS custom properties**. They are dials, not a palette: each derives a closed private scale that every component reads, so one override rescales or recolors the whole surface. Set them on any ancestor of a mounted surface (the app, or one pane):
+The whole contract is **nine CSS custom properties**. They are dials, not a palette: each derives a closed private scale that every component reads, so one override rescales or recolors the whole surface. Set them on any ancestor of a mounted surface (the app, or one pane):
 
 ```css
 .my-editor {
@@ -55,7 +55,6 @@ The poles take a colour, not `transparent` or `inherit`: the raised surfaces, th
 | `--qm-fg`        | `#1c1c1c` / `#d7dadc`                  | Base ink. Body text, labels, and borders step off it.                                                                                                          |
 | `--qm-accent`    | `#71717a` / `#a1a1aa`                  | Focus rings, active marks, the preview's active field box. The surface spends no hue of its own, so this is the one it wears.                                  |
 | `--qm-danger`    | `#9e1518` / `#f9786c`                  | Error diagnostics, the required marker, the delete glyph.                                                                                                      |
-| `--qm-warning`   | `#926510` / `#fdc776`                  | Warning diagnostics.                                                                                                                                           |
 | `--qm-font`      | `ui-sans-serif, system-ui, sans-serif` | The editor surface's font family. Controls and buttons take it too, in place of the UA face.                                                                   |
 | `--qm-font-mono` | `ui-monospace, monospace`              | The monospace face: the JSON array control, the tips card.                                                                                                     |
 | `--qm-font-size` | `0.875rem`                             | Chrome text: every control's size, the anchor the ramp derives up (title) and down (label/meta) from, and the anchor a document body sits one small step over. |
@@ -106,9 +105,9 @@ Setting the poles yourself wins over the default in both schemes, so a fixed pal
 }
 ```
 
-That cuts both ways for the status hues: `--qm-danger` and `--qm-warning` each default to a pair calibrated against the card at both poles, and one pinned value replaces both arms, so a red measured against white carries into the dark scheme unmeasured. Pin them under your own scheme rule (`.dark { --qm-danger: … }`) where the colour your app means by error is itself scheme-aware.
+That cuts both ways for the status hue: `--qm-danger` defaults to a pair calibrated against the card at both poles, and one pinned value replaces both arms, so a red measured against white carries into the dark scheme unmeasured. Pin it under your own scheme rule (`.dark { --qm-danger: … }`) where the colour your app means by error is itself scheme-aware.
 
-A palette **pinned against** your own scheme still wants a second line, for a smaller reason than it used to be: the planes read your card's lightness, so the surface itself lands right either way, but the poles' own defaults, the status hues and native chrome all still read `color-scheme`. Pin it with them (`.my-editor { color-scheme: dark }`). Skip that line and what the browser paints — the selection highlight, the scrollbar, the spinner — stays on whichever scheme the host inherits, and a status hue you left to us is measured against the wrong card.
+A palette **pinned against** your own scheme still wants a second line, for a smaller reason than it used to be: the planes read your card's lightness, so the surface itself lands right either way, but the poles' own defaults, the status hue and native chrome all still read `color-scheme`. Pin it with them (`.my-editor { color-scheme: dark }`). Skip that line and what the browser paints — the selection highlight, the scrollbar, the spinner — stays on whichever scheme the host inherits, and a status hue you left to us is measured against the wrong card.
 
 Pinning **one mount** rather than a page is the `style` prop, which lands on the same root: `<Preview style="color-scheme: dark" />`. There is no `scheme` prop, and deliberately — an inline declaration of ours would be the one thing your own CSS could not beat.
 
@@ -131,7 +130,7 @@ import '@quillmark/svelte/preset';
 
 This is the stylesheet our own apps import: the playground and studio draw with these rules and nothing else, so what you get is what we ship, not a reduction of it.
 
-It carries a `--qmh-*` scale for the page, derived from the same ten dials and calibrated against the surfaces' own steps, so a plate of yours and a card of ours agree about which way "raised" goes. Turning a dial moves both.
+It carries a `--qmh-*` scale for the page, derived from the same nine dials and calibrated against the surfaces' own steps, so a plate of yours and a card of ours agree about which way "raised" goes. Turning a dial moves both.
 
 | Class         | What it is                                                                                                                           |
 | ------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
@@ -139,7 +138,7 @@ It carries a `--qmh-*` scale for the page, derived from the same ten dials and c
 | `.qm-panel`   | The plate your controls and readouts sit on: one rung off the page, a hairline, a corner.                                            |
 | `.qm-label`   | A run of chrome type: a section label, the name over a value.                                                                        |
 | `.qm-readout` | A value read back out of the session, monospace and tabular. `<pre class="qm-readout">` is the block form.                           |
-| `.qm-status`  | A phase line. `.qm-status-error` and `.qm-status-warn` are the two it fails to.                                                      |
+| `.qm-status`  | A phase line. `.qm-status-error` is the one it fails to.                                                                             |
 | `.qm-control` | A boxed button or select, which is what a host's controls are and the package's are not.                                             |
 | `.qm-measure` | A reading column at the width a passage wants.                                                                                       |
 

package/dist/core/theme.css

@@ -89,18 +89,15 @@
 		/* Neutral: the surface spends no hue on a state it can draw in grey. The pair
 		   clears WCAG 2.4.11's 3:1 against the card at both poles, at 4.8:1 and 5.8:1. */
 		--_qm-accent: var(--qm-accent, light-dark(#71717a, #a1a1aa));
-		/* The two hues the surface does spend, and it spends them on a state. Each pole
-		   is its own figure rather than one ink shown twice: a hue calibrated against
-		   white reads as a stain on a dark card. All four clear WCAG 1.4.3's 4.5:1
-		   against the card, which is the bar the label rung asks for and the one the
-		   glyphs drawn in these hues clear on the way past 1.4.11's 3:1 — 8.2:1 and
-		   5.1:1 light, 5.6:1 and 9.7:1 dark. Each is also dark enough at its own pole
-		   to carry a label at 4.5:1, so a filled chip needs no third figure. The
+		/* The one hue the surface spends, and it spends it on a state. Each pole is
+		   its own figure rather than one ink shown twice: a hue calibrated against
+		   white reads as a stain on a dark card. Both clear WCAG 1.4.3's 4.5:1 against
+		   the card, which is the bar the label rung asks for and the one the glyphs
+		   drawn in this hue clear on the way past 1.4.11's 3:1. Dark enough at its own
+		   pole to carry a label at 4.5:1, so a filled chip needs no third figure. The
 		   figures are the host scale's (`preset/scale.css`), so a page's status line
-		   and a card's diagnostic carry one colour meaning error and one meaning
-		   warning. */
+		   and a card's diagnostic carry one colour meaning error. */
 		--_qm-danger: var(--qm-danger, light-dark(#9e1518, #f9786c));
-		--_qm-warning: var(--qm-warning, light-dark(#926510, #fdc776));
 		--_qm-font: var(--qm-font, ui-sans-serif, system-ui, sans-serif);
 		--_qm-font-mono: var(--qm-font-mono, ui-monospace, monospace);
 

package/dist/preset/recipes.css

@@ -247,10 +247,6 @@ pre.qm-readout {
 	overflow-wrap: anywhere;
 }
 
-.qm-status-warn {
-	color: var(--qmh-warn);
-}
-
 /* ── Surfaces ──────────────────────────────────────────────────────────────── */
 
 /* The instrument plate: what a host puts its controls and readouts on. The same plane a

package/dist/preset/scale.css

@@ -2,7 +2,7 @@
    page around the surfaces out. `core/theme.css` is the same shape one level down
    (dials in, `--_qm-*` out), and the two are calibrated against each other: the
    figures here are the figures there (the ground step's ramp, 8% hover, 17%
-   border, 45% ink, the ring's width, the status hues at both poles) and the
+   border, 45% ink, the ring's width, the status hue at both poles) and the
    dial means the same plane in both, so a host plate and a card on it land on the same
    tone at both poles and a host page meets an editor's own column exactly. The well
    under the ground has no counterpart here: a host's own controls are boxed and carry a
@@ -45,13 +45,12 @@
 	   the underline under a link. */
 	--qmh-border-strong: color-mix(in oklab, var(--qmh-surface), var(--qmh-ink) 40%);
 
-	/* The two hues a host spends, and it spends them on a message. The figures are the
-	   surfaces' own, so a page carries one colour meaning error and one meaning warning
-	   rather than a second pair beside the surfaces'. Each pole is its own figure: a hue
-	   calibrated against white reads as a stain on a dark page. The dial sits in front
-	   of the pair, as every pole's does, so a host that turns one owns both schemes. */
+	/* The hue a host spends on a failure. The figures are the surfaces' own, so a
+	   page's status line and a card's diagnostic carry one colour meaning error.
+	   Each pole is its own figure: a hue calibrated against white reads as a stain
+	   on a dark page. The dial sits in front of the pair, as every pole's does, so
+	   a host that turns one owns both schemes. */
 	--qmh-alert: var(--qm-danger, light-dark(#9e1518, #f9786c));
-	--qmh-warn: var(--qm-warning, light-dark(#926510, #fdc776));
 
 	/* ── Rhythm ──────────────────────────────────────────────────────────────── */
 	/* One base and its multiples, the same four steps the surfaces derive. A host

package/dist/visual/DiagnosticList.svelte

@@ -1,9 +1,9 @@
 <!--
- Inline diagnostic display (VISUAL_EDITOR §Diagnostics), severity-styled via
- CSS vars, non-gating: purely additive, never disables the field it sits
- under. Shared by `Field.svelte` (a scalar/prose field) and `Card.svelte` (the
- body leaf, which has no `Field.svelte` wrapper), so a card's body diagnostics
- render the same way a field's do.
+ Inline diagnostic display (VISUAL_EDITOR §Diagnostics). Errors only, non-gating:
+ purely additive, never disables the field it sits under. Shared by `Field.svelte`
+ (a scalar/prose field) and `Card.svelte` (the body leaf, which has no
+ `Field.svelte` wrapper), so a card's body diagnostics render the same way a
+ field's do.
 -->
 <script lang="ts">
 	import type { Diagnostic } from '@quillmark/wasm';
@@ -27,9 +27,7 @@
 	<!-- role=status: commit errors appear mid-typing; announce without stealing focus. -->
 	<div class="qm-diag-list" role="status">
 		{#each diagnostics as d, i (i)}
-			<span class="qm-diag-line" data-severity={d.severity}
-				>{diagnosticText(d, t.formatDiagnostic)}</span
-			>
+			<span class="qm-diag-line">{diagnosticText(d, t.formatDiagnostic)}</span>
 		{/each}
 	</div>
 {/if}
@@ -42,9 +40,6 @@
 	}
 	.qm-diag-line {
 		font-size: var(--_qm-text-label);
-		color: var(--_qm-warning);
-	}
-	.qm-diag-line[data-severity='error'] {
 		color: var(--_qm-danger);
 	}
 </style>

package/dist/visual/Field.svelte

@@ -11,7 +11,7 @@
  `diagnostics` is the routed `Diagnostic[]` for this field (VisualEditor's
  `diagByKey`, merging `quill.validate`, local commit errors, and the external
  `diagnostics` prop (VISUAL_EDITOR §Diagnostics)) rendered via the shared
- `DiagnosticList`, severity-styled, non-gating.
+ `DiagnosticList`, non-gating.
 -->
 <script lang="ts">
 	import type { Document, Quill, Addr, Diagnostic, ResolvedField } from '@quillmark/wasm';

package/dist/visual/VisualEditorInner.svelte

@@ -58,7 +58,6 @@
 	} from './structure.js';
 	import {
 		fieldKeyToString,
-		inlineShown,
 		resolveCardKey,
 		routeAndResolve,
 		mergeDiagnostics,
@@ -487,11 +486,10 @@
 
 	// All three producers. The two positional ones resolve their `.path` to the live
 	// stable-id keying; commit errors are id-keyed already. Nothing is dropped for
-	// being unwelcome — diagnostics never gate — but the obligation warning is
-	// withheld from the boundary's lane, the label's `*` being where the surface
-	// states that (`inlineShown`).
+	// being unwelcome — diagnostics never gate — but warnings do not draw: only
+	// errors reach a control (`routeAndResolve`).
 	const diagByKey = $derived.by(() => {
-		const fromValidate = routeAndResolve(validation.filter(inlineShown), cardIds);
+		const fromValidate = routeAndResolve(validation, cardIds);
 		const fromExternal = routeAndResolve(diagnostics, cardIds);
 		return mergeDiagnostics(fromValidate, fromExternal, [...commitErrors.values()]);
 	});

package/dist/visual/diagnostics.d.ts

@@ -27,32 +27,21 @@ export interface RoutedDiagnostic {
     key: FieldKey;
     diagnostic: Diagnostic;
 }
-/**
- * Whether a validation diagnostic is the surface's to show under a control
- * (VISUAL_EDITOR §Diagnostics). Obligation is not: the label's `*` already states
- * it, from the same schema, for the same cells, and it states it whether or not the
- * cell has been answered — so the warning is a second copy of a mark on screen, once
- * per obliged field, on every document nobody has finished. That is every obliged
- * field of a fresh seed, which is what a consumer's first mount is.
- *
- * Withheld from the boundary's own validation lane only. A consumer's `diagnostics`
- * prop passes whole: what a host hands the surface, the host asked to see. And
- * nothing is suppressed at the source — `quill.validate(doc)` is the completeness
- * read, unchanged and still the host's to make.
- */
-export declare function inlineShown(d: Diagnostic): boolean;
 /**
  * Route a path-keyed producer's raw `Diagnostic[]` (validate / external) to the
  * editor's stable-id keying: the one door producers #1/#3 take, `addrForFieldPath`
- * and `resolveCardKey` in a single pass. An entry drops rather than mis-routes when
- * it carries no `path`, when the path names no single commit address (a nested /
- * array-element one), or when its absolute card index is out of the live `cardIds`.
+ * and `resolveCardKey` in a single pass. Warnings do not draw (VISUAL_EDITOR
+ * §Diagnostics): obligation, completeness, a render note — none of them is a value
+ * the field cannot hold. An entry also drops rather than mis-routes when it carries
+ * no `path`, when the path names no single commit address (a nested / array-element
+ * one), or when its absolute card index is out of the live `cardIds`. Completeness
+ * stays a read the host makes on `quill.validate(doc)`.
  */
 export declare function routeAndResolve(diagnostics: Diagnostic[] | undefined, cardIds: readonly string[]): RoutedDiagnostic[];
 /**
  * Merge N routed groups into `Map<fieldKeyToString(key), Diagnostic[]>`.
  * Dedupes an identical `(severity, message)` pair landing on the same key from
- * more than one group (e.g. the same warning present in both `validate()` and
- * an external feed); within a key, errors sort before warnings.
+ * more than one group (e.g. the same error present in both `validate()` and
+ * an external feed). Producer order within a key.
  */
 export declare function mergeDiagnostics(...groups: RoutedDiagnostic[][]): Map<string, Diagnostic[]>;

package/dist/visual/diagnostics.js

@@ -18,33 +18,20 @@ export function resolveCardKey(key, cardIds) {
     const id = key.card >= 0 && key.card < cardIds.length ? cardIds[key.card] : undefined;
     return id != null ? { card: id, field: key.field } : undefined;
 }
-/**
- * Whether a validation diagnostic is the surface's to show under a control
- * (VISUAL_EDITOR §Diagnostics). Obligation is not: the label's `*` already states
- * it, from the same schema, for the same cells, and it states it whether or not the
- * cell has been answered — so the warning is a second copy of a mark on screen, once
- * per obliged field, on every document nobody has finished. That is every obliged
- * field of a fresh seed, which is what a consumer's first mount is.
- *
- * Withheld from the boundary's own validation lane only. A consumer's `diagnostics`
- * prop passes whole: what a host hands the surface, the host asked to see. And
- * nothing is suppressed at the source — `quill.validate(doc)` is the completeness
- * read, unchanged and still the host's to make.
- */
-export function inlineShown(d) {
-    return d.code !== 'validation::must_fill';
-}
 /**
  * Route a path-keyed producer's raw `Diagnostic[]` (validate / external) to the
  * editor's stable-id keying: the one door producers #1/#3 take, `addrForFieldPath`
- * and `resolveCardKey` in a single pass. An entry drops rather than mis-routes when
- * it carries no `path`, when the path names no single commit address (a nested /
- * array-element one), or when its absolute card index is out of the live `cardIds`.
+ * and `resolveCardKey` in a single pass. Warnings do not draw (VISUAL_EDITOR
+ * §Diagnostics): obligation, completeness, a render note — none of them is a value
+ * the field cannot hold. An entry also drops rather than mis-routes when it carries
+ * no `path`, when the path names no single commit address (a nested / array-element
+ * one), or when its absolute card index is out of the live `cardIds`. Completeness
+ * stays a read the host makes on `quill.validate(doc)`.
  */
 export function routeAndResolve(diagnostics, cardIds) {
     const out = [];
     for (const d of diagnostics ?? []) {
-        if (!d.path)
+        if (d.severity !== 'error' || !d.path)
             continue;
         const key = addrForFieldPath(d.path);
         const resolved = key && resolveCardKey(key, cardIds);
@@ -53,13 +40,11 @@ export function routeAndResolve(diagnostics, cardIds) {
     }
     return out;
 }
-/** Severity ordering: errors sort before warnings within a field's list (never dropped, just ranked: VISUAL_EDITOR §Diagnostics "nothing gates" extends to nothing hides). */
-const SEVERITY_RANK = { error: 0, warning: 1 };
 /**
  * Merge N routed groups into `Map<fieldKeyToString(key), Diagnostic[]>`.
  * Dedupes an identical `(severity, message)` pair landing on the same key from
- * more than one group (e.g. the same warning present in both `validate()` and
- * an external feed); within a key, errors sort before warnings.
+ * more than one group (e.g. the same error present in both `validate()` and
+ * an external feed). Producer order within a key.
  */
 export function mergeDiagnostics(...groups) {
     const byKey = new Map();
@@ -80,8 +65,5 @@ export function mergeDiagnostics(...groups) {
                 byKey.set(k, [diagnostic]);
         }
     }
-    for (const arr of byKey.values()) {
-        arr.sort((a, b) => SEVERITY_RANK[a.severity] - SEVERITY_RANK[b.severity]);
-    }
     return byKey;
 }

package/dist/visual/props.d.ts

@@ -61,7 +61,7 @@ export interface VisualEditorProps {
     onError?: EditorErrorHandler;
     /**
      * External diagnostics, routed by `.path` and merged with `quill.validate`
-     * and local commit errors (VISUAL_EDITOR §Diagnostics).
+     * and local commit errors (VISUAL_EDITOR §Diagnostics). Warnings do not draw.
      */
     diagnostics?: Diagnostic[];
     /**

package/dist/visual/strings.d.ts

@@ -66,12 +66,12 @@ export interface VisualStrings extends TableChromeStrings, SlashStrings {
  * interpolates, keyed by name. What it can re-word tracks what that type carries per
  * lane (VISUAL_EDITOR §Diagnostics for why each lands where it does):
  *
- * - **`validation::enum_violation`, `type_mismatch`, `format_violation`,
- *   `must_fill`**: the constraint re-words from the quill's schema at `path`, the
- *   offending value from `args` (`value` / `sourceToken` / `actual`, the engine
- *   testifying to what it saw) and never from the document at `path`: validation
- *   runs post-coercion, so the validator read a value the document does not hold and
- *   a sentence built from `path` names a spelling the user never typed.
+ * - **`validation::enum_violation`, `type_mismatch`, `format_violation`**: the
+ *   constraint re-words from the quill's schema at `path`, the offending value from
+ *   `args` (`value` / `sourceToken` / `actual`, the engine testifying to what it
+ *   saw) and never from the document at `path`: validation runs post-coercion, so
+ *   the validator read a value the document does not hold and a sentence built from
+ *   `path` names a spelling the user never typed.
  * - **`edit::field_coercion_failed`**: re-words from the app's own control state, the
  *   refused value being in neither document (unchanged on throw) nor schema.
  * - **`parse::yaml_error_with_location`, `invalid_structure`**: does not re-word. No

package/dist/visual/structure.d.ts

@@ -21,8 +21,7 @@ export interface FieldModel {
      * `default:`'s absence when the field declares none (DOCUMENT_MODEL). Drives a
      * persistent label `*`; a field can carry both it and a ghosted `default:`,
      * since the two axes are independent. Persistent (schema-derived, survives
-     * filling); the `must_fill` `validate` warning remains the unmet-ness signal.
-     * Label chrome only; never gates.
+     * filling). Label chrome only; never gates.
      */
     required: boolean;
     /** Prose-leaf flags (only meaningful when `control === 'prose'` / array items). */

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@quillmark/svelte",
-	"version": "0.5.0",
+	"version": "0.5.1",
 	"description": "Editor, live-preview and source surfaces over a Quillmark WASM session.",
 	"repository": {
 		"type": "git",