spine-rigc 1.2.1 → 1.2.2

package/README.md

@@ -692,6 +692,7 @@ letting `A17` blame the editor for the harness's own doing.
 | 📋 [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 |
+| 📓 [CASES.md](https://github.com/firejune/rigc/blob/main/docs/CASES.md) | **converting a Live2D model to Spine, and verifying the conversion.** The method — the source's own player headless, parts from its texture along the drawables, motion baked as deform keys, reference frames first, `check` — run once end to end on two Live2D sample models with no editor and no converter, and verified against the source's renderer and Spine's own runtime: the three instruments, the two rigc defects verifying it led to and v1.2.1 fixed, and where the method stops. Figures only — the models' licence keeps every asset out. Repository material |
 | 🗺️ [ROADMAP.md](https://github.com/firejune/rigc/blob/main/ROADMAP.md) | where this is going, and where it has been. What 1.0 had to mean before the number was claimed, and what it was claimed on — conditions rather than a feature list, because direction here comes from what users hit |
 | 📐 [CLAUDE.md](https://github.com/firejune/rigc/blob/main/CLAUDE.md) | **the doctrine** — why the validator's messages are the product, why nothing reaches disk before green, why no number is ever invented, and what a change has to keep. [CONTRIBUTING.md](https://github.com/firejune/rigc/blob/main/CONTRIBUTING.md) calls it worth ten minutes before a first patch. Repository material |
 

package/docs/AUTHORING.md

@@ -141,7 +141,12 @@ result. There is no `--no-validate`, and there will not be one.
 Green from `build` means the file is valid; it says nothing at all about whether
 the animation is the one in the frames, and there is no assertion that could — see
 §9. The two run in that order because `check` needs artifacts on disk and `build`
-only writes them when the gate is green.
+only writes them when the gate is green. Read its report from the top, because the
+framing block says whether the figures under it are about placement or motion
+(§9.2, *Read the framing block first*), and read a figure as where the loop starts,
+not where it ends: keep the first green build's figure, check every later build
+against the same frames, and stop when the figure stops moving rather than when it
+exists — against a floor measured the way §9.2 says.
 
 🎞️ **When the source is a foreign player — a Live2D model, a Unity scene, a video —
 make the reference frames first, from the source.** rigc reads none of those
@@ -166,6 +171,11 @@ is valid and nothing about whether it is the source's picture. And the parts are
 the source's own texture cut along its drawables, **never a screenshot of it** — a
 screenshot is the composed result, so a part cut from it carries every part under
 it, which is what the first of the three questions under *LOOK* below finds.
+Where a part goes is the drawable's own geometry — its vertices in model space, its
+UVs and its triangles — which is a mesh attachment with those three (§3.4, *Mesh
+attachment*, where `uvs` are fractions of the region you cut rather than of the
+source's page); a region at the drawable's bounding-box centre keeps only the box,
+so no vertex the source moves has anywhere to go.
 
 🚨 **Read `check`'s per-frame column before its MAE.** The table's headline figures
 are the MAE and the slot drift, and a reader who came for those will skip the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spine-rigc",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "Rig compiler for Spine — declarative rig specs in, Spine 4.3 skeleton data out, verified by a spine-core round-trip. Built so AI agents can author rigs and check their own work; the output imports into the Spine editor.",
   "type": "module",
   "bin": {

package/skills/rigc/SKILL.md

@@ -62,7 +62,12 @@ skill the package ships there, and `rigc skills --help` says what it refuses.
    `--slot <slot,…>`), which draws the frame again without that part on the same
    grid, so the two frames say which part a pixel is. AUTHORING §0 holds the three.
 5. `rigc check --candidate <out> --frames <dir>` when you have reference pictures
-   (`--out <dir>` writes the picture each of its numbers came from — open the worst);
+   (`--out <dir>` writes the picture each of its numbers came from — open the worst).
+   Read its output from the top: the framing block says whether the figures under
+   it are about placement or motion. A figure is where the loop starts, not where it
+   ends — keep the first green build's figure, check every later build against the
+   same frames, and stop when the figure stops moving, not when it exists; AUTHORING
+   §9.2 says how to read the framing block and the floor to read a figure against.
    `rigc vote --candidate <a> --candidate <b>` when several candidates are green and
    only a person can choose between them.
 6. `rigc validate <out>` re-gates artifacts already on disk, and
@@ -81,7 +86,10 @@ directory of `f0000.png`, `f0001.png`…, and `rigc check --frames <that dir> --
 reads them with no `frames.json`. A port with no reference frames is unmeasured,
 not finished. The parts are the source's own texture cut along its drawables, never
 a screenshot: a screenshot is the composed result, and a part cut from it carries
-every part under it. rigc reads none of those formats — FACE §11, the paragraph
+every part under it. Where a part goes is its drawable's geometry — its vertices in
+model space, its UVs, its triangles — which is a mesh attachment with those three
+(AUTHORING §3.4, *Mesh attachment*); a region at the drawable's bounding-box centre
+keeps only the box. rigc reads none of those formats — FACE §11, the paragraph
 that opens *No Live2D file is read or written*
 ([FACE.md](https://github.com/firejune/rigc/blob/main/docs/FACE.md#11-non-goals--stated-so-nobody-proposes-them-as-gaps)) —
 only the pictures they produce. The rule, the background those frames need and