spine-rigc 1.0.0 → 1.0.2

package/README.md

@@ -56,22 +56,6 @@ it cuts both ways:
   trusted at all. So the [Spine Runtimes License Agreement](https://esotericsoftware.com/spine-runtimes-license)
   applies to rigc exactly as it applies to any other runtime integration.
 
-🗓️ **One sentence left this section on 2026-09-05, and its removal is a decision
-rather than a tidy-up.** It read *"rigc is complementary to the editor. It is not
-a replacement for it, and it is not a way around one."* That was a claim about
-what rigc would never become, and
-[#380](https://github.com/firejune/rigc/issues/380) — a format-agnostic core with
-its own format and web player, Spine kept as one backend among others — is a
-course the claim cannot survive. A promise the roadmap contradicts is worth less
-than no promise, so it is retired rather than reworded
-([#398](https://github.com/firejune/rigc/issues/398)). What a reader can check is
-unchanged: rigc emits Spine skeleton data, links `spine-core`, validates through
-it with no flag that turns that off, and carries the licence obligation the next
-section states in full. A backend emitting something other than Spine data would
-have no spine-core to check it against, and #380 treats an oracle of its own as
-the prerequisite for shipping one — nothing here makes an unchecked emit path
-acceptable.
-
 ### Licensing, stated plainly
 
 rigc's own code is MIT (see [LICENSE](LICENSE)). That says nothing about Spine, and
@@ -494,8 +478,8 @@ the shot: both silhouette edges move apart, which a flat slide cannot do, becaus
 feature carries its own depth. The rig guarantees the seams — <code>idle</code> loops
 while <code>gaze</code> and <code>turn</code> return to rest, so the hand-offs meet at 0
 differing pixels — and the composing is the consumer's. Authorable on plain Spine 4.3, no
-plugin, no runtime patch; the split was authoring cost rather than runtime capability, and
-the cost is now one stated expression per key. Compiled and rendered entirely by the
+plugin, no runtime patch; what the turn costs is authoring rather than runtime capability,
+and that cost is one stated expression per key. Compiled and rendered entirely by the
 published package.</em></p>
 
 🎞️ **How the three films on this page were made** is kept with them, one directory per
@@ -569,20 +553,20 @@ holds no art — every rebuild then has to repeat `build --images parts/`.
 
 **`build(ingest(x))` is `x`.** Over the eleven rigs this repository builds — the seven
 gallery examples, the three generated probes and a coverage probe written for the
-purpose — the rebuilt `skeleton.json` is byte for byte the file the decompiler read,
-and `bun run selftest` holds it there on every run. The atlas is held to a weaker
+purpose — the rebuilt `skeleton.json` is byte for byte the file the decompiler read.
+The atlas is held to a weaker
 claim on purpose, and the weakening is measured rather than assumed: it comes back
 equal as a **multiset of region blocks**, because the order the pages are collected in
 is in no field of the skeleton.
 
-**And over twelve skeletons nobody here wrote.** The same run ingests every editor
-export in the fetched example corpus, rebuilds it through the pack beside it and
-`diff`s the result against the source: **12 of 12, no blockers, 1.000 on every measure
-the report carries** — and each rebuild is its export's own text in canonical form,
-apart from the header's `hash` and `spine`: the editor's project hash and the runtime
-version rigc stamps, the two keys the rig spec has no field for by design (`IG83`,
-12 of 12). [INGEST.md §2.3](docs/INGEST.md) states that pass line and why those two
-are the exceptions.
+**And over twelve skeletons nobody here wrote.** Every editor export in the fetched
+example corpus, ingested, rebuilt through the pack beside it and `diff`ed against the
+source, comes back **12 of 12, no blockers, 1.000 on every measure the report
+carries** — and each rebuild is its export's own text in canonical form, apart from
+the header's `hash` and `spine`: the editor's project hash and the runtime version
+rigc stamps, the two keys the rig spec has no field for by design (12 of 12).
+[INGEST.md §2.3](docs/INGEST.md) states that pass line and why those two are the
+exceptions.
 
 **What it reads is skeleton JSON and nothing else** — no `.spine` project, no binary
 `.skel`, no atlas, no art. So it never invents, and the things it cannot get out of
@@ -595,16 +579,13 @@ specs are still written — a spec plus a list of what is missing from it beats
 
 - **The stage.** `skeleton.width`/`height`. A skeleton that declares none is carried as
   declaring none — the rig spec states `"width": null, "height": null` and the rebuild
-  carries no box either, byte for byte
-  ([#714](https://github.com/firejune/rigc/issues/714)) — and `--stage x,y,w,h` is how a
+  carries no box either, byte for byte — and `--stage x,y,w,h` is how a
   caller *adds* one, recorded as a judgement. It is not derivable — posing the rig gives
   the *animated* extent, which is a different number from the setup box. ⛔ **And `--stage` beside a box the file already states is refused
   too**, for the opposite reason: two sources for one value, where the file is the record
-  of what was measured. It used to be read after the box and therefore never
-  ([#626](https://github.com/firejune/rigc/issues/626)). ⚠️ This said *"an editor export carries none"* until #594 measured
-  it: **all twelve exports in the example corpus carry a stage** and none of them needs
-  the flag. It is still the value that costs least to get wrong, because `diff` reports
-  the box and gates nothing on it.
+  of what was measured. **All twelve exports in the example corpus carry a stage** and
+  none of them needs the flag. It is the value that costs least to get wrong, because
+  `diff` reports the box and gates nothing on it.
 - **An animation's duration.** The format has no such field. The largest key time is
   the only derivable answer and it is what a runtime plays to; it is wrong for an
   animation that holds its last pose past its last key, so it is recorded as a finding
@@ -636,17 +617,14 @@ render-and-check block per skin, with a per-skin roll-up under them, because a
 rig's contested art lives in its named skins and a single un-skinned check draws
 none of it; a skin only one side declares is a FAIL naming it as **lost** (or
 **added**) **by the export**, with `diff`'s `attachments.skins` beside it, and is
-rendered on neither side ([#801](https://github.com/firejune/rigc/issues/801)) — and a
+rendered on neither side — and a
 field-by-field list of what the editor rewrote. Every step quotes what its child
 said when that child did not do what it was for, the renderers included; a skin
 **neither** side can draw — a hit-box rig, say — is a **SKIP** naming that, not a
 red, because `check` had nothing to compare and `diff` and `validate` have
 already measured the rig. One side drawing where the other does not is the
-divergence the trip exists to find and stays a failure. On its first
-run it found three emitter defects — [#368](https://github.com/firejune/rigc/issues/368),
-[#369](https://github.com/firejune/rigc/issues/369),
-[#370](https://github.com/firejune/rigc/issues/370) — and then showed that a
-human edit made in the editor survives the trip back.
+divergence the trip exists to find and stays a failure. A human edit made in the
+editor survives the trip back.
 
 🔒 **It requires a licensed Spine editor on the machine, by construction**, and
 drives only the [documented command line](https://esotericsoftware.com/spine-command-line-interface)
@@ -659,14 +637,8 @@ and failing downstream. Both refusals point at `--exported <file>`, which
 measures an export the editor already made and is the half of this tool that
 needs no editor at all.
 
-⛔ **The round trip is not, and must not become, a selftest control.** `bun run
-selftest` is self-contained and CI has no editor; a control that needed one would
-report SKIP for ever, which is how a gate comes to look kept while checking
-nothing. Run the round trip by hand, on a machine that has the editor. Its
-**refusals** are gated, because they are the half a machine with no editor can
-answer for: the suite points the tool at stubs in a temp directory and reads what
-comes back, including the case that must *not* be refused — an editor at an
-unfamiliar path, which is who `--editor` exists for.
+⛔ **Run the round trip by hand, on a machine that has the editor.** CI has no
+editor, so no automated check runs it.
 
 ⚠️ Build with `--copy-images`. An ordinary build's atlas names its pages by a
 relative path back to the art directory, and the round trip copies that atlas to
@@ -683,9 +655,11 @@ letting `A17` blame the editor for the harness's own doing.
 | 🙂 **[docs/FACE.md](docs/FACE.md)** | **authoring a face.** A blink, a gaze and a 2.5D head turn on plain Spine data: the one line of yaw arithmetic every number in a turn comes from, depth as the parameter you are actually authoring, where to put a grid's columns and the angle at which any grid folds, what foreshortens and what does not, channel allocation before the first key, and the three cliffs with their angles. Also the deform audit gap, demonstrated — a folded mesh gates green — and the differential check that works today |
 | 📥 **[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)** | Spine 4.3's full export surface against what rigc emits and what the official examples measurably use, with the ordered gap list |
+| 🔬 **[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 49 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 |
 | 🗺️ [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 |
 
@@ -695,7 +669,7 @@ rigc is measured against **Spine's own official example projects** — the
 `1-weight-and-mass` … `8-follow-through` series as a difficulty ladder, with spineboy
 as the graduation exam.
 
-🎓 **The ladder is complete, 2026-08-28.** All eight numbered rungs and the
+🎓 **The ladder is complete.** All eight numbered rungs and the
 spineboy graduation exam are cleared and hold under the current gate, **v2.4**, every clause PASS or SKIP:
 worst attributable slot drift **5.5550 px** against a 6.0 px bar — a **1.0801×**
 margin, the thinnest of the ladder's **G2** figures, and **G5**'s 1.0376× is thinner
@@ -703,24 +677,15 @@ still — and **0 of 124** frame-change disagreements. Recompiling the same spec
 different session reproduced every field of the measurement record **to the digit**.
 The rungs stay in place as regression gates.
 
-🗓️ **One rung's pass was withdrawn and restored on 2026-09-02, and both are dated
-facts.** `check`'s extent tolerance ([PR #254](https://github.com/firejune/rigc/pull/254))
-changed which box a set is measured in, and rung 7's stored candidate failed **G2**
-under it — one of its three slots draws in every set and is attributable in none,
-and no read-down ground survived the framing change. The gate then answered the two
-clause questions that exposed, as **v2.3**: a read-down names the framing of its
-evidence, and a slot whose attributability is **measured** to be capped below the bar
-reads down when everything observable about it is independently verified strict. That
-rung's third attempt clears on those grounds, on the candidate it already had.
-**Rungs 1–6 and 8 and the graduation exam were unaffected throughout**: each keeps its
-pass on the clause, and recompiling a stored candidate reproduces its record **to the
-digit within one gate**. Across an instrument change the digits do move, and the
-record says where — the graduation **G2** figure went 5.5491 → 5.5544 → **5.5550 px**
-over the #301 sampler repair and v2.4's adoption of the re-rendered reference basis,
-while **0 of 124** held throughout. Both verdicts, and the sweep of every candidate under the gate of the day, are in
-[docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md)'s *PR #254 instrument re-inspection* and *gate-v2.3
-re-inspection*; the standing figures quoted above are from its *gate-v2.4
-re-inspection*, which is the current sweep.
+**Rung 7 clears on a read-down.** One of its three slots draws in every set and is
+attributable in none; a read-down names the framing of its evidence, and a slot whose
+attributability is **measured** to be capped below the bar reads down when everything
+observable about it is independently verified strict. Every other rung and the
+graduation exam pass on the clause itself. Recompiling a stored candidate reproduces its
+record **to the digit within one gate**; across an instrument change the digits move,
+and [docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) records
+where. The standing figures quoted above are from its *gate-v2.4 re-inspection*, which
+is the current sweep.
 
 ⚠️ **What that certifies, stated exactly.** That **the tool, the guide and the
 protocol reach the bar across a bounded series of honest attempts, each residual
@@ -732,8 +697,7 @@ ladder has not demonstrated that, and each row records which of the two it is.
 🧪 **A separate series measures that harder question, and it has not been kind.**
 From-zero attempts at spineboy — no inherited specs — have landed at **18.2, 18.8,
 19.57, 7.86, 9.33 and 18.98 px** worst drift against the 6.0 px bar, a spread with no
-monotone trend, and the two most recent — both **2026-09-03**, after the ladder's
-2026-08-28 completion — are recorded 🔴 **FAIL**. They move no rung and reopen nothing —
+monotone trend and every figure above the bar. They move no rung and reopen nothing —
 a from-zero run is a tooling-progress measurement rather than a re-climb, which is
 why the certification above is scoped to tool + guide + protocol. One of those
 attempts states the residual in its own words: *"in motion it is not at editor