@particle-academy/fancy-conformance 0.22.0 → 0.22.1

package/VERSION

@@ -1 +1 @@
-0.22.0
+0.22.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@particle-academy/fancy-conformance",
-  "version": "0.22.0",
-  "description": "Shared cross-language conformance fixtures for the Fancy suite. One contract, N implementations, and a single table that every implementation asserts in its own CI \u2014 so 'parity' is a test result rather than a claim. Ships the fixture data itself, so a Rust, Go or Python runner can consume it without a JavaScript toolchain.",
+  "version": "0.22.1",
+  "description": "Shared cross-language conformance fixtures for the Fancy suite. One contract, N implementations, and a single table that every implementation asserts in its own CI — so 'parity' is a test result rather than a claim. Ships the fixture data itself, so a Rust, Go or Python runner can consume it without a JavaScript toolchain.",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/Particle-Academy/fancy-conformance.git"

package/runners/README.md

@@ -85,6 +85,15 @@ that reported green while covering nothing.
    `Conformance::version()`. "We're on an old fixture set" should be visible in
    the log rather than inferred months later.
 
+**Reading the fixtures from git? Check out the tag you pin.** A consumer that
+checks this repository out (an `actions/checkout` step, a git dependency) must
+pin that checkout to `v<pinned version>`, never `main`, and keep a test that
+fails when the ref and the pin disagree. Unpinned, every fixture release turns
+every such consumer red at once for a reason none of its commits caused, and
+nobody reads it: four Python ports sat red for weeks that way in 2026-09. The
+pin is the contract, and moving it is a deliberate commit in the consumer. A
+registry install gets this from a committed lockfile, and only from one.
+
 ## Adding a case
 
 A new case lands **here first, red**, then in each implementation. Where an

package/suites/dark-slide/table-cell-model/manifest.json

@@ -12,7 +12,7 @@
       "gridWidthsEmu": "gridWidthsEmu(element, totalEmu) -> the <a:gridCol w> values, in order, as strings."
     },
     "runShape": {
-      "everyValueIsAString": "No golden in this file is a number. Fractional quantities are converted to the INTEGER unit the writer emits — font size and letter spacing in hundredths of a point, padding and border width in EMU — and then stringified. That removes float comparison from the suite entirely, which matters because the four fancy-conformance loaders do NOT agree on how a float golden is compared (PHP, Python and Rust use a scaled 1e-12 epsilon; the TypeScript loader uses exact Object.is). A suite whose verdict depends on which loader ran it is not a conformance suite.",
+      "everyValueIsAString": "No golden in this file is a number. Fractional quantities are converted to the INTEGER unit the writer emits — font size and letter spacing in hundredths of a point, padding and border width in EMU — and then stringified. That removes float comparison from the suite entirely: a value in EMU or hundredths of a point is exactly what the writer emits, so no golden carries a tolerance question. (This note first said the loaders disagree on float comparison. That was already false when it was written: all four have compared exactly since 0.10.0.)",
       "resolvedCell": "{ text, bold, italic, underline, color, fill, align, anchor, fontSizeHundredths, letterSpacingHundredths, caps, padding: {left,right,top,bottom}, borders: {left,right,top,bottom}, colSpan, rowSpan, merged }. Booleans are \"1\" / \"0\". `fill` is null when the cell has none. Each border is null when the cell has none on that side, otherwise { widthEmu, color, style }.",
       "gridWidthsEmu": "An ordered array of strings."
     },