rig-parts 1.5.2 → 1.5.4

package/NOTICE.md

@@ -69,7 +69,7 @@ only as a development dependency, and an install of rig-c gates a build with
 its own validator. rig-parts does not install it either; it is this repository's
 development dependency, at the version rig-c develops against, for the round
 trip in the selftest and CI and the selftest's posing oracle.
-rig-c's [NOTICE.md](https://github.com/firejune/rigc/blob/main/NOTICE.md)
+rig-c's [NOTICE.md](https://github.com/rig-c/core/blob/main/NOTICE.md)
 sets out the chain in full; briefly, as a restatement of Esoteric Software's
 terms and not a term of this project:
 

package/README.md

@@ -4,7 +4,7 @@
 are written.** rig-parts takes a single character painting and the layers
 [See-through](https://github.com/shitagaki-lab/see-through) decomposed it into,
 merges them into measured rig-space parts, authors weighted meshes, bone chains
-and a looping idle over them in [rig-c](https://github.com/firejune/rigc)'s
+and a looping idle over them in [rig-c](https://github.com/rig-c/core)'s
 spec, and hands that spec to rig-c to compile, gate, pack, render and check.
 It is built for agents that cannot see the image: every stage prints named,
 numeric findings, a refusal names the object, the value found and the value
@@ -14,12 +14,12 @@ input is silent.
 ## What you get
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/firejune/rig-parts/main/assets/demo-source.png" alt="The demo painting: a generated full-body character in a white and pink frilled dress with long pink twin tails, standing with her hands clasped" height="420" />
-  <img src="https://raw.githubusercontent.com/firejune/rig-parts/main/assets/demo-idle.png" alt="The same character rigged, breathing, blinking once and swaying her hair, sleeves and skirt in a four-second loop" height="420" />
+  <img src="https://raw.githubusercontent.com/rig-c/parts/main/assets/demo-source.png" alt="The demo painting: a generated full-body character in a white and pink frilled dress with long pink twin tails, standing with her hands clasped" height="420" />
+  <img src="https://raw.githubusercontent.com/rig-c/parts/main/assets/demo-idle.png" alt="The same character rigged, breathing, blinking once and swaying her hair, sleeves and skirt in a four-second loop" height="420" />
 </p>
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/firejune/rig-parts/main/assets/demo-parts.png" alt="Contact sheet of the painting and the 22 assembled parts it was split into: hair, dress, sleeves, shoes, face, eyes, brows, mouth and ornaments" width="100%" />
+  <img src="https://raw.githubusercontent.com/rig-c/parts/main/assets/demo-parts.png" alt="Contact sheet of the painting and the 22 assembled parts it was split into: hair, dress, sleeves, shoes, face, eyes, brows, mouth and ornaments" width="100%" />
 </p>
 
 <p align="center"><em>
@@ -40,7 +40,7 @@ is taken from the full run, because the twin tails leave the head crop sideways
 <code>seam: setup pose at 714x1216, scale 0.9422: mean |d| 0.234 (&lt;= 1.0), 2 px over 40, 2.25 rig px (the count / s²; &lt;= 50), 0 px over 80 (reported)</code><br/>
 <code>pack: skeleton.png 922x1348, 22 region(s), 94.9% covered, padding 2, page edges free, shape polygon</code><br/>
 <code>--seam silhouette</code> repaired the navy blobs the default rule leaves on the white
-blouse (recomposite error pixels 11,050 → 9,540); the default stays
+blouse (recomposite error pixels 10,340 → 8,644); the default stays
 <code>near-white</code>, the reference implementation's rule, so the examples stay
 comparable with it. The loop is <code>rig-parts loop --palette</code>'s indexed APNG, 48 frames at
 12 fps, 1,706,719 bytes, one 256-entry palette at a measured error of max 57, mean 1.601
@@ -54,7 +54,7 @@ made the contact sheet.
 </em></p>
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/firejune/rig-parts/main/assets/sample-parts.png" alt="Contact sheet of the sample character's painting and its 20 parts" width="560" />
+  <img src="https://raw.githubusercontent.com/rig-c/parts/main/assets/sample-parts.png" alt="Contact sheet of the sample character's painting and its 20 parts" width="560" />
 </p>
 
 <p align="center"><em>
@@ -148,9 +148,9 @@ atlas written by anything else would have no oracle behind it.
 
 | stage | tool | what it owns |
 | --- | --- | --- |
-| painting + See-through layers → parts and specs | **rig-parts** | the merge of two runs, the measurements, the rig spec and motion spec |
-| specs → Spine skeleton data | **[rig-c](https://github.com/firejune/rigc)** | compile, the gate (rigc's own validator in an install; the round trip through `spine-core` where the runtime is beside it, as in this repository's CI), the named assertions, the packer, the renderer |
-| skeleton data → a page | **[rig-play](https://github.com/firejune/rig-play)** (formerly spine-html), a sibling project | a DOM renderer; rigc's `spine-html` profile is its policy, and every build here is gated under that profile as well as under `spine` |
+| painting + See-through layers → parts and specs | **rig-parts** (npm `@rig-c/parts`) | the merge of two runs, the measurements, the rig spec and motion spec |
+| specs → Spine skeleton data | **[rig-c](https://github.com/rig-c/core)** (npm `rig-c`) | compile, the gate (rigc's own validator in an install; the round trip through `spine-core` where the runtime is beside it, as in this repository's CI), the named assertions, the packer, the renderer |
+| skeleton data → a page | **[rig-play](https://github.com/rig-c/play)** (npm `@rig-c/play`; formerly spine-html), a sibling project | a DOM renderer; rigc's `spine-html` profile is its policy, and every build here is gated under that profile as well as under `spine` |
 
 rig-parts never writes Spine data itself. Everything on disk under `check/build/`
 was written by rig-c after its own gate passed.
@@ -388,15 +388,17 @@ before it, at v0.14.0).
 
 ## Requirements
 
-[Bun](https://bun.sh) 1.2 or later. `npm install -g rig-parts` installs the
-`rig-parts` command; it hands off to Bun and says so in one sentence if Bun is not
-on `PATH`. **`rig-parts` is the package's name; versions up to 0.16.0 were published
+[Bun](https://bun.sh) 1.2 or later. `npm i -D @rig-c/parts` installs the
+`rig-parts` command (`npm install -g @rig-c/parts` puts it on `PATH`); it hands off
+to Bun and says so in one sentence if Bun is not on `PATH`. **`@rig-c/parts` is the
+package's name; versions 1.0.0-rc.1 to 1.5.3 were published as `rig-parts`, and
+versions up to 0.16.0
 as `spine-parts`, its former name**, and the install keeps a `spine-parts` command
 beside `rig-parts` for the transition, the same launcher under both names. On npm
-the alias `spine-parts` stays published beside `rig-parts` at every version,
+both former names stay published beside `@rig-c/parts` at every version, as aliases
 carrying the same files with only the `name` in `package.json` changed, so a
-project that depends on the former name keeps receiving every release; a new
-install names `rig-parts` ([RELEASING.md](RELEASING.md), *The registry side*). rig-c
+project that depends on either keeps receiving every release; a new
+install names `@rig-c/parts` ([RELEASING.md](RELEASING.md), *The registry side*). rig-c
 comes with it as a dependency. No Spine runtime does: since
 rig-c 2.0 the installed `rigc` gates every build with its own validator over the
 compiled model document, and `rigc --version` says `entry: cli_core.ts —

package/cli.ts

@@ -550,6 +550,39 @@ function printLayerTable(set: LayerSet): void {
   console.log(`  ${warned} WARN line(s)`);
 }
 
+/**
+ * Every flag each command takes: `valued` flags carry a value, `switches` are bare. Each parser reads its row to
+ * decide what it accepts, and {@link notTaken} prints the same row in the unknown-flag refusal, so the refusal
+ * lists exactly the flags the parser accepts (CL26). `layers` takes one positional path and no flag, so it has no row.
+ */
+const TAKES = {
+  sheet: { valued: ['--source', '--layers', '--out', '--cell', '--cols'], switches: [] },
+  rig: { valued: ['--config', '--parts', '--out', '--idle-keys', '--page-edges', '--pack-shape'], switches: [] },
+  propose: { valued: ['--parts', '--source', '--out', '--from-config', '--compare', '--full', '--canvas', '--keypoints', '--person', '--wrist-snap'], switches: ['--head-box'] },
+  compare: { valued: ['--left', '--right', '--map'], switches: [] },
+  check: { valued: ['--rig', '--out', '--parts', '--source', '--page-edges', '--pack-shape', '--requirements'], switches: ['--seam-pairs', '--keep-stills'] },
+  loop: { valued: ['--frames', '--out'], switches: ['--palette'] },
+  assemble: { valued: ['--source', '--full', '--head', '--config', '--out', '--seam', '--project'], switches: ['--propose-plan'] },
+  'comfy seethrough': { valued: ['--image', '--out', '--resolution', '--steps', '--seed', '--prefix', '--host', '--wait', '--timeout', '--poll'], switches: ['--offload', '--lama', '--nf4'] },
+  'comfy paint': { valued: ['--config', '--out', '--seeds', '--seed0', '--host', '--wait', '--timeout', '--poll'], switches: [] },
+  inputs: { valued: ['--source', '--config', '--out'], switches: [] },
+  build: { valued: ['--config', '--source', '--full', '--head', '--out', '--seam', '--project', '--page-edges', '--pack-shape', '--requirements', '--idle-keys'], switches: ['--loop'] },
+  compose: { valued: ['--scene', '--out', '--requirements', '--accept'], switches: [] },
+} as const satisfies Record<string, { valued: readonly string[]; switches: readonly string[] }>;
+
+type Command = keyof typeof TAKES;
+
+/** Whether `command` takes `flag` as a valued flag, read off its {@link TAKES} row. */
+function takesValued(command: Command, flag: string): boolean {
+  return (TAKES[command].valued as readonly string[]).includes(flag);
+}
+
+/** The unknown-flag refusal: the flag, and every flag the command's {@link TAKES} row holds, valued then bare. */
+function notTaken(command: Command, flag: string): string {
+  const row = TAKES[command];
+  return `${command} does not take "${flag}"; it takes ${[...row.valued, ...row.switches].join(', ')}`;
+}
+
 function cmdLayers(args: string[]): number {
   if (args.length !== 1) return usage(`layers takes one path; got ${args.length}`);
   try {
@@ -569,7 +602,7 @@ function cmdSheet(args: string[]): number {
   for (let i = 0; i < args.length; i++) {
     const flag = args[i];
     const value = args[i + 1];
-    if (!['--source', '--layers', '--out', '--cell', '--cols'].includes(flag)) return usage(`sheet does not take "${flag}"`);
+    if (!takesValued('sheet', flag)) return usage(notTaken('sheet', flag));
     if (value === undefined) return usage(`${flag} needs a value`);
     i++;
     if (flag === '--source') source = value;
@@ -639,7 +672,7 @@ function cmdRig(args: string[]): number {
   for (let i = 0; i < args.length; i++) {
     const flag = args[i];
     const value = args[i + 1];
-    if (!['--config', '--parts', '--out', '--idle-keys', '--page-edges', '--pack-shape'].includes(flag)) return usage(`rig does not take "${flag}"`);
+    if (!takesValued('rig', flag)) return usage(notTaken('rig', flag));
     if (value === undefined) return usage(`${flag} needs a value`);
     i++;
     if (flag === '--config') config = value;
@@ -699,18 +732,17 @@ function rigcRunner(bin: string): RigcRunner {
   };
 }
 
-/** `switches` are the command's bare flags, taken out by the caller before this reads the valued ones; they are only named in the unknown-flag refusal, so it lists every flag the command takes. */
-function flags(args: string[], known: readonly string[], command: string, optional: readonly string[] = [], switches: readonly string[] = []): Map<string, string> | string {
+/** The command's valued flags as `--flag value` pairs, each one its {@link TAKES} row holds; `required` must all be given. Its bare switches are taken out by the caller before this reads the rest. A string is a usage error. */
+function flags(args: string[], command: Command, required: readonly string[]): Map<string, string> | string {
   const got = new Map<string, string>();
-  const all = [...known, ...optional];
   for (let i = 0; i < args.length; i += 2) {
     const flag = args[i];
-    if (!all.includes(flag)) return `${command} does not take "${flag}"; it takes ${[...all, ...switches].join(', ')}`;
+    if (!takesValued(command, flag)) return notTaken(command, flag);
     if (args[i + 1] === undefined) return `${flag} needs a value`;
     if (got.has(flag)) return `${flag} is given twice`;
     got.set(flag, args[i + 1]);
   }
-  for (const k of known) if (!got.has(k)) return `${command} needs ${k} <value>`;
+  for (const k of required) if (!got.has(k)) return `${command} needs ${k} <value>`;
   return got;
 }
 
@@ -722,10 +754,8 @@ function cmdCheck(args: string[]): number {
   if (keepStills > 1) return usage('--keep-stills is given twice');
   const f = flags(
     args.filter((a) => a !== '--seam-pairs' && a !== '--keep-stills'),
-    ['--rig', '--out'],
     'check',
-    ['--parts', '--source', '--page-edges', '--pack-shape', '--requirements'],
-    ['--seam-pairs', '--keep-stills'],
+    ['--rig', '--out'],
   );
   if (typeof f === 'string') return usage(f);
   const rig = f.get('--rig') as string;
@@ -775,14 +805,13 @@ function printLint(P: PartSet, spec: { bones: CharacterConfig['bones']; meshes:
 function cmdPropose(args: string[]): number {
   const flags = new Map<string, string>();
   let headBox = false;
-  const valued = ['--parts', '--source', '--out', '--from-config', '--compare', '--full', '--canvas', '--keypoints', '--person', '--wrist-snap'];
   for (let i = 0; i < args.length; i++) {
     const flag = args[i];
     if (flag === '--head-box') {
       headBox = true;
       continue;
     }
-    if (!valued.includes(flag)) return usage(`propose does not take "${flag}"; it takes --head-box and ${valued.join(', ')}`);
+    if (!takesValued('propose', flag)) return usage(notTaken('propose', flag));
     const value = args[i + 1];
     if (value === undefined) return usage(`${flag} needs a value`);
     if (flags.has(flag)) return usage(`${flag} is given twice`);
@@ -880,10 +909,9 @@ function cmdPropose(args: string[]): number {
 
 function cmdCompare(args: string[]): number {
   const flags = new Map<string, string>();
-  const valued = ['--left', '--right', '--map'];
   for (let i = 0; i < args.length; i++) {
     const flag = args[i];
-    if (!valued.includes(flag)) return usage(`compare does not take "${flag}"; it takes ${valued.join(', ')}`);
+    if (!takesValued('compare', flag)) return usage(notTaken('compare', flag));
     const value = args[i + 1];
     if (value === undefined) return usage(`${flag} needs a value`);
     if (flags.has(flag)) return usage(`${flag} is given twice`);
@@ -912,8 +940,8 @@ function cmdLoop(args: string[]): number {
   if (palettes > 1) return usage('--palette is given twice');
   const f = flags(
     args.filter((a) => a !== '--palette'),
-    ['--frames', '--out'],
     'loop',
+    ['--frames', '--out'],
   );
   if (typeof f === 'string') return usage(f);
   const out = f.get('--out') as string;
@@ -932,14 +960,13 @@ function cmdLoop(args: string[]): number {
 function cmdAssemble(args: string[]): number {
   const flags = new Map<string, string>();
   let propose = false;
-  const valued = ['--source', '--full', '--head', '--config', '--out', '--seam', '--project'];
   for (let i = 0; i < args.length; i++) {
     const flag = args[i];
     if (flag === '--propose-plan') {
       propose = true;
       continue;
     }
-    if (!valued.includes(flag)) return usage(`assemble does not take "${flag}"`);
+    if (!takesValued('assemble', flag)) return usage(notTaken('assemble', flag));
     const value = args[i + 1];
     if (value === undefined) return usage(`${flag} needs a value`);
     if (flags.has(flag)) return usage(`${flag} is given twice`);
@@ -975,8 +1002,9 @@ function cmdAssemble(args: string[]): number {
   }
 }
 
-/** Parse `--flag value` pairs and bare `--switch`es; a string is a usage error. */
-function comfyFlags(args: string[], valued: readonly string[], switches: readonly string[], command: string): { v: Map<string, string>; on: Set<string> } | string {
+/** Parse `--flag value` pairs and bare `--switch`es, as the command's {@link TAKES} row names them; a string is a usage error. */
+function comfyFlags(args: string[], command: 'comfy seethrough' | 'comfy paint'): { v: Map<string, string>; on: Set<string> } | string {
+  const switches: readonly string[] = TAKES[command].switches;
   const v = new Map<string, string>();
   const on = new Set<string>();
   for (let i = 0; i < args.length; i++) {
@@ -986,7 +1014,7 @@ function comfyFlags(args: string[], valued: readonly string[], switches: readonl
       on.add(flag);
       continue;
     }
-    if (!valued.includes(flag)) return `${command} does not take "${flag}"; it takes ${[...valued, ...switches].join(', ')}`;
+    if (!takesValued(command, flag)) return notTaken(command, flag);
     const value = args[i + 1];
     if (value === undefined) return `${flag} needs a value`;
     if (v.has(flag)) return `${flag} is given twice`;
@@ -1012,14 +1040,10 @@ function secondsFlag(v: Map<string, string>, flag: string, fallback: number): nu
   return Number.isFinite(n) && n > 0 ? n : `${flag} ${raw} is not a number of seconds above 0`;
 }
 
-const COMFY_TIMING = ['--host', '--wait', '--timeout', '--poll'] as const;
-
 async function cmdComfy(args: string[]): Promise<number> {
   const [sub, ...rest] = args;
   if (sub !== 'seethrough' && sub !== 'paint') return usage(`comfy takes seethrough or paint; got ${sub === undefined ? 'nothing' : `"${sub}"`}`);
-  const valued = sub === 'seethrough' ? ['--image', '--out', '--resolution', '--steps', '--seed', '--prefix', ...COMFY_TIMING] : ['--config', '--out', '--seeds', '--seed0', ...COMFY_TIMING];
-  const switches = sub === 'seethrough' ? ['--offload', '--lama', '--nf4'] : [];
-  const f = comfyFlags(rest, valued, switches, `comfy ${sub}`);
+  const f = comfyFlags(rest, `comfy ${sub}`);
   if (typeof f === 'string') return usage(f);
   const { v, on } = f;
   const wait = secondsFlag(v, '--wait', 1800);
@@ -1082,7 +1106,7 @@ async function cmdComfy(args: string[]): Promise<number> {
 }
 
 function cmdInputs(args: string[]): number {
-  const f = flags(args, ['--source', '--config', '--out'], 'inputs');
+  const f = flags(args, 'inputs', ['--source', '--config', '--out']);
   if (typeof f === 'string') return usage(f);
   const source = f.get('--source') as string;
   const out = f.get('--out') as string;
@@ -1114,7 +1138,6 @@ function cmdInputs(args: string[]): number {
 function cmdBuild(args: string[]): number {
   const flags = new Map<string, string>();
   let loop = false;
-  const valued = ['--config', '--source', '--full', '--head', '--out', '--seam', '--project', '--page-edges', '--pack-shape', '--requirements', '--idle-keys'];
   for (let i = 0; i < args.length; i++) {
     const flag = args[i];
     if (flag === '--loop') {
@@ -1122,7 +1145,7 @@ function cmdBuild(args: string[]): number {
       loop = true;
       continue;
     }
-    if (!valued.includes(flag)) return usage(`build does not take "${flag}"; it takes --loop and ${valued.join(', ')}`);
+    if (!takesValued('build', flag)) return usage(notTaken('build', flag));
     const value = args[i + 1];
     if (value === undefined) return usage(`${flag} needs a value`);
     if (flags.has(flag)) return usage(`${flag} is given twice`);
@@ -1161,7 +1184,7 @@ function cmdBuild(args: string[]): number {
 }
 
 function cmdCompose(args: string[]): number {
-  const f = flags(args, ['--scene', '--out'], 'compose', ['--requirements', '--accept']);
+  const f = flags(args, 'compose', ['--scene', '--out']);
   if (typeof f === 'string') return usage(f);
   let bin: string;
   try {

package/docs/AUTHORING.md

@@ -17,7 +17,7 @@ into `examples/sample/inputs/`.
 
 | what | why | how |
 | --- | --- | --- |
-| [Bun](https://bun.sh) 1.2 or later | rig-parts and rig-c are Bun programs | `npm install -g rig-parts` installs the command; it says so if Bun is missing |
+| [Bun](https://bun.sh) 1.2 or later | rig-parts and rig-c are Bun programs | `npm install -g @rig-c/parts` installs the command; it says so if Bun is missing |
 | [rig-c](https://www.npmjs.com/package/rig-c) | compiles, gates, packs and renders every rig; rig-parts writes no Spine data itself | installed with rig-parts as a dependency (`node_modules/.bin/rigc`); with no Spine runtime beside it, it gates with its own validator, and `rigc --version` says `entry: cli_core.ts` |
 | [See-through](https://github.com/shitagaki-lab/see-through), somewhere | the layer decomposition is the input | any route in README *Getting See-through layers*; it runs twice per character, outside this tool |
 | a GPU, wherever See-through runs | See-through is a diffusion model | nothing in rig-parts itself uses a GPU |
@@ -1230,8 +1230,10 @@ names it — `[29]` on both examples.
 flat stack of parts differs from the painting by more than 60, the top part takes the
 painting's colour — except where the painting is near-white, which protects the page
 and also every white garment. `--seam silhouette` protects near-white pixels only
-outside the figure. On the demo it lowered recomposite error pixels from 11,050 to
-9,540 and changed no check bar; on the sample it changed nothing. The default stays
+outside the figure. On the demo it lowers recomposite error pixels from 10,340 to
+8,644 (`assemble`'s `error px > 40`, at v1.5.2); on the sample it changes nothing
+(4,359 under both). At v0.14.0 the demo's were 11,050 and 9,540, and no check bar
+changed. The default stays
 the reference's so the examples stay comparable with it.
 
 **The fringe push-back** (issue #119; under either seam rule, no flag). Both places
@@ -1253,9 +1255,9 @@ and a cleared bridge to opaque art is put back, so no part gains an island
 names them. On the examples (default flags, measured against the v0.14.0 build of
 the same inputs): `demo` 1,193 px over 16 parts, recomposite error pixels 11,050 →
 10,340; `sample` 276 px over 15 parts, 4,512 → 4,359; uncovered error pixels and
-holes unchanged on both, `check` 9 of 9 on both. The `--seam` and `--project`
-comparisons in this section and the `SETUP_POSE_VS_SOURCE` example figures in §7
-were measured before it, at v0.14.0.
+holes unchanged on both, `check` 9 of 9 on both. The `--project` comparison in
+this section and the `SETUP_POSE_VS_SOURCE` example figures in §7 were measured
+before it, at v0.14.0; the `--seam` figures above are v1.5.2's.
 
 **Page edges.** `rig`, `check` and `build` pack through `rigc build --pack
 --page-edges <v>`, and hand the value to rigc verbatim. The default is `free`,

package/docs/MIGRATION.md

@@ -9,14 +9,14 @@ from the pull request that measured it.
 
 ## In one paragraph
 
-Install `rig-parts`. A config that built on 0.16.0 loads and builds unchanged: every
-config change since is a new, opt-in field inside a new mesh mode. The bytes a
-config without that mode builds moved once, by a declared exception (every mesh
-triangle's vertex order, #133); apart from it, each change since 0.16.0 that touched
-the code was measured against the tree before it on the three public examples'
-builds, and moved no byte of them. Inside the automatic mode, one change after the
-candidate moves declared bytes, named in *Since 1.0.0-rc.1*: the skinning envelope's
-reference (#169).
+Install `@rig-c/parts` (the package's name after 1.5.3; *After 1.5.3* below). A
+config that built on 0.16.0 loads and builds unchanged: every config change since is
+a new, opt-in field inside a new mesh mode. The bytes a config without that mode
+builds moved once, by a declared exception (every mesh triangle's vertex order,
+#133); apart from it, each change since 0.16.0 that touched the code was measured
+against the tree before it on the three public examples' builds, and moved no byte
+of them. Inside the automatic mode, one change after the candidate moves declared
+bytes, named in *Since 1.0.0-rc.1*: the skinning envelope's reference (#169).
 
 ## From 0.16.0 to 1.0.0-rc.1
 
@@ -31,7 +31,7 @@ reference (#169).
 | spec ids of the files authors write and this package writes | `spine-parts-requirements/1`, `spine-parts-scene/1`, `spine-parts-keypoints/1`, `spine-parts-bonemap/1`, `spine-parts-basis/1`, `spine-parts-scene-report/1` | unchanged: they name a file format, not the tool, so a file written before the rename still reads |
 | public examples repository | `spine-parts-examples` | unchanged (it keeps the name it was published under) |
 
-What to do: install with `npm install -g rig-parts` and write `rig-parts` in scripts.
+What to do: install with `npm install -g @rig-c/parts` and write `rig-parts` in scripts.
 A script or a dependant that names the alias `spine-parts` keeps working and keeps
 receiving every release; how long the alias stays is RELEASING.md's *The alias stays
 until its retirement questions have written answers*. No build output carries the
@@ -135,3 +135,16 @@ What to do: nothing for a config without `auto`. A config under `auto` that decl
 `motion.residual` may write a different mesh than 1.0.0-rc.1 did, as above; a
 consumer that compares builds byte for byte with 1.0.0-rc.1 expects that move and
 nothing else.
+
+## After 1.5.3: the scoped name
+
+| | 1.0.0 to 1.5.3 | after 1.5.3 |
+| --- | --- | --- |
+| npm package | `rig-parts` | `@rig-c/parts`; `rig-parts` and the alias `spine-parts` are published beside it at every version as aliases, the same files with only the `name` in `package.json` changed |
+| command | `rig-parts`, and the alias `spine-parts` on the same launcher | unchanged |
+| repository | `firejune/rig-parts` (GitHub redirects it) | `rig-c/parts`, beside `rig-c/core` (npm `rig-c`) and `rig-c/play` |
+| spec ids, the config, the bytes a build writes | | unchanged |
+
+What to do: install with `npm i -D @rig-c/parts` (or `npm install -g @rig-c/parts`);
+command lines do not change. A dependant that names `rig-parts` keeps receiving
+every release under it (#222).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rig-parts",
-  "version": "1.5.2",
+  "version": "1.5.4",
   "description": "AI-authored 2D character parts from one anime painting and its See-through layer decomposition: measured parts, weighted-mesh rig specs, verified through rig-c before anything is written. A CLI for agents that cannot see the image.",
   "type": "module",
   "bin": {
@@ -14,10 +14,10 @@
   "author": "firejune",
   "repository": {
     "type": "git",
-    "url": "https://github.com/firejune/rig-parts.git"
+    "url": "https://github.com/rig-c/parts.git"
   },
-  "homepage": "https://github.com/firejune/rig-parts#readme",
-  "bugs": "https://github.com/firejune/rig-parts/issues",
+  "homepage": "https://github.com/rig-c/parts#readme",
+  "bugs": "https://github.com/rig-c/parts/issues",
   "keywords": [
     "spine",
     "spine2d",

package/skills/rig-parts/SKILL.md

@@ -2,7 +2,7 @@
 name: rig-parts
 description: Turn one anime character painting and its See-through layer decomposition into a verified 2D character rig (Spine 4.3 skeleton data) — measured parts, weighted meshes, bone chains and a looping idle — with rig-parts, which gates everything through rig-c before it is written. Use for a request to rig or animate a single character painting, to run or read rig-parts layers, sheet, assemble, propose, rig, check, loop or build, or to write or fix a rig-parts config.json. Not for cutting art into parts by hand, for authoring a rig from loose PNGs (that is the rigc skill), for lip-sync or swapping a part's image, or for running See-through itself.
 license: MIT
-compatibility: Requires Bun 1.2 or later. The tool is the npm package rig-parts (bunx rig-parts, or bun add -d rig-parts); rig-c is installed with it. See-through is run separately.
+compatibility: Requires Bun 1.2 or later. The tool is the npm package @rig-c/parts (npm i -D @rig-c/parts, or bun add -d @rig-c/parts), whose command is rig-parts; rig-c is installed with it. See-through is run separately.
 ---
 
 # rig-parts — a painting to a Spine rig, for agents
@@ -125,7 +125,7 @@ it and the order as `scene.json` records it (AUTHORING §7, *Composing several
 characters*).
 
 `--seam silhouette` repairs more of the seam on white garments than the default
-`near-white` (the demo: 11,050 → 9,540 recomposite error pixels); the default is
+`near-white` (the demo: 10,340 → 8,644 recomposite error pixels); the default is
 the reference implementation's rule. `--project visible` lets thin visible parts
 (lashes, brows, irises) take the painting's pixels, which the default `core` rule
 erodes away. Name both rules you used in your report, and quote the assemble
@@ -150,9 +150,9 @@ share is synthesis where the painting was there to be taken.
 
 ## Where to read next
 
-[docs/AUTHORING.md](https://github.com/firejune/rig-parts/blob/main/docs/AUTHORING.md)
+[docs/AUTHORING.md](https://github.com/rig-c/parts/blob/main/docs/AUTHORING.md)
 first — every config field, the command order, what to read after each stage, every
-refusal. It is in the installed package at `node_modules/rig-parts/docs/AUTHORING.md`,
+refusal. It is in the installed package at `node_modules/@rig-c/parts/docs/AUTHORING.md`,
 the copy that matches the version you run. Two recipes there cover what this package
 leaves to you: