spine-rigc 0.36.1 → 1.0.1

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
@@ -686,7 +670,8 @@ letting `A17` blame the editor for the harness's own doing.
 | 🔬 **[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 |
 | 🎓 **[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 |
-| 🗺️ [ROADMAP.md](https://github.com/firejune/rigc/blob/main/ROADMAP.md) | where this is going, and where it has been. What 1.0 has to mean before the number is claimed — conditions rather than a feature list, because direction here comes from what users hit |
+| 🧬 [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 |
 
 ## Why you can trust the output

package/docs/AUTHORING.md

@@ -727,6 +727,8 @@ is a `BLOCK GENERATION_UNKNOWN`, never rounded to the nearest: a catalog that ro
 handed 19 skeletons labelled `3.8.99` a 4.2 runtime and every one of them posed as NaN
 (row 7). Reading a file with *that generation's own* defaults is #706's item 2 and is
 not in this tool — re-export as 4.3, or transcribe by hand ([INGEST.md](INGEST.md) §2).
+[GENERATIONS.md](https://github.com/firejune/rigc/blob/main/docs/GENERATIONS.md) is
+the whole policy, and the editor migration it names.
 
 📝 **Do not delete the `note`.** Both written specs carry one saying the file is
 decompiled and naming the skeleton it came from. A decompiled spec is

package/docs/INGEST.md

@@ -674,6 +674,11 @@ before it was a hand-edit of emitted JSON with nothing checking it. That is now
 `ingest` hands you in one command; the sections below are how to read and change what
 it hands you, and every rule in them applies to a spec `ingest` wrote.
 
+A file from another Spine generation is the one case where transcription is not the
+first fallback: migrate it through the editor of its own generation first, as
+[GENERATIONS.md](https://github.com/firejune/rigc/blob/main/docs/GENERATIONS.md) §4
+states.
+
 📌 **The cost this section used to warn about is measured, and it is why §5 changed.**
 The smallest skeleton of the corpus behind [#569](https://github.com/firejune/rigc/issues/569)
 transcribed to a **257,422-byte** rig spec, of which 91.8 % is the six geometry

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spine-rigc",
-  "version": "0.36.1",
+  "version": "1.0.1",
   "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": {