spine-rigc 2.13.3 → 2.14.0

package/NOTICE.md

@@ -38,8 +38,8 @@ Software's terms, not a licence term of this project:
    development dependency for its own gate, and so does an install with
    `spine-core` added beside it. Validation is not optional on either: the gate
    runs through the runtime where it is installed and through rigc's own validator
-   where it is not, and the two are held to the same verdicts in CI on 50 of the
-   51 assertions — the official parser's own parse runs only where the runtime is.
+   where it is not, and the two are held to the same verdicts in CI on 49 of the
+   50 assertions — the official parser's own parse runs only where the runtime is.
 
 > **If a product integrates a Spine Runtime to play rigc's output, that integration
 > is subject to the terms above** — rigc neither creates those terms nor removes

package/README.md

@@ -61,12 +61,12 @@ it cuts both ways:
   is a development dependency: this repository uses it to hold rigc's own validator
   to the round trip's verdicts — in CI, on the public example recipes and every
   selftest call, and on a private corpus of production rigs measured before each
-  release. Of the 51 assertions, 50 run on both; `A00_ROUNDTRIP_PARSE`, the official
+  release. Of the 50 assertions, 49 run on both; `A00_ROUNDTRIP_PARSE`, the official
   parser's own parse, runs only where the runtime is installed and is reported as a
   SKIP elsewhere. There, in the parse's place, the report also carries the model
   side's own two parse rules, `A00_MODEL_READ` and `A00_MODEL_REGIONS_ON_PAGES`,
   which no round-trip rule matches and the registry does not hold — so its summary
-  totals 53 on the core entry, and its last line counts 44 rules on the model side
+  totals 52 on the core entry, and its last line counts 43 rules on the model side
   ([AUTHORING §5.2](docs/AUTHORING.md) has a row for each). Install it beside rigc
   (`bun add -d @esotericsoftware/spine-core`) and the same `rigc` runs the round
   trip on every build. The
@@ -581,9 +581,9 @@ first three work on any reference you have, and `bench` is a repository workflow
 and `bun run fetch-examples`. The reasoning behind them is in
 [the benchmark dossier](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md).
 
-`build` and `validate` both default to `--profile spine` — the 35 validity rules, which
+`build` and `validate` both default to `--profile spine` — the 34 validity rules, which
 ask *is this valid Spine 4.3 that any runtime plays correctly?* `--profile spine-html`
-adds all 51: the other 16 are one renderer's policy and one canvas budget's, and they
+adds all 50: the other 16 are one renderer's policy and one canvas budget's, and they
 fire on perfectly correct editor-produced Spine data, which is why they are opt-in.
 ⇒ **That reason is about foreign data and does not carry to a rig you are authoring
 yourself: author under `--profile spine-html` and read the extra 16 as findings, and
@@ -739,7 +739,7 @@ letting `A17` blame the editor for the harness's own doing.
 | 📥 **[docs/INGEST.md](docs/INGEST.md)** | **working with a skeleton you did not author.** What every command can and cannot do with a foreign `skeleton.json`, reading it with the toolchain, transcription as the route that makes it yours, what each validator complaint means on an export, and the re-pivot/rename/extend recipes. Ships in the package too |
 | 🤖 **[docs/PROMPTING.md](docs/PROMPTING.md)** | **handing the authoring to an AI agent** — the prompt clauses a measured pilot run paid for, and what you can leave unsaid. Ships in the package too |
 | 🔬 **[docs/SPEC_COVERAGE.md](docs/SPEC_COVERAGE.md)** | **the Spine 4.3 format, field by field.** Every key the 4.3 JSON parser and atlas reader take, what each defaults to, and the parser line it comes from — the rows rigc's refusals cite by part number. Ships in the package too |
-| 🎓 **[the benchmark dossier](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md)** | **why you can trust the output.** The yardstick, `diff` and `check` and what neither can see, the eight-rung ladder and the spineboy graduation exam, the run viewer, the 51 named assertions with their profiles, and the selftest that has watched every one of them fire. Repository material — it is not in the npm package |
+| 🎓 **[the benchmark dossier](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md)** | **why you can trust the output.** The yardstick, `diff` and `check` and what neither can see, the eight-rung ladder and the spineboy graduation exam, the run viewer, the 50 named assertions with their profiles, and the selftest that has watched every one of them fire. Repository material — it is not in the npm package |
 | 📋 [LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) · [GATE.md](https://github.com/firejune/rigc/blob/main/docs/GATE.md) · [PILOT.md](https://github.com/firejune/rigc/blob/main/docs/PILOT.md) | the live rung ledger, the clause statements a candidate is graded against, and how to run an agent through the ladder and score what comes back |
 | 🔬 [SURVEY_2026-08-22.md](https://github.com/firejune/rigc/blob/main/docs/SURVEY_2026-08-22.md) | the survey the ladder was climbed by: rigc and the official examples as measured on 2026-08-22, and the gap list ordered by rung. A dated record, not kept current. Repository material |
 | 🧬 [GENERATIONS.md](https://github.com/firejune/rigc/blob/main/docs/GENERATIONS.md) | **Spine data from another generation.** Why a 3.8–4.2 file read as 4.3 fails in silence, the policy that follows (detect from `skeleton.spine`, never guess, play on the matching runtime), what `A16` and `ingest` do with such a file, and the editor as the migration path. Repository material |
@@ -789,7 +789,7 @@ quality."* All six, with their verdicts, are in
 [docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md).
 
 The whole dossier — the yardstick, `diff` and `check` and what neither of them can
-see, every rung, the run viewer, the 51 assertions and the selftest behind them — is
+see, every rung, the run viewer, the 50 assertions and the selftest behind them — is
 [docs/BENCHMARK.md](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md).
 Live rung status is
 [docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md).

package/docs/AUTHORING.md

@@ -233,7 +233,7 @@ What the flags mean:
 | `--manifest` | a cut manifest. Only for a rig with **measured art** behind it; a foreign skeleton has none |
 | `--cut` | `build`, `explain` and `validate`: look up a named cut in `--cuts <cuts.json>`, **instead of** `--rig`/`--motion`/`--out` — the two spellings are one build stated two ways and are refused together. A `cuts.json` is `{ "<name>": { "rig": …, "motion": …, "out": …, "manifest"?: … } }`, every path in it relative to the table's own file, so the table lives with the project that owns the art |
 | `--cuts` | the `cuts.json` `--cut` names. Required beside it — `--cut` alone is refused, with no guess at where the table lives |
-| `--profile` | `spine` = the 35 validity rules (**the default**) · `spine-html` = all 51, opt-in |
+| `--profile` | `spine` = the 34 validity rules (**the default**) · `spine-html` = all 50, opt-in |
 | `--candidate` | `check`, `bench`, `render`, `preview`, `chainfit` and `vote` only: a **compiled** artifact — the directory `build --out` wrote, or a `skeleton.json` path. A directory holding no `skeleton.json`, or a path with nothing at it, is refused `nothing at <path>`, exit 2, nothing written, by every command that takes a build — `validate <dir>` and a directory given to `diff` included (`RC27`). `--atlas <path>` names the atlas when it does not sit beside the skeleton. On `render` and `check` a rigc build whose `skeleton.model.json` is `rigc-compiled/3` or `/2` needs no atlas at all: with no `--atlas` and no atlas beside it, it is drawn from the document's `pages`, the same frames, geometry and figures as with it, and the `atlas` line says `— not there`. An atlas that is there is still read, and held to `pages`: one that differs (edited after the build) is drawn through spine-core, and the `poser` line names the first difference. A build drawn through an atlas that is not there — a `rigc-compiled/1` document, or a build the core refuses — is refused `nothing at <the atlas>: … is drawn through its atlas (<why>)`, exit 2, nothing written; a Spine export without its atlas is refused `nothing at <the atlas>` as it always was. A directory whose files are not one build — a `skeleton.json` or a `skeleton.atlas` from another build beside this one's `skeleton.model.json` — is drawn through spine-core where the runtime can load the pair, the `poser` line naming the two digests or the atlas's first difference; where it cannot, it is refused `<skeleton> does not load against <the atlas>: spine-core draws this pair (<the poser line's why>) and could not resolve it — "<the runtime's own words>". <dir> is not one build: …`, exit 2, nothing written (`RC18`) — another build's skeleton beside this build's atlas typically ends `"Region not found in atlas: <region> (attachment: <name>)"`. Rebuild, or put the build's own three files back beside each other. A Spine export beside an atlas it was not exported with is refused in the same words, ending `The skeleton and the atlas are not one pair`. An atlas copied from another build's directory usually stops earlier, at its pages — their paths are relative to the directory it was written in — and is refused naming the first one: `nothing at <the page>: <the atlas> names it as a page, and spine-core draws this pair through that atlas (<why>). … <dir> is not one build: …`, exit 2, nothing written (`RC18`); an export whose atlas names a page that is not there is refused the same way, ending `and the page has to be there`. A build moved or copied whole away from the directory it was built in stops at the same place, on either poser, and is refused naming the page and the file that names it: `nothing at <the page>: <the skeleton.model.json> names it as a page, and the core draws this build from it. A page path is relative to the build's directory, so a build moved or copied away from the directory it was built in names pages that are not here — build it again where it is, or build it with --copy-images, which writes its pages beside it` (under `--poser spine`, `<the atlas> names it as a page, and spine-core draws this pair through that atlas (--poser spine)` with the same ending), exit 2, nothing written (`RC21`); only where the core refused the files does a page refusal say the directory is not one build. `bench --bones` and `rigc bonedist` — on its `--candidate` and on its `--reference` — refuse a pair the runtime cannot load in the words above with `spine-core poses this pair (bonedist's candidate: …)` or `(bonedist's reference: …)`, exit 2, nothing written (`RC20`); they read no page image, so a build whose pages are elsewhere is measured as it is in place. A `skeleton.json` that is not JSON is refused `rigc: cannot read <the file>: <the parser's words> (line N, column N)`, exit 2, by `render`, `check`, `bench` and `bonedist` as by every other command that reads one (`RC22`). With the atlas gone, `check` on a `rigc-compiled/3` build reads its pages' `scale:` lines off the document, so its texture note and `check.json`'s `textureFrom.candidateScales` are what they are with the atlas; on a `/2` build its texture note says whether the atlas declares a `scale:` line is not read (that document does not state one), and `candidateScales` is `null` (`RC13`). **`vote` and `preview` take it more than once**: `vote` 2–4 times, one per pane, labelled A, B, C, D in the order given; `preview` any number of times, one pane per candidate in the order given, each headed by its path and its gate line, and the same skeleton twice (a directory and its `skeleton.json` are one) is refused by name. `--atlas` goes with one candidate only. Everywhere else a repeat is a typo and is refused |
 | `--animation` | `render`, `preview` and `vote` only: which animation to show. The default is **every** one for `render`, the **first** for `preview` (each candidate's own first, with several), and for `vote` the first of candidate A. A name the skeleton does not have is refused, with the ones it does have listed — and for `vote` and a several-candidate `preview`, so is a name that only *some* candidates have, naming the one that lacks it |
 | `--geometry` | `render` only: also write a `geometry.json` into each frame directory — per frame, every bone's world transform and every slot's region or mesh vertices in world units after skinning, plus each attachment's rest geometry and topology, on the frames' own grid and viewport. Every other file is byte for byte what the render writes without it. Refused with `--slot`/`--hide`, because the geometry is the whole pose whatever is drawn — **§8.2** |
@@ -1947,7 +1947,7 @@ it would simply be a second root.
 | --- | --- | --- |
 | `name` | required, unique — the join key for slots, meshes and timelines | — |
 | `parent` | omitted only by the root bone | none |
-| `length` | bone length; cosmetic in a renderer, part of a faithful reproduction | `0` |
+| `length` | bone length. Drawing reads it nowhere, but a physics constraint driving `rotate`, `shearX` or `scaleX` on this bone steps off it: the solver's lever is the tip, `length` along the bone's own x axis. With `0` there is no tip, and `A23` refuses the constraint by name (§5.2, issue #1195) | `0` |
 | `x`, `y` | position **local to the parent** | `0` |
 | `rotation` | degrees, counter-clockwise, y **up** | `0` |
 | `scaleX`, `scaleY` | | `1` |
@@ -3951,7 +3951,7 @@ is not an array. Every field is optional and each is the payload a firing
 
 Optional with one exception, and only meaningful for rigc's own formations:
 `meshSlots` and `meshTriangles` (the two halves of the mesh budget `A13` measures
-against), `axisBone`, `massBone`, `detached`, `deformMayFold`, `editorRoundTrip`,
+against), `axisBone`, `massBone`, `detached`, `deformMayFold`,
 `consumerDrivenMix`, `idleDrivesMeshes`.
 Nothing in skeleton
 JSON records that a
@@ -4005,33 +4005,6 @@ page turning over, a cloth creasing back on itself, where the reversed winding
 of the field and an honest one**, but it is a loan against a fix, not a fix — and
 what makes it repayable is A39 measuring the ceiling the art can actually take.
 
-🎬 **`editorRoundTrip` is the one field here that names a CONSUMER rather than a
-shape.** Write `"editorRoundTrip": true` when this rig is authored to come back
-out of the Spine editor — imported, hand-edited, exported — and
-`A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP` refuses a physics constraint driving a
-component that editor cannot hold. `true` is the only accepted value; a `false`
-would be a key nothing reads.
-
-⚠️ **Leaving it out is not a weaker gate, and this is the part worth reading.**
-rigc's output is not wrong here: a physics constraint driving `rotate` is valid
-Spine 4.3 that every runtime plays — a cowlick, a tail, an ear — so refusing it by
-default would be refusing correct data on behalf of a pipeline nobody declared.
-What a rig that says nothing gets instead is the **SKIP**, and the SKIP names the
-constraint and the component:
-
-```
-  SKIP  A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP: the rig "look" does not declare `invariants.editorRoundTrip`, so nothing here is gated against the Spine editor. What is here: physics "whip" drives rotate, and the editor's physics model holds x and y only, so a round trip returns that constraint driving nothing at all (issue #540)
-```
-
-📏 **Measured, not inferred:**
-three rigs, twelve constraints, predictions written before the round trip. A lone
-`y` came back and `x` + `y` together came back — the rule is membership, not arity
-— while a lone `rotate`, a lone `scaleX` and a lone `shearX` each came back driving
-**no component at all**, and neither `scaleY` mode rescues `scaleX`. So the fix for
-a refusal is to drive the constraint in `x`/`y`, or to drop the declaration if this
-rig never goes near the editor. ⇒ `A23_PHYSICS_CONSTRAINT_EFFECTIVE` is the same
-loss seen from the far side: it is what fires on the file the editor hands **back**.
-
 🚫 **Do not reach for it to cover a part you have faded out.** A key whose slot
 draws no pixels at that key's own time is already passed over — `A39` measures
 that and says so (§4.11, and the `skipped` line in the `DEFORM` block). Declaring
@@ -4040,6 +4013,14 @@ visible too, which is trading a false positive for a blind spot on the same slot
 ⚠️ And land that alpha-0 key **before** the folding key rather than on it — the
 frames in between are drawn and are gated (§4.11.3).
 
+🗑️ **`editorRoundTrip` was retired in issue #1196, with
+A41, the one rule that read it**, and a rig
+that still declares it is refused as an unknown key: the editor drops a physics
+constraint's `rotate`, `scaleX` and `shearX` only on a bone with no length
+(measured on Spine 4.3.23 and 4.3.26), which `A23_PHYSICS_CONSTRAINT_EFFECTIVE`
+refuses by name on every rig (§5.2), so a declaration could no longer move any
+verdict.
+
 🎛️ **`consumerDrivenMix` names the ik and transform constraints whose mix the
 CONSUMER sets** — from code, at runtime — rather than any animation in this file.
 It is
@@ -6365,9 +6346,9 @@ prints six rows and is one failure here.
 `A00_MODEL_READ` and `A00_MODEL_REGIONS_ON_PAGES` — the first two rows of the
 table below — which stand where `A00_ROUNDTRIP_PARSE`'s parse stands and have no
 round-trip counterpart, so they are not in the registry. That is the whole of the
-difference between the two totals: `<N>` is 53 on the core entry and 51 on `cli.ts build`,
-and the core report's last line states the split — 44 rules on the model side,
-which are the 42 registry assertions the model side runs and those two; the 8 restated over the emitted text;
+difference between the two totals: `<N>` is 52 on the core entry and 50 on `cli.ts build`,
+and the core report's last line states the split — 43 rules on the model side,
+which are the 41 registry assertions the model side runs and those two; the 8 restated over the emitted text;
 and `A00_ROUNDTRIP_PARSE`, which it reports as a SKIP.
 
 🚨 **When `A00_ROUNDTRIP_PARSE` fails, read the report as a report about A00 and
@@ -6405,7 +6386,7 @@ Fix A00 and run it again.
 | `A20_MESH_WEIGHTS_COHERENT` | both ◑ | a weighted vertex with no bone, a negative weight, a bone index out of range, or weights that do not sum to 1. On a rig spec's `"boneIndexing": "raw"` mesh an index out of range or a run that does not decode is refused at compile first (§5.1, issue #917), so here it names a skeleton rigc did not compile. Under `spine-html` also: an unweighted mesh, a binding at weight 0, or **a bone the mesh declares that no vertex binds** — `mesh "x" declares bone "grip_b" and none of its 25 vertices binds it; the weights reference "box", "grip_a"`. Those three are one sentence about rigc's own generators: the bone set a generated mesh declares is the bone set its weights reference, so a `controls` or `chain` name that moves nothing is a defect where a foreign mesh's is not. Fix the rig spec's `controls`/`chain`, a `segments` generator's `bones` (its `influence` line names a bone no vertex binds), or the manifest's `control_bones`. **SKIP** when the skeleton carries no mesh attachment |
 | `A21_MESH_RIM_PINNED` | archetype | a generated ring's rim, a ribbon's entry row, or a contour's outline (which is all of it) is not pinned to its anchor bone at weight 1. **SKIPs** by name on authored or linked geometry and on a `segments` mesh, whose outline is weighted by distance like the rest of it — none of them claims a pinned rim |
 | `A22_MESH_UVS_IN_UNIT_RANGE` | both | a mesh UV outside its region, or a UV array that disagrees with the vertex count. **SKIP** when the skeleton carries no mesh attachment |
-| `A23_PHYSICS_CONSTRAINT_EFFECTIVE` | both | a physics constraint that drives no component, rests at `mix: 0` with **no timeline in any animation keying that `mix` above 0**, has `mass: 0`, has `strength` at or below 0 — `0` says `nothing pulls it back`, below 0 says the offset `is pushed away and grows with every step`, both read off the row's `outside` arms, which the key's refusal quotes too — or has `damping` outside `[0, 1]`, which says `` physics "C" has damping 1.5; must be inside [0, 1] — the per-step decay is `damping ** (60 * step)`, and the runtime runs this value finitely, so refusing it is rigc's call rather than the runtime's: above 1 every velocity grows on every step and the offset diverges ``, the bound read off the row the key's refusal reads; `1` and `0` are inside, since both are finite at every rate — **at rest, and on every physics timeline key**. The timeline arm reads each key through the runtime's own `PhysicsConstraint*Timeline.set`, so a keyed `mass` is judged as the `massInverse` it becomes, and the detail names the animation, the constraint, the key time, the value and the bound. Two differences between the two arms, and the runtime is the reason for both: a **key** of `mix: 0` is accepted, because `update` opens with `if (mix === 0) return;` and muting a constraint for a stretch is what a mix timeline is for — the editor's own `sack-pro` example keys it there on 24 of its 36 mix keys — and a **key** of `strength: 0` is accepted, because it releases the constraint for the span with `damping` and `inertia` still applied and the next key pulls the offset back, measured through spine-core at no NaN, a coast to a limit and a return in 54 steps. As a **setup** value `strength: 0` is still refused by the arm above, and `mix: 0` is refused only when nothing keys it above 0. The `mix` branch above is why `mix` is the one setup value a key can answer for: at rest the constraint is **inert** rather than broken, so a rig that rests muted and is keyed above 0 is refused by nothing, while a rig resting at `mass: 0` is `massInverse` Infinity before anything plays and no key reaches back into that. The detail of the refusal says both halves and how many animations were searched: `` physics "C" has mix 0 and none of the 3 animations keys its mix above 0; the runtime runs this value finitely, so refusing it is rigc's call rather than the runtime's: at 0 `update` returns before it does anything (`PhysicsConstraint.js:109-111`), so the constraint is muted — rest it above 0, or key its mix above 0 in an animation ``. ⚠️ Every reason A23 prints for a setup value is that value's row `basis` arm (§4.4's table) — an arithmetic arm names its expression (`physics "C" has massInverse Infinity; mass must be > 0 — at 0 …`), a behavioural one says it is rigc's call and what the value does. A setup `mix` **below** 0 is told the jiggle is applied inverted, not that it is muted: such a constraint is measured moving its bone by exactly the opposite of a positive mix. The search counts the unnamed global timeline for every constraint whose own `mixGlobal` is set, reads each key through the runtime's accessor, counts every sample of a Bezier between two keys as a value the timeline poses — so two keys of 0 joined by a curve lifted above 0 are a rescue, measured to move the bone — and takes an animation a slider applies like any other. It is the one reading `A36` and `A37` use as well. `inertia`, `wind`, `gravity` and the top of `mix` are bounded nowhere, at rest or keyed. `ingest` does not carry a constraint that drives no component into the spec it writes: it omits it with its timelines and reports `PHYSICS_DRIVES_NOTHING` ([INGEST §2.0](INGEST.md)), so this sentence is met on a file, never on a decompiled rebuild. **SKIP** when the skeleton declares no physics constraint — the same sentence `A36` and `A37` print for their own constraint types |
+| `A23_PHYSICS_CONSTRAINT_EFFECTIVE` | both | a physics constraint that drives no component, rests at `mix: 0` with **no timeline in any animation keying that `mix` above 0**, has `mass: 0`, has `strength` at or below 0 — `0` says `nothing pulls it back`, below 0 says the offset `is pushed away and grows with every step`, both read off the row's `outside` arms, which the key's refusal quotes too — or has `damping` outside `[0, 1]`, which says `` physics "C" has damping 1.5; must be inside [0, 1] — the per-step decay is `damping ** (60 * step)`, and the runtime runs this value finitely, so refusing it is rigc's call rather than the runtime's: above 1 every velocity grows on every step and the offset diverges ``, the bound read off the row the key's refusal reads; `1` and `0` are inside, since both are finite at every rate — **at rest, and on every physics timeline key**. The timeline arm reads each key through the runtime's own `PhysicsConstraint*Timeline.set`, so a keyed `mass` is judged as the `massInverse` it becomes, and the detail names the animation, the constraint, the key time, the value and the bound. Two differences between the two arms, and the runtime is the reason for both: a **key** of `mix: 0` is accepted, because `update` opens with `if (mix === 0) return;` and muting a constraint for a stretch is what a mix timeline is for — the editor's own `sack-pro` example keys it there on 24 of its 36 mix keys — and a **key** of `strength: 0` is accepted, because it releases the constraint for the span with `damping` and `inertia` still applied and the next key pulls the offset back, measured through spine-core at no NaN, a coast to a limit and a return in 54 steps. As a **setup** value `strength: 0` is still refused by the arm above, and `mix: 0` is refused only when nothing keys it above 0. The `mix` branch above is why `mix` is the one setup value a key can answer for: at rest the constraint is **inert** rather than broken, so a rig that rests muted and is keyed above 0 is refused by nothing, while a rig resting at `mass: 0` is `massInverse` Infinity before anything plays and no key reaches back into that. The detail of the refusal says both halves and how many animations were searched: `` physics "C" has mix 0 and none of the 3 animations keys its mix above 0; the runtime runs this value finitely, so refusing it is rigc's call rather than the runtime's: at 0 `update` returns before it does anything (`PhysicsConstraint.js:109-111`), so the constraint is muted — rest it above 0, or key its mix above 0 in an animation ``. ⚠️ Every reason A23 prints for a setup value is that value's row `basis` arm (§4.4's table) — an arithmetic arm names its expression (`physics "C" has massInverse Infinity; mass must be > 0 — at 0 …`), a behavioural one says it is rigc's call and what the value does. A setup `mix` **below** 0 is told the jiggle is applied inverted, not that it is muted: such a constraint is measured moving its bone by exactly the opposite of a positive mix. The search counts the unnamed global timeline for every constraint whose own `mixGlobal` is set, reads each key through the runtime's accessor, counts every sample of a Bezier between two keys as a value the timeline poses — so two keys of 0 joined by a curve lifted above 0 are a rescue, measured to move the bone — and takes an animation a slider applies like any other. It is the one reading `A36` and `A37` use as well. `inertia`, `wind`, `gravity` and the top of `mix` are bounded nowhere, at rest or keyed. `ingest` does not carry a constraint that drives no component into the spec it writes: it omits it with its timelines and reports `PHYSICS_DRIVES_NOTHING` ([INGEST §2.0](INGEST.md)), so this sentence is met on a file, never on a decompiled rebuild. 🦴 **A lever drive on a bone with no lever** (issue #1195): a constraint driving `rotate`, `shearX` or `scaleX` on a bone whose `length` is 0 (or states none) is refused, at rest, with one sentence per reading. `rotate` and `shearX` chase the bone's tip, so with no tip the solver aims the bone at a **world** direction — measured through rigc's poser on a chain held still for 3 s, a length-0 bone turns 53.204° from a 90° rest and holds there, where length 0.01 moves 0.0000: `` physics "C" drives rotate on bone "B" whose length is 0 — with no tip the solver aims the bone at world angle 0 and holds it there; give "B" a length or drive x/y instead ``. The rest angle is not read: a bone resting at world 0° does not move, but only until a key or a parent turns it. `scaleX` divides the motion along the bone by its length and adds nothing at 0, so the drive does nothing: `` physics "C" drives scaleX on bone "B" whose length is 0, which the solver divides the motion by, so it drives nothing; give "B" a length ``. Fix in the **rig spec**: give the bone its `length` (§3.2), measured off the art it carries, or, for the first sentence, drive the constraint in `x`/`y` in the **motion spec** instead. `x` and `y` read the bone's origin and never its tip, so a constraint driving only those on a length-0 bone is not refused; the editor's own example exports carry them there. The Spine editor's export drops `rotate`, `scaleX` and `shearX` from a physics constraint on a zero-length bone and keeps them on any bone with a length — measured on 4.3.23 and 4.3.26, issue #1196 — so what this clause refuses is also what the editor would silently lose. **SKIP** when the skeleton declares no physics constraint — the same sentence `A36` and `A37` print for their own constraint types |
 | `A24_AXIS_SPACE_STROKE` | archetype | a bone under the rig's `axisBone` was keyed with a screen-space Y component, or the axis bone itself was keyed. **SKIP** when the rig declares no axis bone, and also when no animation keys that bone or anything under it |
 | `A25_DETACHED_BONE_PARENTAGE` | archetype | a bone the rig declares `detached` is a descendant of the bone it must never hang under |
 | `A26_SLOT_DRAW_ORDER` | archetype | the emitted slots are not the rig's slot table — a slot is out of order, is not in the table at all, or is in the table and missing from the skeleton (§3.3). **SKIP** when the rig declares no canonical slot order. ⚠️ A skeleton with **no** slot beside a rig that declares some is **not** a skip, and it is the one rule in this family where an empty loop is not a vacuous pass: the completeness clause reads it as every declared slot lost and names them |
@@ -6423,7 +6404,6 @@ Fix A00 and run it again.
 | `A38_SKIN_MEMBERS_ARE_SKIN_REQUIRED` | both | a bone or constraint a skin activates that is not `skinRequired` (the list changes nothing), or one that is `skinRequired` and no skin activates (it is never active). Two keys in two places, and only together do they mean "this belongs to that skin" (§3.4.1). **SKIP** when no skin activates anything and nothing is `skinRequired` |
 | `A39_DEFORM_KEEPS_TRIANGLE_WINDING` | archetype | a `deform` key reverses a triangle's winding, so the mesh has locally turned inside out and draws its texture backwards there (§4.11). The detail names the animation, the slot, the attachment, the key index and time, and each reversed triangle with its vertex triple and its signed area before and after. Measured at the key's **own** time, deformed against the same posed bones undeformed, so a mirrored slot bone cancels and a wrong *projection* with intact winding is correctly silent. A projection past its fold angle is the usual cause — [FACE.md §4.2](FACE.md) has the closed form. Legitimate art does fold, so declare `invariants.deformMayFold` (§3.7) for a slot that folds on purpose. ⚠️ A key whose slot **draws no pixels at that key's own time** — faded to alpha exactly 0, or showing another attachment — is measured and then passed over, because "draws its texture backwards" is false when nothing of it is drawn; the key is named on the stats line (`deformKeysNotDrawn`) and in the `DEFORM` block, never silently. The bar is **exactly 0**: at alpha 0.5 the fold is still refused and the alpha is in the message. It is per key and per time, so the same slot folding at full alpha in another animation is still refused. ⚠️ And the **spans between** consecutive keys are scanned too (§4.11.3): the runtime interpolates, so a deform inside its fold angle at every key can be past it in between. That refusal is its own sentence — `BETWEEN key 0 (t=0s) and key 1 (t=0.5s), at t=…` — with the time solved for in closed form and then posed and measured like any key, alpha read at that same moment. `deformSpansScanned` says on every green build that the scan ran. ⚠️ And the **frame** it poses in is the one the animation is reached in (§4.11.4): on a track when nothing applies it, and otherwise once per **slider**, with that slider's mapping inverted and its bone driven until the runtime selects the key's own time — because a slider picks the time, so the two are one number and posing them independently is a frame that never occurs. The frame is on every `DEFORM` line, on the stats line as `deformFrames`, and in the refusal itself when it is not the track. A key at a time **no dial value selects** is measured in the frame the runtime does land on, left out of `deformKeysMeasured` and named as `deformKeysUnreachable`/`deformUnreachable` — never refused and never silent. ⚠️ And the **skin** it poses in is the one the timeline is keyed on (§4.11.5), since a deform's address is a `skin / slot / attachment` triple: the pose wears that skin, which also switches on any `skin: true` bone or constraint it activates, and the "nothing is drawn" sentence names the skin it was read under. **SKIP** when no animation carries a deform timeline, when nothing keyed has triangles, when every mesh keyed is exempt, when every key measured draws no pixels or is unreachable *and no span between them folds where anything is drawn*, or when there is no rig info at all |
 | `A40_SLIDERS_COMPOSE_ON_A_SHARED_TARGET` | both | two or more sliders whose animations key the same timeline, where a later one is not `additive` — it writes that property outright at `mix: 1` and every earlier slider on it is dead (§3.5.2). Also fires when the shared timeline **cannot** be applied additively (a slot colour, an attachment swap, a draw order, an ik mix, a path's `spacing`, most physics properties), where `"additive": true` is not the fix and one of the two has to go. ⭐ Which of the two it is, is **posed rather than read off `Timeline.additive`**: the shared timeline is applied twice with `add` set and the detail says what it did (two classes declare that flag falsely about themselves: a path constraint's `mix` and a slider's `time` compose although the flag says they do not). The detail names the bone or slot and the property, every slider keying it in `constraints` order with its flag, which one wins today, and the class that was posed. Four shapes are deliberately not findings: a slider below `mix: 1` or with its `mix` keyed (the apply is then a lerp from the current pose, not an overwrite), two `skinRequired` sliders no skin activates together, two sliders on different properties, and a shared timeline that writes **nothing a pose holds** — an `events` timeline fires no event under a slider (`firedEvents` is null), so neither slider has anything there for the other to erase. **SKIP** when fewer than two sliders are at full authority; a PASS means two were compared |
-| `A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP` | both | a physics constraint driving a component the **Spine editor** cannot hold, on a rig that declared `invariants.editorRoundTrip` (§3.7). The editor's physics model holds `x` and `y` only, with no cap on how many at once, so a constraint driving `rotate`, `scaleX` or `shearX` is imported, exported and handed back driving **nothing** — measured over three rigs and twelve constraints with the predictions written first. The detail names the constraint and each component. ⚠️ rigc's own output is correct — every runtime plays a rotation jiggle — so this is opt-in and the default is *not* silence: on a rig that declares nothing it **SKIPs**, and the SKIP names the constraint and the component anyway, so an author learns without having asked. Fix by driving the constraint in `x`/`y`, or by dropping the declaration if the rig never goes near the editor. Disjoint from `A23_PHYSICS_CONSTRAINT_EFFECTIVE` by construction: A23 refuses an **empty** driven set, which is what comes back from the editor, and this refuses a non-empty one that will not survive going in. **SKIP** also when the rig declares the editor and carries no physics constraint at all |
 | `A42_DRIVEN_CONSTRAINTS_UPDATE_AFTER_THEIR_DRIVER` | both | a slider whose animation keys a property of a constraint **at or before it** in `constraints` (§3.5.2) — a slider's `mix` or `time`, an ik or transform mix, a path `position`, `spacing` or `mix`, any physics value. That array is the update order for every kind, and each constraint reads its own applied pose when its turn comes — `Slider.update` takes `mix` as the alpha it applies with and `time` as the time it applies at, `PhysicsConstraint.update` returns on `mix` 0 before reading the rest — so the key lands after the only read of it and `Posed.resetConstrained` discards it before the next frame: what the driven constraint drives is dead at every position of the driving dial, although its pose still holds the number. The detail names the slider, the driven constraint with its kind, both array indices, the property, the runtime class whose `update` reads it, and the animation the key sits in. Fix by moving the driver earlier, or by keying that property from a slider that already is. **The two indices equal is the same failure**: a slider cannot key its own `mix` or `time`, and one muted at setup that keys its own `mix` up never applies anything at all — `A37` is silent there, because it asks whether *an* animation keys the mix and not which one. **Two shapes it deliberately leaves out**, both measured: a `physics` `reset` key, which fires on a crossed frame time and so never fires from a slider at all, in either order — the reorder would repair nothing; and a physics timeline naming no constraint, which is every physics constraint declaring that property global and IS refused for the ones already run. Disjoint from `A40` by construction: `A40` asks who writes a shared property last and excludes every slider whose `mix` is keyed, this asks whether anything reads what was written. **SKIP** when the skeleton declares no slider, and when no slider's animation keys a constraint property — that SKIP names any `reset` keys it found — a pass means a driver and a driven were compared |
 | `A43_TWO_COLOR_TINT_LOADS_AND_POSES_AS_WRITTEN` | both | a slot's `dark` (§3.3) or an `rgba2` / `rgb2` timeline (§4.4) that the runtime does not hold as the file states it. Three shapes, all of which parse in silence: a `dark` the slot reader **drops** — it takes the field through a truthiness test, so `""` is discarded without a word and the slot renders with one colour; a `dark` that is **not six hex digits** — `Color.setFromString` slices fixed offsets and stores whatever `parseInt` gives back, so `"4020"` loads a channel of `NaN`; and an `rgba2` or `rgb2` timeline on a slot with **no `dark` at all**, where the runtime allocates no dark colour and the first `state.apply` throws in the consumer's process. The keyed half is read by posing: the animation is stepped to each key's own time — at the key **as the runtime stores it**: spine-core keeps key times as 32-bit floats, so a key at `0.2` is posed at `0.20000000298…`, the later of the two, and not one float step before it, where a first key still shows the setup value and a stepped key the one before, and the posed `color` and `darkColor` are compared against the hex the key states, to half a quantisation step (`1/510`). The detail names the slot, the value found and the value required. ⚠️ The required value is parsed **here** and not through `Color.fromString`, because a check that read it out of the parser it is checking would agree with that parser whatever it did. `compile.ts` refuses the third shape outright in a rig rigc builds; this is the same fact held against a skeleton it did not write. An `rgb2` key's light colour is compared over its three channels only: the light alpha is not its to state, and it is left where it was. **SKIP** when no slot declares a `dark` and no animation keys an `rgba2` or `rgb2` — there is then no two-colour tint to read back |
 | `A44_LINKED_MESH_STATES_NO_GEOMETRY_OF_ITS_OWN` | both | a **linked mesh** (§3.4) — `type: "linkedmesh"`, or a `type: "mesh"` carrying `source` — that also states `uvs`, `triangles`, `vertices`, `hull` or `edges`. The parser returns from the `source` branch before `readVertices` (`SkeletonJson.ts:582-586`), so those keys are read by **nothing at all** and `setSourceMesh` fills the attachment with the source's arrays instead: the file says one mesh and every runtime draws another, in silence. The detail names the attachment by skin, slot and placeholder, every key it states, the `source` and where the parser looks for it — the two defaults spelled out, because an omitted `skin` is the **default** skin rather than the one the link is written in — and the shape the keys describe beside the shape the attachment loaded. ⚠️ **`width`/`height` are not part of this.** `setSourceMesh` overwrites both with the source's, so they are as dead at runtime — but the parser reads them (`:569-570`), the format carries them on a link and rigc emits them, so refusing them would refuse every link rigc writes (§3.4). `compile.ts` refuses the same shape outright in a rig rigc builds (§5.1); this is that fact held against a skeleton it did not write, and `ingest` reports it as `ATTACHMENT_LINK_GEOMETRY` ([INGEST §2.0](INGEST.md)). **SKIP** when no attachment in the skeleton takes its geometry from another — which is almost every skeleton, so a pass here means a link was read |

package/docs/FACE.md

@@ -1347,14 +1347,26 @@ which declares no constraints at all and so can carry no slider. What it found:
   omitting a default — which is why `A23_PHYSICS_CONSTRAINT_EFFECTIVE` refuses it
   by name. Independent of the ordering.
 
-  ✅ **Why, measured.** It is not elision and not a defect in one field:
-  the editor's physics model holds `x` and `y` and nothing else, with no limit on
-  how many at once. Three rigs, twelve constraints, predictions written before the
-  round trip — a lone `y` came back, `x` and `y` together came back, and a lone
-  `rotate`, a lone `scaleX` and a lone `shearX` each came back as **no components
-  at all**, with every constraint's fixed-point `strength` returning exactly so a
-  silent harness failure could not read as a finding. ⇒ **A rotation-driven
-  jiggle does not survive the editor, and no `scaleY` mode substitutes for it.**
+  ✅ **Why, measured** — and corrected. It is not elision and not a defect in
+  one field. Issue #540 measured three rigs and twelve constraints, predictions
+  written before the round trip: a lone `y` came back, `x` and `y` together came
+  back, and a lone `rotate`, a lone `scaleX` and a lone `shearX` each came back as
+  **no components at all**, with every constraint's fixed-point `strength`
+  returning exactly. It read that as *"the editor's physics model holds `x` and
+  `y` and nothing else"*, and that reading was wrong.
+
+  🔁 **Corrected 2026-10-06 (issue #1196), on Spine 4.3.23 and 4.3.26:** what
+  decides the loss is the **bone's length**, not the component. The editor's own
+  example export `sack-pro` keeps 18 of 18 `rotate` constraints through the same
+  import and export, and deleting the `length` of one of its bones loses `rotate`
+  on exactly that one constraint. `look` with a 40-unit `ahoge_whip` keeps
+  `rotate`, `scaleX` and `shearX` each; at 0.01 and 1 `rotate` is kept too; with no
+  length all three are lost, on both versions. `look`'s `ahoge_whip` was emitted
+  with no length; #540's rigs were not at hand to read, but every row it reported
+  is reproduced here at length 0. ⇒
+  **A rotation-driven jiggle survives the editor on a bone that has a length**,
+  and `A23_PHYSICS_CONSTRAINT_EFFECTIVE` refuses one on a bone that has none
+  (issue #1195).
 
   ✅ **And the locus is measured: the loss is at EXPORT** — against Spine
   4.3.26 and without decoding the project format. `gallery/look`'s build and three variants of its
@@ -1371,18 +1383,17 @@ which declares no constraints at all and so can carry no slider. What it found:
   the exporter wrote nothing for it. It is the editor's **writer**, not its
   reader, and not rigc's emitter.
 
-  ✅ **And the gate says so before the trip, not after.** A face rig that is
-  authored to come back out of the editor declares
-  `"invariants": { "editorRoundTrip": true }` (AUTHORING §3.7) and
-  `A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP` refuses the constraint by name at build
-  time, with the fix in the message: drive it in `x`/`y`, or drop the declaration.
-  ⚠️ A rig that declares nothing is **not** silent either — A41 SKIPs and the skip
-  names the constraint and the component, which is the whole reason the rule is
-  opt-in rather than default-off. rigc's own output is not wrong here: a
-  rotation jiggle is valid Spine 4.3 that every runtime plays, and refusing it for
-  everybody would be refusing correct data on behalf of one consumer. ⇒ A23 and
-  A41 are the same loss from opposite sides of the trip: A41 fires on what goes
-  in, A23 on what comes back.
+  The importer stores the value on a zero-length bone too, at 4.3.23 as well as
+  4.3.26 (issue #1196: `rotate: 0.234375` lands as `3e 70 00 00` in the project,
+  and the JSON and binary exports both omit it — the binary export of a project
+  holding `rotate: 1` is byte-identical to one holding NaN).
+
+  🗑️ **A41, the rule that gated the editor round trip, and its declaration
+  `invariants.editorRoundTrip` were retired in issue #1196.** They gated the
+  components rather than the bone, so they refused rotation physics the editor
+  keeps, and once A23 refuses those components on a zero-length bone a rig that
+  passes it has nothing the editor's export drops — the declaration could no
+  longer move a verdict.
 - 🔸 Unexplained, and **unreproduced by anything in this tree**: `diff` reports
   `animations.curve_kinds` moved on **196 of 200** keys in every round trip taken,
   the clean one included. Visually small once the ordering is fixed — but it is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spine-rigc",
-  "version": "2.13.3",
+  "version": "2.14.0",
   "description": "AI-authored Spine 2D rigging and animation, verified before it is written. rigc compiles a rig spec into Spine 4.3 skeleton data, gates it with named assertions held to a spine-core round trip's verdicts, and emits nothing that fails. Output imports into the Spine editor. Ships as an agent skill.",
   "type": "module",
   "bin": {

package/src/assertions/bodies/a23.ts

@@ -173,6 +173,56 @@ export function a23PhysicsConstraintEffective({ fail, skip, stats }: Verdicts, f
     if (!components.length) {
       fail('A23_PHYSICS_CONSTRAINT_EFFECTIVE', `${where} drives no component; it parses and does nothing`);
     }
+    // --- a lever drive on a bone with no lever (issue #1195) ---------------
+    //
+    // `rotate`, `shearX` and `scaleX` are stepped off the bone's tip,
+    // `length·(a, c)` (`stepPhysics` in `src/core/constraints_physics.ts`,
+    // held to spine-core at tolerance 0); `x` and `y` read only the origin, so
+    // they are not refused here — the editor's own example exports and
+    // rigc's public builds carry them on bones of length 0 and they step as
+    // authored. The two lever readings fail in opposite directions, so they
+    // print two sentences:
+    //
+    // 📏 rotate / shearX: the offset chases `atan2(dy + ty, dx + tx)`, and with
+    // no tip and no motion that is `atan2(0, 0)` = 0 — a WORLD direction —
+    // where any tip at all makes it the bone's own previous direction.
+    // Measured through the core on a four-bone chain held still for 3 s
+    // (inertia 0.5, strength 100, damping 0.85, weight 0.2794): at length 0
+    // the bone turns 26.602° from a 45° rest, 53.204° from 90°, 106.408° from
+    // 180°, and holds there; at length 0.01 it moves 0.0000. The swing under
+    // motion, by contrast, is continuous in the length (0.914° at 36.5 up to
+    // 64.934° at 0 on one bounce) — that is the author's tuning, not a defect,
+    // and this clause does not judge it.
+    //
+    // ⚠️ The rest ANGLE is not read. The same probe resting at world 0° moves
+    // 0.000° at length 0 — but only because the bone already points where the
+    // solver aims it. A key that turns the bone, or a parent that turns it,
+    // breaks that, so a length-0 bone resting at 0° is the same defect waiting
+    // for its first rotation, and refusing it by the angle would refuse a
+    // pose rather than a rig.
+    //
+    // 📏 scaleX: the along-bone motion is divided by `length·|x column|` and
+    // nothing is added when that is 0, so the drive does nothing — every
+    // length-0 rung of the same probe read 0.0000, where 0.01 threw the tip
+    // 806 units. It is this assertion's first clause reached through the bone
+    // rather than the component fields.
+    if (physics.boneLength === 0) {
+      const turns = components.filter((k) => k === 'rotate' || k === 'shearX');
+      if (turns.length) {
+        fail(
+          'A23_PHYSICS_CONSTRAINT_EFFECTIVE',
+          `${where} drives ${turns.join(' and ')} on bone "${physics.bone}" whose length is 0 — with no tip the solver aims the bone ` +
+            `at world angle 0 and holds it there; give "${physics.bone}" a length or drive x/y instead`,
+        );
+      }
+      if (components.includes('scaleX')) {
+        fail(
+          'A23_PHYSICS_CONSTRAINT_EFFECTIVE',
+          `${where} drives scaleX on bone "${physics.bone}" whose length is 0, which the solver divides the motion by, so it drives ` +
+            `nothing; give "${physics.bone}" a length`,
+        );
+      }
+    }
     const pose = physics.setup;
     // The four bounded fields, each judged by its `PHYSICS_POSE_RULES` row.
     // The wording is per-field and stays so: "it is muted" and "nothing

package/src/assertions/constraint_words.ts

@@ -14,29 +14,21 @@ import type { ConstraintFacts, ConstraintTimeline } from './facts/constraints.ts
 import type { RigInfo } from '../types.ts';
 
 /**
- * Every component a physics constraint can drive (`PhysicsConstraintData`), and
- * the subset the **Spine editor** models.
+ * Every component a physics constraint can drive (`PhysicsConstraintData`), the
+ * vocabulary A23 reads when it asks whether a constraint drives anything.
  *
- * ⭐ One list, read by both A23 and A41, because the relationship between those
- * two rules is the thing most worth keeping true: A23 fires when the driven set
- * is EMPTY, A41 when it contains something outside `EDITOR_PHYSICS_COMPONENTS`.
- * Written against one array those conditions cannot both hold on one constraint,
- * and a reader can see that they cannot. Two copies of the vocabulary could
- * drift into overlapping, and a rig refused twice for one fact is a report that
- * has stopped saying what is wrong with it.
- *
- * 📏 The subset is measured rather than read off a document, and it is the whole
- * of issue #540: three rigs, twelve constraints, predictions recorded before the
- * round trip and scored by the code that printed them. A lone `y` came back, `x`
- * and `y` together came back — so the rule is membership and not arity — and a
- * lone `rotate`, a lone `scaleX` and a lone `shearX` each came back driving no
- * component at all, with neither `scaleY` mode rescuing `scaleX`. Every
- * constraint carried a fixed-point `strength` and all twelve returned exactly,
- * so the rows that reported nothing were reading live data. Measured on Spine
- * 4.3.26 Professional.
+ * 📏 It stood beside a second set, the components "the Spine editor models",
+ * read by A41 (the editor round-trip rule) and measured in issue #540 as
+ * `x` and `y`. Issue #1196 measured what that was really seeing, on Spine 4.3.23
+ * and 4.3.26: the editor imports a physics constraint's `rotate`, `scaleX` and
+ * `shearX` into its project and its JSON and binary exports omit them **only on
+ * a bone with no length** — on any bone with a length (0.01, 1, 40 tried) all
+ * three come back, and the editor's own example export keeps 18 of 18 `rotate`
+ * constraints through the same trip. A23 refuses those components on a
+ * zero-length bone (issue #1195), so a rig that passes it has nothing the editor drops, and
+ * A41, its declaration and its set were retired rather than reworded.
  */
 export const PHYSICS_COMPONENTS = ['x', 'y', 'rotate', 'scaleX', 'shearX'] as const;
-export const EDITOR_PHYSICS_COMPONENTS: ReadonlySet<(typeof PHYSICS_COMPONENTS)[number]> = new Set(['x', 'y'] as const);
 
 /**
  * The half of a muted-at-rest refusal that says what was searched, and how

package/src/assertions/facts/constraints.ts

@@ -2,7 +2,7 @@
  * The constraints and the timelines that key them, as the bodies that ask
  * "does this constraint do anything" read them (issue #1025, step 4c of
  * #380) — the census's F12 to F17 and F19 with R1 and R2, for A23, A36, A37,
- * A41, A42, A47 and A48.
+ * A42, A47 and A48.
  *
  * ⭐ **The order is the runtime's update order**, which is the file's
  * `constraints` array and the document's: a body that prints one line per
@@ -56,7 +56,19 @@ export interface ConstraintEntry {
   readonly name: string;
   /** The runtime class the constraint updates as (`IkConstraint`, `Slider`, …) — the word A42's sentence names `update` on. */
   readonly runtimeClass: string;
-  readonly physics?: { readonly bone: string; readonly components: PhysicsComponents; readonly setup: PhysicsSetup; readonly step: number };
+  readonly physics?: {
+    readonly bone: string;
+    /**
+     * The bone's `length`, as the runtime holds it after its parse (0 where the
+     * file leaves it out) — the lever a `rotate`, `shearX` or `scaleX` drive is
+     * stepped with (issue #1195): the tip `length·(a, c)` the rotation chases,
+     * and the radius the along-bone motion is divided by for `scaleX`.
+     */
+    readonly boneLength: number;
+    readonly components: PhysicsComponents;
+    readonly setup: PhysicsSetup;
+    readonly step: number;
+  };
   readonly path?: { readonly bones: readonly string[]; readonly slot: string; readonly setup: { readonly mixRotate: number; readonly mixX: number; readonly mixY: number } };
   readonly slider?: {
     /** The animation it applies — its name, how many timelines it carries and its duration — or `null` when it applies none. */
@@ -118,7 +130,7 @@ export interface ConstraintTimeline {
   readonly posed?: (value: number) => number;
 }
 
-/** What A23, A36, A37, A41, A42, A47 and A48 read. */
+/** What A23, A36, A37, A42, A47 and A48 read. */
 export interface ConstraintFacts {
   /** How many animations the skeleton declares. */
   readonly animations: number;

package/src/assertions/kinds.ts

@@ -88,7 +88,6 @@ export const ASSERTION_KIND: Readonly<Record<string, AssertionKind>> = {
   A38_SKIN_MEMBERS_ARE_SKIN_REQUIRED: 'validity',
   A39_DEFORM_KEEPS_TRIANGLE_WINDING: 'archetype',
   A40_SLIDERS_COMPOSE_ON_A_SHARED_TARGET: 'validity',
-  A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP: 'validity',
   A42_DRIVEN_CONSTRAINTS_UPDATE_AFTER_THEIR_DRIVER: 'validity',
   A43_TWO_COLOR_TINT_LOADS_AND_POSES_AS_WRITTEN: 'validity',
   A44_LINKED_MESH_STATES_NO_GEOMETRY_OF_ITS_OWN: 'validity',

package/src/assertions/model/constraints.ts

@@ -103,6 +103,8 @@ function entryOf(doc: CompiledDocument, kind: ConstraintKind, name: string, reco
         ...base,
         physics: {
           bone: record.bone,
+          // The length the core's step is handed (`bone(state, c.bone).length ?? 0` in `src/core/constraints.ts`): the parser's 0 where the document leaves it out.
+          boneLength: doc.bones.find((b) => b.name === record.bone)?.length ?? 0,
           components: { x: record.x, y: record.y, rotate: record.rotate, scaleX: record.scaleX, shearX: record.shearX },
           setup: { mix: record.mix, massInverse: record.massInverse, strength: record.strength, damping: record.damping },
           step: record.step,

package/src/assertions/model/declared.ts

@@ -45,7 +45,6 @@ void MESH_KINDS_COMPLETE;
 type Check = (value: unknown, at: string, problems: string[]) => void;
 const say = (problems: string[], at: string, value: unknown, what: string): void => void problems.push(`${at} is ${JSON.stringify(value) ?? 'absent'}, not ${what}`);
 const str: Check = (v, at, p) => (typeof v === 'string' ? undefined : say(p, at, v, 'a string'));
-const bool: Check = (v, at, p) => (typeof v === 'boolean' ? undefined : say(p, at, v, 'true or false'));
 const num: Check = (v, at, p) => (typeof v === 'number' && Number.isFinite(v) ? undefined : say(p, at, v, 'a finite number'));
 const nullable = (inner: Check): Check => (v, at, p) => (v === null ? undefined : inner(v, at, p));
 const list = (inner: Check, length?: number): Check => (v, at, p) => {
@@ -74,7 +73,6 @@ const RIG_FIELDS: Readonly<Record<keyof RigInfo, Check>> = {
   meshDeclaredBones: record(list(str)),
   meshSoftBones: record(str),
   deformMayFold: list(str),
-  editorRoundTrip: bool,
   consumerDrivenMix: list(shape({ type: oneOf(['ik', 'transform']), constraint: str, why: str })),
   idleDrivesMeshes: nullable(str),
   basePlates: list(str),

package/src/assertions/model/index.ts

@@ -85,7 +85,6 @@ import { a28RibbonRowsShareWeights } from '../bodies/a28.ts';
 import { a33VertexAttachmentGeometry } from '../bodies/a33.ts';
 import { a36PathConstraintEffective } from '../bodies/a36.ts';
 import { a37SliderConstraintEffective } from '../bodies/a37.ts';
-import { a41PhysicsSurvivesEditorRoundTrip } from '../bodies/a41.ts';
 import { a42DrivenConstraintsUpdateAfterTheirDriver } from '../bodies/a42.ts';
 import { a44LinkedMeshStatesNoGeometryOfItsOwn } from '../bodies/a44.ts';
 import { a47IkConstraintNotMutedThroughout } from '../bodies/a47.ts';
@@ -294,7 +293,6 @@ export const MOVED_ASSERTIONS: readonly MovedAssertion[] = [
   { code: 'A22_MESH_UVS_IN_UNIT_RANGE', run: (v, read, _input, supply) => a22MeshUvsInUnitRange(v, supply.meshes(read)), unread: SKIP_NO_MODEL },
   { code: 'A39_DEFORM_KEEPS_TRIANGLE_WINDING', run: (v, read, input, supply) => a39DeformKeepsTriangleWinding(v, supply.deformSurvey(read), supply.rigInfo(read, input)), unread: SKIP_NO_MODEL },
   { code: 'A23_PHYSICS_CONSTRAINT_EFFECTIVE', run: (v, read, _input, supply) => a23PhysicsConstraintEffective(v, supply.constraints(read), supply.meshes(read)), unread: SKIP_NO_MODEL },
-  { code: 'A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP', run: (v, read, input, supply) => a41PhysicsSurvivesEditorRoundTrip(v, supply.constraints(read), supply.rigInfo(read, input)), unread: SKIP_NO_MODEL },
   { code: 'A36_PATH_CONSTRAINT_EFFECTIVE', run: (v, read, _input, supply) => a36PathConstraintEffective(v, supply.constraints(read)), unread: SKIP_NO_MODEL },
   { code: 'A37_SLIDER_CONSTRAINT_EFFECTIVE', run: (v, read, _input, supply) => a37SliderConstraintEffective(v, supply.constraints(read)), unread: SKIP_NO_MODEL },
   { code: 'A47_IK_CONSTRAINT_NOT_MUTED_THROUGHOUT', run: (v, read, input, supply) => a47IkConstraintNotMutedThroughout(v, supply.constraints(read), supply.rigInfo(read, input)), unread: SKIP_NO_MODEL },

package/src/compile.ts

@@ -837,13 +837,13 @@ const SKIN_ORDER: OrderedCollection = {
  * choosing a member of it.
  *
  * It is deliberately **not** conditional on anything: not on the rig declaring a
- * slider, and not on the rig declaring the editor as a consumer. A slider is what
- * makes the difference bite today and `invariants.editorRoundTrip` is how a rig
- * says the editor is downstream, but the emitted order is a claim about the
- * editor either way, and a check that only ran for some rigs would make the claim
- * hold for some and not others with nothing in the file saying which — adding the
- * slider, or the declaration, would then be the edit that refuses a rig that built
- * yesterday. What issue #543 changed is the size of what is claimed, not who it is
+ * slider, and not on whether the editor is downstream of it, which a rig spec
+ * does not state (the one declaration that did, `invariants.editorRoundTrip`,
+ * was retired in issue #1196). A slider is what makes the difference bite today,
+ * but the emitted order is a claim about the editor either way, and a check that
+ * only ran for some rigs would make the claim hold for some and not others with
+ * nothing in the file saying which — adding the slider would then be the edit
+ * that refuses a rig that built yesterday. What issue #543 changed is the size of what is claimed, not who it is
  * claimed for.
  *
  * ⚠️ `what` is a parameter and not a second copy of this walk because issue #541
@@ -7551,7 +7551,6 @@ function buildRigInfo(
     meshDeclaredBones,
     meshSoftBones,
     deformMayFold,
-    editorRoundTrip: rig.invariants?.editorRoundTrip === true,
     // `parseRigSpec` resolved every entry against the rig's own constraints.
     consumerDrivenMix: (rig.invariants?.consumerDrivenMix ?? []).map((e) => ({ type: e.type, constraint: e.constraint, why: e.why })),
     // `parseRigSpec` refused every shape but a non-blank `why`.

package/src/rig.ts

@@ -315,7 +315,12 @@ export interface RigBone {
   name: string;
   /** Omitted only by the skeleton's single root bone. */
   parent?: string;
-  /** Default 0. Cosmetic in a renderer; part of a faithful reproduction. */
+  /**
+   * Default 0. Drawing reads it nowhere, but a physics constraint driving
+   * `rotate`, `shearX` or `scaleX` on this bone steps off its tip — `length`
+   * along the bone's x axis is the solver's lever — so a length of 0 there is
+   * refused by `A23_PHYSICS_CONSTRAINT_EFFECTIVE` (issue #1195).
+   */
   length?: number;
   /** Local to the parent. Default 0. Supplied by `from` when that is given. */
   x?: number;
@@ -1694,31 +1699,6 @@ export interface RigInvariants {
    * second kind, and names the issue.
    */
   deformMayFold?: RigDeformFoldExemption[];
-  /**
-   * Declare that this rig is authored to come back out of the **Spine editor** —
-   * imported, hand-edited, exported — and gate what that consumer cannot hold
-   * (`A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP`).
-   *
-   * 🔑 **Opt-in, because rigc's output is not wrong.** A physics constraint
-   * driving `rotate` is valid Spine 4.3 and every runtime plays it: a cowlick, a
-   * tail, an ear. What is true is that one consumer discards it — measured, not
-   * inferred (issue #540): the editor's physics model holds `x` and `y` only,
-   * with no cap on how many at once, and a lone `rotate`, `scaleX` or `shearX`
-   * comes back driving nothing at all. Refusing that by default would be rigc
-   * refusing correct data on behalf of a pipeline nobody told it about, which is
-   * the same silence pointed the other way. rigc knows what the object is; only
-   * the rig knows which consumers it is for.
-   *
-   * ⚠️ **Declaring nothing is not the same as being told nothing.** `A41` SKIPs
-   * on a rig that stays quiet — and the SKIP names the constraint and the
-   * component a round trip would drop, because the defect this field exists for
-   * is that nobody finds out. Declaring `true` turns that sentence into a
-   * refusal.
-   *
-   * Only `true` is accepted. A `false` here would be a key nothing reads (issue
-   * #545), and leaving it out says the same thing without the ambiguity.
-   */
-  editorRoundTrip?: boolean;
   /**
    * Ik and transform constraints whose mix **the consumer sets**, from code,
    * rather than any animation in this file — so `A47` / `A48` do not refuse
@@ -1882,7 +1862,7 @@ export const RIG_KEYS = {
   RigBoneFrom: ['anchor', 'slotWindow', 'meshCenter', 'rotation'],
   RigSlot: ['name', 'bone', 'attachment', 'color', 'dark', 'blend'],
   RigEvent: ['int', 'float', 'string', 'audio', 'volume', 'balance'],
-  RigInvariants: ['meshSlots', 'meshTriangles', 'axisBone', 'massBone', 'detached', 'deformMayFold', 'editorRoundTrip', 'consumerDrivenMix', 'idleDrivesMeshes'],
+  RigInvariants: ['meshSlots', 'meshTriangles', 'axisBone', 'massBone', 'detached', 'deformMayFold', 'consumerDrivenMix', 'idleDrivesMeshes'],
   RigIdleDrivesMeshes: ['why'],
   RigDetachedRule: ['bone', 'notUnder', 'why'],
   RigDeformFoldExemption: ['slot', 'why'],
@@ -1990,7 +1970,7 @@ export const RIG_TYPES = {
   RigEvent: { int: 'number', float: 'number', string: 'string', audio: 'string', volume: 'number', balance: 'number' },
   RigInvariants: {
     meshSlots: 'number', meshTriangles: 'number', axisBone: 'string', massBone: 'string', detached: 'object[]',
-    deformMayFold: 'object[]', editorRoundTrip: 'boolean', consumerDrivenMix: 'object[]', idleDrivesMeshes: 'object',
+    deformMayFold: 'object[]', consumerDrivenMix: 'object[]', idleDrivesMeshes: 'object',
   },
   RigIdleDrivesMeshes: { why: 'string' },
   RigDetachedRule: { bone: 'string', notUnder: 'string', why: 'string' },
@@ -2673,19 +2653,6 @@ export function parseRigSpec(raw: unknown, where: string): RigSpec {
     }
   }
 
-  // `invariants.editorRoundTrip` — the field that turns a check ON, so the only
-  // thing it can be wrong about is saying nothing while looking like it said
-  // something. `false` is refused for exactly that: it reads as a decision and
-  // behaves as an absence, which is the shape issue #545 closed elsewhere.
-  const roundTrip = spec.invariants?.editorRoundTrip;
-  if (roundTrip !== undefined && roundTrip !== true) {
-    throw new CompileError(
-      `${where}: invariants.editorRoundTrip is ${JSON.stringify(roundTrip)}; the only accepted value is \`true\`. ` +
-        'A rig that is not authored for the editor leaves the key out — A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP then ' +
-        'SKIPs and still names anything a round trip would drop, so nothing is lost by saying nothing',
-    );
-  }
-
   // A constraint's namespace is its KIND, not the array (issue #692).
   // `SkeletonData.findConstraint(name, type)` tests `constraint instanceof type`
   // BEFORE it compares the name, and every resolution in the format goes through

package/src/types.ts

@@ -1478,13 +1478,6 @@ export interface RigInfo {
    * is on.
    */
   deformMayFold: string[];
-  /**
-   * The rig declared `invariants.editorRoundTrip: true` — it is authored to come
-   * back out of the Spine editor, so `A41` gates what that consumer cannot hold.
-   * False is the ordinary case and is not a weaker gate: A41 then SKIPs, and the
-   * SKIP still names anything a round trip would drop.
-   */
-  editorRoundTrip: boolean;
   /**
    * Ik and transform constraints whose mix the consumer sets, from
    * `invariants.consumerDrivenMix`, in the rig spec's order. `A47` / `A48` do

package/src/validate.ts

@@ -120,7 +120,6 @@ import { a28RibbonRowsShareWeights } from './assertions/bodies/a28.ts';
 import { a33VertexAttachmentGeometry } from './assertions/bodies/a33.ts';
 import { a36PathConstraintEffective } from './assertions/bodies/a36.ts';
 import { a37SliderConstraintEffective } from './assertions/bodies/a37.ts';
-import { a41PhysicsSurvivesEditorRoundTrip } from './assertions/bodies/a41.ts';
 import { a42DrivenConstraintsUpdateAfterTheirDriver } from './assertions/bodies/a42.ts';
 import { a44LinkedMeshStatesNoGeometryOfItsOwn } from './assertions/bodies/a44.ts';
 import { a47IkConstraintNotMutedThroughout } from './assertions/bodies/a47.ts';
@@ -1615,6 +1614,7 @@ export function spineConstraintFacts(data: ReturnType<SkeletonJson['readSkeleton
         runtimeClass,
         physics: {
           bone: c.bone.name,
+          boneLength: c.bone.length,
           components: { x: c.x, y: c.y, rotate: c.rotate, scaleX: c.scaleX, shearX: c.shearX },
           setup: { mix: pose.mix, massInverse: pose.massInverse, strength: pose.strength, damping: pose.damping },
           step: c.step,
@@ -2798,7 +2798,7 @@ export function validate(input: ValidateInput): ValidateReport {
     // survey the two hand it held to one by `tools/survey_hashes.ts`.
     check('A39_DEFORM_KEEPS_TRIANGLE_WINDING', () => a39DeformKeepsTriangleWinding(verdicts, spineDeformSurvey(data), input.rig));
 
-    // --- A23, A41, A36, A37, A47, A48: a constraint that does nothing, quietly -
+    // --- A23, A36, A37, A47, A48: a constraint that does nothing, quietly -
     //
     // Their bodies, the reasoning each states and the one reading of "does an
     // animation switch this on" they share (`switchedOn`, which replaced the
@@ -2808,13 +2808,6 @@ export function validate(input: ValidateInput): ValidateReport {
     // `ConstraintFacts`, which `spineConstraintFacts` supplies here.
     check('A23_PHYSICS_CONSTRAINT_EFFECTIVE', () => a23PhysicsConstraintEffective(verdicts, constraintFacts(), loadedMeshFacts()));
 
-    // A41 — `validity` rather than policy, on A09's precedent: what it measures
-    // is the artifact against a claim the artifact's own spec makes, and a rig
-    // that makes no such claim has nothing to be measured against and SKIPs.
-    // Nothing here is one renderer's taste or one formation's shape, so there is
-    // no profile it should be hidden behind.
-    check('A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP', () => a41PhysicsSurvivesEditorRoundTrip(verdicts, constraintFacts(), input.rig));
-
     check('A36_PATH_CONSTRAINT_EFFECTIVE', () => a36PathConstraintEffective(verdicts, constraintFacts()));
 
     check('A37_SLIDER_CONSTRAINT_EFFECTIVE', () => a37SliderConstraintEffective(verdicts, constraintFacts()));

package/src/assertions/bodies/a41.ts

@@ -1,83 +0,0 @@
-/**
- * A41, the body (issue #1025, step 4c of #380): a physics component the Spine
- * editor cannot hold, refused on a rig declared for the editor.
- *
- * 🚨 The silence this converts is not in the artifact — it is one consumer
- * downstream of it. An author builds a rig whose cowlick jiggles, opens it
- * in the editor to move an eyebrow, saves, exports, and the hair has stopped
- * moving. The returned file says nothing: the component is simply absent,
- * and absent parses as 0. `gallery/look` is exactly that rig.
- *
- * 🔑 **rigc's output is correct, so the refusal is opt-in.** `rotate` on a
- * physics constraint is valid Spine 4.3 that every runtime plays, and
- * refusing it by default would be refusing correct data on behalf of a
- * pipeline rigc was never told about. What rigc can see is the object; which
- * consumers it is for is the rig's to say, and it says it with
- * `invariants.editorRoundTrip` (`src/rig.ts`).
- *
- * ⚠️ **The SKIP is the other half of the product and is not a shrug.** A rig
- * that declares nothing is not gated — but the reason names the constraint
- * and the components a round trip would drop, so the one thing that must not
- * happen (nobody finds out) does not happen either. That is why this reads
- * the whole skeleton before it reads the declaration, rather than returning
- * early on a rig that asked for nothing.
- *
- * 🔸 **Against A23, on the far side of the same trip.** A23 refuses a
- * constraint driving NOTHING — which is what the editor hands back, after
- * the loss — and it is what fires today on a round-tripped `look`. This
- * refuses a constraint driving something the editor will not keep, before
- * the trip. They cannot both fire on one constraint: A23's condition is an
- * empty driven set and this one's is a non-empty one (see
- * `PHYSICS_COMPONENTS`), so the two are disjoint by construction rather than
- * by agreement.
- *
- * Moved out of `src/validate.ts` whole: the components are the document's
- * physics records, the declaration the rig's.
- */
-import type { Verdicts } from '../harness.ts';
-import type { ConstraintFacts } from '../facts/constraints.ts';
-import { EDITOR_PHYSICS_COMPONENTS, PHYSICS_COMPONENTS } from '../constraint_words.ts';
-import type { RigInfo } from '../../types.ts';
-
-export function a41PhysicsSurvivesEditorRoundTrip({ fail, skip }: Verdicts, facts: ConstraintFacts, rig: RigInfo | undefined): void {
-  // Counted here rather than read off `stats.physicsConstraints`: that entry
-  // is written by A23, and a rule whose SKIP depends on another rule having
-  // run is a rule that reports "nothing to measure" when its neighbour threw.
-  const physics = facts.constraints.flatMap((c) => (c.physics === undefined ? [] : [{ name: c.name, components: c.physics.components }]));
-  const dropped: string[] = [];
-  for (const constraint of physics) {
-    const lost = PHYSICS_COMPONENTS.filter((k) => constraint.components[k] > 0 && !EDITOR_PHYSICS_COMPONENTS.has(k));
-    if (lost.length) dropped.push(`physics "${constraint.name}" drives ${lost.join(', ')}`);
-  }
-  const editorKeeps = [...EDITOR_PHYSICS_COMPONENTS].join(' and ');
-  const found =
-    dropped.length === 0
-      ? 'no physics constraint here drives a component it would discard'
-      : `${dropped.join('; ')}, and the editor's physics model holds ${editorKeeps} only, so a round trip ` +
-        'returns that constraint driving nothing at all (issue #540)';
-  if (rig?.editorRoundTrip !== true) {
-    return skip(
-      'A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP',
-      `${
-        rig
-          ? `the rig "${rig.archetype}" does not declare \`invariants.editorRoundTrip\``
-          : 'this is a bare directory, with no rig info to declare `invariants.editorRoundTrip`'
-      }, so nothing here is gated against the Spine editor. What is here: ${found}`,
-    );
-  }
-  if (physics.length === 0) {
-    return skip(
-      'A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP',
-      `the rig "${rig.archetype}" is declared for the editor, but it carries no physics constraint — ` +
-        'there is nothing here whose components could be lost',
-    );
-  }
-  for (const one of dropped) {
-    fail(
-      'A41_PHYSICS_SURVIVES_EDITOR_ROUND_TRIP',
-      `${one}; the editor's physics model holds ${editorKeeps} only, and this ` +
-        'rig declares `invariants.editorRoundTrip` — drive it in x/y, or drop the declaration if this rig never ' +
-        'goes through the editor (issue #540)',
-    );
-  }
-}