@rig-c/core 2.86.0 → 3.0.0

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.0",
   "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/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';