@rig-c/core 2.86.0 → 3.0.1

package/README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="https://raw.githubusercontent.com/rig-c/core/main/assets/banner.svg" alt="rigc — AI-authored 2D rigging and animation, verified before it is written" width="100%" />
+  <img src="https://raw.githubusercontent.com/rig-c/core/main/assets/banner.svg" alt="@rig-c/core — AI-authored 2D rigging and animation, verified before it is written" width="100%" />
 </p>
 
 <p align="center">
@@ -8,6 +8,8 @@
   <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-38BDF8.svg?style=flat-square" alt="license" /></a>
 </p>
 
+# @rig-c/core
+
 **AI-authored 2D rigging and animation, verified before it is written.** rigc is
 a rig compiler: a rig spec and a motion spec in, skeleton data out — in the Spine 4.3
 format, with rigc's own compiled model beside it —

package/docs/AUTHORING.md

@@ -367,7 +367,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 36 validity rules (**the default**) · `rig-play` = all 50, opt-in. `spine-html`, the profile's former name, is read as `rig-play` until the next major release and prints `rigc: --profile spine-html is deprecated and reads as --profile rig-play, the same rules; it is accepted until the next major release — pass --profile rig-play` on stderr |
+| `--profile` | `spine` = the 36 validity rules (**the default**) · `rig-play` = all 50, opt-in. Since 3.0, `spine-html` is refused with `--profile "spine-html"; known profiles: spine, rig-play` (usage error, exit 2); replace it with `--profile rig-play`, which runs the same rules |
 | `--report` | `build` and `repack`: also write the gate's report as a JSON document (`build-report/1`) to this file — every gate's `PASS`, `SKIP` and `FAIL` rows, its summary figures and stats line, which supplier judged it, and every `pack:` line's figures. Written when the command writes `--out` and when a gate is red, before the exit; a file already at the path is removed first, so a compile error or a refused repack leaves none. Never inside `--out`, refused by name. The printed lines are byte-identical with it and without it — **§5.3** |
 | `--candidate` | `check`, `bench`, `render`, `inspect`, `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 |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rig-c/core",
-  "version": "2.86.0",
+  "version": "3.0.1",
   "description": "AI-authored 2D rigging and animation, verified before it is written. rigc compiles a rig spec into skeleton data in the Spine 4.3 format, gates it with named assertions held to a spine-core round trip's verdicts, and emits nothing that fails. Ships as an agent skill.",
   "type": "module",
   "bin": {
@@ -22,15 +22,18 @@
     "./runtime": "./src/runtime/index.ts",
     "./cli": "./cli.ts",
     "./package.json": "./package.json",
-    "./*.ts": "./*.ts",
-    "./*.mjs": "./*.mjs",
-    "./*.cjs": "./*.cjs",
-    "./*.json": "./*.json",
-    "./*.md": "./*.md",
     "./LICENSE": "./LICENSE",
     "./bin/rigc": "./bin/rigc.cjs",
     "./tools/png_probe": "./tools/png_probe.mjs",
-    "./*": "./*.ts"
+    "./deformgen": "./src/deformgen.ts",
+    "./environment": "./src/environment.ts",
+    "./motion": "./src/motion.ts",
+    "./passthrough": "./src/passthrough.ts",
+    "./stop": "./src/stop.ts",
+    "./meshrasters": "./src/meshrasters.ts",
+    "./seam": "./src/seam.ts",
+    "./folds": "./src/folds.ts",
+    "./model": "./src/model.ts"
   },
   "engines": {
     "bun": ">=1.4.0"

package/skills/rigc/SKILL.md

@@ -28,7 +28,7 @@ index within that same limit; only legacy uncoded library errors point at `§5.1
 ## Non-negotiables
 
 - **Validation is never bypassed.** `build` writes nothing on a red gate; there is
-  no `--no-validate`, and none may be added — AUTHORING §0 says so in as many
+  no flag to skip it, and none may be added — AUTHORING §0 says so in as many
   words. Correctness is the whole of the reason: the assertions are what make the
   output trustworthy, and they are held to the official parser's verdicts in the
   repository's CI — all but the parse itself, which runs only where the runtime is
@@ -55,20 +55,23 @@ Codex, Gemini CLI and Antigravity read skills from `.agents/skills/` in the
 workspace and none of them reads `node_modules`; `rigc skills install` puts every
 skill the package ships there, and `rigc skills --help` says what it refuses.
 
-The package links no Spine runtime. `validate`, `preview` and `vote` below run
-through `@esotericsoftware/spine-core`: install it beside the package
-(`bun add -d @esotericsoftware/spine-core`) and the same `rigc` runs them, and
-`build` runs the round trip as well. Without it they are refused by name, and
-`build` writes the same files gated without the parse — `rigc --version` names the
-entry that ran. In the parse's place that `build` runs two rules of its own over
-rigc's model document, `A00_MODEL_READ` and `A00_MODEL_REGIONS_ON_PAGES`; they are
-not registry assertions, so its summary counts two more, and AUTHORING §5.2 has a
-row for each.
+The package links no Spine runtime. `build` writes `skeleton.json`,
+`skeleton.atlas` and `skeleton.model.json`. `preview`, `vote`, `bench` and `bonedist`
+run through `@esotericsoftware/spine-core`: install it beside
+the package (`bun add -d @esotericsoftware/spine-core`) and the same `rigc` runs
+them, and `build` runs the round trip as well. Without it those commands are refused
+by name, while `build`, `validate`, `explain`, `diff`, `render`, `check` and `inspect`
+(`--poser core|spine`) run on rigc's own core over `skeleton.model.json` —
+`rigc --version` names the entry that ran (AUTHORING §0). In the parse's place that
+`build` runs two rules of its own over rigc's model document, `A00_MODEL_READ` and
+`A00_MODEL_REGIONS_ON_PAGES`; they are not registry assertions, so its summary
+counts two more, and AUTHORING §5.2 has a row for each.
 
 ## The loop
 
 1. `rigc build --rig <spec> --motion <spec> --images <dir> --out <dir>` compiles,
-   gates, and writes only on green.
+   gates (under `--profile spine`, the default, or `--profile rig-play`), and writes
+   `skeleton.json`, `skeleton.atlas` and `skeleton.model.json` only on green.
 2. Read the report. Every red line names the file to change; fix the spec and
    build again.
 3. `rigc explain --rig <spec> --motion <spec> --out <dir>` when the red line is
@@ -85,11 +88,17 @@ row for each.
    cover a feature the art shows — and answer each with `render --hide <slot>` (or
    `--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.
-   When the question is geometry — is this bone where the art is, which way does it
-   squash, where in rig units is this point — `rigc inspect --candidate <out> --show
-   art,bones,names --dim` draws the bones over the art and writes a legend beside the
-   picture that puts every mark back in world units; AUTHORING §13 maps each
-   question to its view.
+   For motion and dial readings, `render --pass-through <cloth>:<leg>` names the
+   frames where a cloth drawn over a leg passes through it (AUTHORING §8.5),
+   `render --angle-range <bone>:<relative-to>` prints how far a bone turns against
+   another (AUTHORING §8.7), `render --seam <slot>:<slot>` reads joint gaps,
+   visible ghosts and background exposure (AUTHORING §8.8), and
+   `render --parallax <dial>` reads a slider dial across its value grid
+   (AUTHORING §8.12). When the question is geometry — is this bone where the art is,
+   which way does it squash, where in rig units is this point —
+   `rigc inspect --candidate <out> --show art,bones,names --dim` draws the bones
+   over the art and writes a legend beside the picture that puts every mark back in
+   world units; AUTHORING §13 maps each question to its view.
 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).
    Read its output from the top: the framing block says whether the figures under
@@ -100,17 +109,21 @@ row for each.
    `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
-   `rigc <command> --help` is each command's own flag table. `rigc repack <out>
-   --out <dir>` packs a build again under `build --pack`'s packing flags when its
-   parts were not kept, and writes only after every region and the skeleton are
-   shown unchanged (`--accept-skeleton-differences` writes a rebuild whose skeleton
-   differs, every difference printed; `--stage-box <slot>` reads a build's stage box)
-   — AUTHORING §0.4. A mesh refused because its triangles are several pieces that
-   share no vertex: `rigc split --rig … --motion … --slot <slot> --out <dir>` writes
-   both specs back with one mesh per piece and every deform key renumbered — build
-   that — AUTHORING §3.4.11.
-7. Every finished unit ends with `rigc preview --candidate <out>`, and the report
-   names the `.html` it wrote. The hand-off to a person is part of the work.
+   `rigc <command> --help` is each command's own flag table.
+   `rigc repack <out> --out <dir>` packs a build again under `build --pack`'s
+   packing flags when its parts were not kept, and writes only after every region and
+   the skeleton are shown unchanged (`--keep-pages` refreshes `skeleton.model.json`
+   over the existing atlas pages; `--accept-skeleton-differences` writes a rebuild
+   whose skeleton differs, every difference printed; `--stage-box <slot>` reads a
+   build's stage box) — AUTHORING §0.4. A mesh refused because its triangles are
+   several pieces that share no vertex: `rigc split --rig … --motion … --slot <slot> --out <dir>`
+   writes both specs back with one mesh per piece and every deform key renumbered —
+   build that — AUTHORING §3.4.11.
+7. Every finished unit ends with `rigc preview --candidate <out>` (or
+   `rigc review <out>` when `@rig-c/review` is installed beside the project and a
+   person reviews the build via its loopback URL, AUTHORING §0), and the report
+   names the `.html` or URL it produced. The hand-off to a person is part of the
+   work.
 
 The loop in full, with `pose` before it and `chainfit` after the first build:
 AUTHORING §0.
@@ -141,7 +154,7 @@ spec files field by field, the emission rules, the loop, and the failure map. Th
 | --- | --- | --- |
 | a **skeleton** — how many bones, where each pivot sits, what hangs off what | [RIGGING.md](https://github.com/rig-c/core/blob/main/docs/RIGGING.md) | `rigc-rigging` |
 | a **movement** — an idle, a loop, from this pose to that one | [MOTION.md](https://github.com/rig-c/core/blob/main/docs/MOTION.md) | `rigc-motion` |
-| a **face** — a blink, a gaze, a head turn a few degrees off axis | [FACE.md](https://github.com/rig-c/core/blob/main/docs/FACE.md) | `rigc-face` |
+| a **face** — a blink, a gaze, a head turn or a value-driven face dial | [FACE.md](https://github.com/rig-c/core/blob/main/docs/FACE.md) | `rigc-face` |
 | a **skeleton.json somebody else authored** — read it, repair it, extend it | [INGEST.md](https://github.com/rig-c/core/blob/main/docs/INGEST.md) | `rigc-ingest` |
 | you are the **person operating** the agent rather than the agent | [PROMPTING.md](https://github.com/rig-c/core/blob/main/docs/PROMPTING.md) | — |
 

package/skills/rigc-face/SKILL.md

@@ -1,16 +1,17 @@
 ---
 name: rigc-face
-description: Author a face on plain Spine data with rigc — a blink, a gaze shift, a breathing portrait and a head turn a few degrees off axis, built from deform timelines and per-part parallax. Use when the request is a talking or living portrait, a standing character, an expression or a head turn, such as "rig this face", "make the portrait blink and look around" or "turn the head". Not for Live2D file conversion, cutting a face illustration into parts, or VTuber-style real-time face tracking.
+description: Author a face on plain Spine data with rigc — a blink, a gaze shift, a breathing portrait, a head turn (from a flat sheet a few degrees off axis or a per-vertex depth map across its turn ceiling) and slider-driven face dials, built from closed-form deform transforms, derived group tracks, per-part parallax and socket alpha clipping. Use when the request is a talking or living portrait, a standing character, an expression, a head turn or a look dial, such as "rig this face", "make the portrait blink and look around" or "turn the head". Not for Live2D file conversion, cutting a face illustration into parts, or VTuber-style real-time face tracking.
 license: MIT
 compatibility: Requires Bun 1.4 or later and the npm package @rig-c/core (rig-c is the convenience name).
 ---
 
-# Face — a turn, a gaze and a blink
+# Face — a turn, a gaze, a blink and a dial
 
 Load this when the request is a **head rather than a body**: a drawn face that
-breathes, blinks, moves its eyes and turns a few degrees off axis. Every rule below
-is owned by [FACE.md](https://github.com/rig-c/core/blob/main/docs/FACE.md); this file says when to open it and what
-it will not do for you.
+breathes, blinks, moves its eyes, turns off axis (on a flat sheet or a per-vertex
+`depth` map) or exposes its turn as a slider-driven dial. Every rule below is owned
+by [FACE.md](https://github.com/rig-c/core/blob/main/docs/FACE.md); this file says when to open it and what it will
+not do for you.
 
 📖 **A failure line ends with the command that prints its row of the guide** —
 ` (see rigc guide <RULE>)`. Run that command first, before reading anything else:
@@ -27,9 +28,22 @@ index within that same limit; only legacy uncoded library errors point at `§5.1
 
 - **Validation is never bypassed.** `build` writes nothing on a red gate, and there
   is no flag that changes that — AUTHORING §0.
-- **The compiler never invents a value.** A `deform` key states every vertex it
-  moves; the geometry a turn implies is evaluated by you and written into the spec,
-  never inferred by the compiler — AUTHORING §4 and FACE §1.
+- **The compiler never invents a value.** A `deform` key states either explicit
+  vertex deltas or `transform` (`yaw`/`pitch` with `radius` and `degrees`, or over
+  the mesh's per-vertex `depth` sheet, AUTHORING §3.4.5 and FACE §2.1, §2.2), and a
+  bone group track states `derive` (`depth` per member, `carried` shared shift); the
+  compiler evaluates the closed form from the parameters you declare and never
+  guesses a radius, angle or depth — AUTHORING §4, §4.5.1, §4.11.1 and FACE §1,
+  §1.1, §3.1.
+- **A face angle exposed as a dial is a slider constraint, not a playback time.**
+  Map a control bone across `[−1, +1]` onto the turn animation with a slider
+  (AUTHORING §3.5.2, FACE §8), bound its degrees by the turn ceiling `build` and
+  `explain` print for the depth sheet (FACE §2.2), set `additive: true` when yaw and
+  pitch dials share a target (`A40_SLIDERS_COMPOSE_ON_A_SHARED_TARGET`), keep driven
+  constraints after their driver (`A42_DRIVEN_CONSTRAINTS_UPDATE_AFTER_THEIR_DRIVER`),
+  read the dial across its value grid with `rigc render --candidate <out> --parallax <dial>`
+  (AUTHORING §8.12), and clip an iris or highlight to its painted socket with
+  `alphaClip` (AUTHORING §3.4, FACE §11).
 - **The validator's messages are the instructions.** Read each named failure as the
   pointer to the file that has to change — AUTHORING §5.
 
@@ -46,19 +60,23 @@ nothing about the fold, so author under `--profile rig-play`.
 
 What `A39` still cannot say is whether the projection was the right one —
 nothing measures whether 12° was the angle the shot wanted. FACE §9.2 is that
-demonstration, three builds with one of them refused, and §9.3 is the
-differential audit and the three limits it does not lift.
+demonstration, three builds with one of them refused, and §9.3 is the differential
+audit and the three limits it does not lift.
 
 ## Read, in this order
 
-1. [AUTHORING.md](https://github.com/rig-c/core/blob/main/docs/AUTHORING.md) — the `deform` timeline field by field
-   and what rigc refuses in it (§4), the failure map (§5–§6), the editor's
-   conventions (§10).
+1. [AUTHORING.md](https://github.com/rig-c/core/blob/main/docs/AUTHORING.md) — `alphaClip` and per-vertex `depth` maps
+   (§3.4, §3.4.5), slider constraints (§3.5.2), the `deform` timeline, `derive` and
+   `transform` field by field (§4, §4.5.1, §4.11, §4.11.1), the failure map
+   (§5–§6), `render --parallax <dial>` (§8.12), and the editor's conventions (§10).
 2. [MOTION.md](https://github.com/rig-c/core/blob/main/docs/MOTION.md) — timing, easing and the offset table (§3),
    candidates and the ballot (§4–§5). A blink and a gaze are ordinary motion work.
-3. [FACE.md](https://github.com/rig-c/core/blob/main/docs/FACE.md) — the face's own geometry: the closed form every
-   number in a turn comes from (§1), the hierarchy underneath (§3), what
-   foreshortens (§5), and the deform audit gap (§9).
+3. [FACE.md](https://github.com/rig-c/core/blob/main/docs/FACE.md) — the face's own geometry: the closed form and
+   `transform` (§1, §1.1), per-vertex depth sheets and turn ceilings (§2, §2.1,
+   §2.2), the shared-shift hierarchy and `derive` (§3, §3.1), the 3×5 mesh and its
+   silhouette cliff (§4), what foreshortens (§5), the blink and channel allocation
+   (§6–§7), the three cliffs and the turn as a slider-driven value (§8), the deform
+   audit gap (§9), and non-goals and `alphaClip` socket clipping (§11).
 4. Then [RIGGING.md](https://github.com/rig-c/core/blob/main/docs/RIGGING.md) for the hierarchy as a general rule
    rather than this closed form, and [INGEST.md](https://github.com/rig-c/core/blob/main/docs/INGEST.md) if the head
    arrived as a compiled skeleton.

package/skills/rigc-rigging/SKILL.md

@@ -36,17 +36,24 @@ index within that same limit; only legacy uncoded library errors point at `§5.1
 ## What this guide will not do
 
 Nothing grades a hierarchy. A rig with its head off its torso passes the gate, the
-pixels are nearly blind to structure, and the two instruments that see it at all
-are named in RIGGING §11 — neither as a pass bar.
+pixels are nearly blind to structure, and the instruments that see it at all are
+named in RIGGING §11 and §11.2 — none as a pass bar. `rigc pose` and `rigc chainfit`
+read part placements and chain hinges from a key-pose picture inside the loop
+(AUTHORING §11, RIGGING §9–§10); `rigc bonedist` measures per-frame bone
+world-transform distance against the same rig's own `home` setup-pose animation
+(RIGGING §7.3) or, at the finish line only, against another skeleton (RIGGING
+§11.2, subject to the honesty rule in AUTHORING §9.1).
 
 ## Read, in this order
 
 1. [AUTHORING.md](https://github.com/rig-c/core/blob/main/docs/AUTHORING.md) — the rig spec field by field (§3),
-   the failure map (§5–§6), reading a pose out of a picture (§8.1, §11, §12),
-   and the editor's own conventions (§10).
+   the failure map (§5–§6), reading a pose out of a picture and diagnostic render
+   flags (§8.1, §8.5, §8.7, §8.8, §11, §12), the honesty rule (§9.1), and the
+   editor's own conventions (§10).
 2. [RIGGING.md](https://github.com/rig-c/core/blob/main/docs/RIGGING.md) — the structure itself: what identifies a
-   pivot and what moving one costs (§2–§3), gauges (§4), what a chain can reach
-   (§6), and the instruments that see structure (§11).
+   pivot and what moving one costs (§2–§3), gauges (§4), what a chain can reach and
+   `bonedist` against `home` (§6–§7, §7.3), and the instruments that see structure
+   (§11, §11.2).
 3. Then [MOTION.md](https://github.com/rig-c/core/blob/main/docs/MOTION.md) once the skeleton exists;
    [FACE.md](https://github.com/rig-c/core/blob/main/docs/FACE.md) if the figure is a head;
    [INGEST.md](https://github.com/rig-c/core/blob/main/docs/INGEST.md) if the skeleton was handed to you already

package/src/assertions/emitted/index.ts

@@ -129,7 +129,7 @@ export function roundTripOnlyCodes(): string[] {
 
 /** The restated rules over one build's emitted texts, in `validate()`'s report shape. */
 export function validateEmittedText(given: EmittedTextInput): VerdictLists & { profile: AssertionProfile } {
-  // A former profile name reads as its profile (issue #1277), for the rules and the report alike.
+  // Refuse unknown and removed profiles before choosing policy or writing a report (issue #1668).
   const input: EmittedTextInput = { ...given, profile: resolveProfile(given.profile, 'the emitted text') };
   const known = new Set(EMITTED_TEXT_RULES.map((r) => r.code));
   const unrun = roundTripOnlyCodes().filter((code) => !known.has(code));

package/src/assertions/harness.ts

@@ -75,9 +75,8 @@ export interface VerdictHarness extends VerdictLists {
  * the table lacks — `validate` for the gate, so its message is the one it was.
  */
 export function verdictHarness(profile: AssertionProfile, kinds: Readonly<Record<string, AssertionKind>>, who: string): VerdictHarness {
-  // A former name resolves to its profile and anything outside the pair is
-  // refused by name — `resolveProfile` says why. The entries resolve before
-  // they get here, so this is the floor for a caller of the harness itself.
+  // Anything outside the two profiles is refused by name. Entries check before
+  // they get here too; this is the floor for a caller of the harness itself.
   profile = resolveProfile(profile, who);
   const failures: Failure[] = [];
   const passed: string[] = [];

package/src/assertions/kinds.ts

@@ -14,28 +14,9 @@
 /** The two rulebooks — `ValidateProfile` in `src/validate.ts`, where the choice between them is argued. */
 export type AssertionProfile = 'spine' | 'rig-play';
 
-/**
- * A profile's former name, which the CLI's `--profile` still reads for one
- * minor and resolves at parse time, printing the deprecation line that names
- * the profile it reads as (issue #1277). Nothing past the flag parser sees an
- * alias: the rule set is keyed on the profile it resolves to, so the alias and
- * its target cannot come to run different rules.
- */
-export const PROFILE_ALIASES: Readonly<Record<string, AssertionProfile>> = { 'spine-html': 'rig-play' };
-
-/**
- * The profile a gate entry runs under: a profile as given, a former name as the
- * profile it became — silently, because the CLI prints the deprecation line and
- * a library caller of `validate()` through a courtesy key passed the former
- * name on the release before this one and must get the same rules — and
- * anything else refused by name. `kindRunsUnder` reads every name but
- * `rig-play` as validity-only, so an unresolved name would run a weaker gate in
- * silence, under a name nobody chose (issue #1277).
- */
+/** Refuse an unknown profile before the kind rule can silently select validity alone. */
 export function resolveProfile(profile: string, who: string): AssertionProfile {
   if (profile === 'spine' || profile === 'rig-play') return profile;
-  const target = Object.hasOwn(PROFILE_ALIASES, profile) ? PROFILE_ALIASES[profile] : undefined;
-  if (target !== undefined) return target;
   throw new Error(`${who}: profile ${JSON.stringify(profile)} is not a profile; the profiles are "spine" and "rig-play"`);
 }
 

package/src/assertions/model/index.ts

@@ -386,7 +386,7 @@ function rigFigures(stats: Record<string, number | string>, read: ReadDocument |
  * pass one.
  */
 export function validateModel(given: ModelValidateInput, plant: Partial<ModelSupply> = {}): ModelReport {
-  // A former profile name reads as its profile (issue #1277), for the policy switches and the report alike.
+  // Refuse unknown and removed profiles before choosing policy or writing a report (issue #1668).
   const input: ModelValidateInput = { ...given, profile: resolveProfile(given.profile, 'the model side') };
   const supply: ModelSupply = { ...MODEL_SUPPLY, ...plant };
   const h = verdictHarness(input.profile, { ...ASSERTION_KIND, ...MODEL_PARSE_KIND }, 'the model side');

package/src/assertions/report.ts

@@ -12,17 +12,6 @@ import { failLine } from '../guide.ts';
 
 export const VALIDATE_PROFILES: readonly AssertionProfile[] = ['spine', 'rig-play'];
 
-/**
- * The line `--profile <alias>` prints on stderr before the command runs: the
- * old name, the profile it reads as, and the flag to pass instead (issue
- * #1277). Stderr so a report on stdout reads the same whichever name the
- * caller typed; the report itself names the profile that judged it, which is
- * the target and never the alias.
- */
-export function profileAliasLine(alias: string, target: AssertionProfile): string {
-  return `rigc: --profile ${alias} is deprecated and reads as --profile ${target}, the same rules; it is accepted until the next major release — pass --profile ${target}`;
-}
-
 /**
  * What the CLI uses when `--profile` is absent — and ONLY the CLI. This is not
  * `validate()`'s default; that function has none (`ValidateProfile` in

package/src/cli/shared.ts

@@ -26,11 +26,10 @@ import {
   CLI_DEFAULT_PROFILE,
   type GateHere,
   type PackPageFigures,
-  profileAliasLine,
   VALIDATE_PROFILES,
 } from '../assertions/report.ts';
 import type { VerdictLists } from '../assertions/harness.ts';
-import { PROFILE_ALIASES, type AssertionProfile } from '../assertions/kinds.ts';
+import type { AssertionProfile } from '../assertions/kinds.ts';
 import { MAX_CANDIDATES, MIN_CANDIDATES } from '../ballot.ts';
 import { BONEDIST_SPEC, IDENTITY_CORRESPONDENCE } from '../correspondence.ts';
 import { ANCHOR_MAX_RESIDUAL, ANCHOR_MAX_UNEXPLAINED, DEFAULT_HINGE_MAX, DEFAULT_HINGE_MIN, DEFAULT_MIN_LEVER_PX, DEFAULT_MIN_VISIBLE, DEFAULT_PASSES } from '../chainfit.ts';
@@ -2245,13 +2244,6 @@ export function usageText(docs: readonly CommandDoc[], checkout: string, rules:
 export function readProfile(flags: Record<string, string>): AssertionProfile {
   const raw = flags.profile;
   if (raw === undefined) return CLI_DEFAULT_PROFILE;
-  // A former name resolves here and nowhere else (issue #1277): past this line
-  // the alias does not exist, so it cannot select a rule set of its own.
-  const aliased = Object.hasOwn(PROFILE_ALIASES, raw) ? PROFILE_ALIASES[raw] : undefined;
-  if (aliased !== undefined) {
-    console.error(profileAliasLine(raw, aliased));
-    return aliased;
-  }
   const found = VALIDATE_PROFILES.find((p) => p === raw);
   if (!found) throw new UsageError(`--profile ${JSON.stringify(raw)}; known profiles: ${VALIDATE_PROFILES.join(', ')}`);
   return found;

package/src/core/entry.ts

@@ -47,5 +47,6 @@ export type { DrawnRegion, UvPage, UvRegion, UvSource } from './uvs.ts';
 export { clipThrough, clipShapeOf, convexWhy, REGION_UVS, REGION_TRIANGLES } from './clipping.ts';
 export type { ClipShape, ClipResult } from './clipping.ts';
 export { eventsFired } from './events.ts';
-export { bezierPolyline, BEZIER_PIECES } from './animation.ts';
+export { bezierPolyline, BEZIER_PIECES, IRR_OFFSET } from './animation.ts';
 export type { ModelPage, ModelPageRegion } from '../model.ts';
+export { RUNTIME_PI } from './world.ts';

package/src/motion.ts

@@ -819,3 +819,6 @@ function parseMotionSpecInto(raw: unknown, where: string, visits: readonly Shape
 
   return raw as unknown as MotionSpec;
 }
+
+/** Named type used by consumer motion readers (issue #1668). */
+export type { MotionSpec } from './types.ts';

package/src/render_read.ts

@@ -41,6 +41,7 @@ export type {
   BoneSnapshot,
   AttachmentPose,
   AttachmentRest,
+  GeometryFile,
   Piece,
   PieceCommon,
   PieceTexture,

package/src/validate.ts

@@ -2009,7 +2009,7 @@ function once<T>(supply: () => T): () => T {
 }
 
 export function validate(input: ValidateInput): ValidateReport {
-  // A former name reads as its profile (issue #1277): the policy switch below and the report both use the resolved one.
+  // Refuse unknown and removed profiles before choosing policy or writing a report (issue #1668).
   const profile = resolveProfile(input.profile, 'validate');
   /** True when this profile's rulebook includes the policy layer. */
   const policy = profile === 'rig-play';