spine-rigc 0.5.0 → 0.6.0

package/docs/AUTHORING.md

@@ -29,22 +29,27 @@ that can see that, and a run that skips it has verified nothing about the motion
   attachment, keying practice, curve kind, draw order — sourced from Spine's own
   public documentation: **§10**
 
+If you were given no brief and no reference frames, this section does not apply to
+you — skip to **§0**. You are rigging somebody's own art rather than reproducing a
+measured shot, so none of what follows applies: it is the ladder's protocol, not a
+property of the tool.
+
 🔒 **A ladder run reads this guide in full and does not follow its references out of
 it.** The guide is allowed reading; not everything it cites is. Citations here are
 provenance for a reader of record — the loop that hit a trap, the issue that closed it —
 and following one can arrive at a stored candidate's own spec, at the corpus inventory,
-or at the gate a verdict is read against, none of which a run may open. So: read the
+or at the **derivation** of the gate a verdict is read against, none of which a run may
+open. ⭐ The gate's **clause statements** are a different matter and a run may read them:
+they are in `docs/GATE.md`, item 11 of the allowed list (owner ruling 2026-08-29) — the
+measure, the comparator, the number and the SKIP semantics, with no recorded figure in it.
+So: read the
 document, take its numbered sections as the input, and leave its footprints to whoever
 is maintaining it. The rule this states is that an **allowed-reading surface has to be
 closed under reading**; the criterion behind it is under *The honesty rule* in
-[LADDER.md](LADDER.md), and the enumerated allowed and forbidden lists are in
+[LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md), and the enumerated allowed and forbidden lists are in
 `bench/runs/README.md`, *What a run may read* — the prompt that starts a run quotes them
 outright, which is the copy that binds.
 
-If you were given no brief and no frames — you are rigging somebody's own art rather
-than reproducing a measured shot — none of this applies to you. It is the ladder's
-protocol, not a property of the tool.
-
 ## The vocabulary is Spine's
 
 Wherever rigc has no better abstraction it uses **Spine 4.3's own concept, its own
@@ -80,6 +85,10 @@ bun cli.ts check \
 
 # read the table → fix the spec → build again → check again
 #   ↳ read its per-frame column before its MAE — §9.2
+
+# …and if nobody gave you frames, LOOK at it instead — neither needs a reference:
+bun cli.ts render  --candidate path/to/spine    # PNG frames + a contact sheet grid
+bun cli.ts preview --candidate path/to/spine    # one .html that plays it in Spine's own player
 ```
 
 `build` compiles, round-trips the result through `@esotericsoftware/spine-core`,
@@ -112,16 +121,26 @@ What the flags mean:
 | `--rig` | the rig spec — skeleton structure |
 | `--motion` | the motion spec — time |
 | `--out` | directory for `skeleton.json` + `skeleton.atlas`; atlas page paths are written relative to it |
+| `--copy-images` | `build` only: also copies every referenced page PNG into `--out` and rewrites the atlas to the copies, so the directory is self-contained enough to zip or commit on its own. Default is unchanged — page paths still point at the source art (issue #217) |
 | `--images` | where the rig spec's `image` names resolve (overrides the rig's own `images` field, and is relative to your working directory) |
 | `--manifest` | a cut manifest. Only for a rig with **measured art** behind it; a foreign skeleton has none |
-| `--profile` | `spine` = the 20 validity rules · `spine-html` = all 34 (**the default**) |
-
-Pick the profile deliberately. `spine-html` adds one renderer's policy and one
-project's canvas budget, and those rules fire on perfectly correct Spine data
-(clipping attachments, unweighted meshes, packed atlases). If what you are
-authoring is "valid Spine 4.3 that any runtime plays correctly", use
-`--profile spine`. A report always prints which profile ran and lists what that
-profile left out, on `PROF` lines.
+| `--profile` | `spine` = the 20 validity rules (**the default**) · `spine-html` = all 34, opt-in |
+| `--candidate` | `check`, `bench`, `render` and `preview` only: a **compiled** artifact — the directory `build --out` wrote, or a `skeleton.json` path. `--atlas <path>` names the atlas when it does not sit beside the skeleton |
+| `--animation` | `render` and `preview` only: which animation to show. The default is **every** one for `render` and the **first** for `preview`. A name the skeleton does not have is refused, with the ones it does have listed |
+
+`render` also takes `--fps <n>` (the rate it samples at, default 12 — the same
+protocol rate the reference frames use) and `--max <px>` (the long side of a
+frame, default 256). Both commands take `--out`: a directory for `render`
+(default `render/`), the `.html` file for `preview` (default `preview.html`).
+
+Pick the profile deliberately, and know which one you got by saying nothing. The
+default is `spine`: "is this valid Spine 4.3 that any runtime plays correctly",
+which is the question a rig authored anywhere is asking. `--profile spine-html`
+adds one renderer's policy and one project's canvas budget on top, and those
+extra rules fire on perfectly correct Spine data (clipping attachments,
+unweighted meshes, packed atlases) — reach for it when you are shipping into
+*that* project, not to be thorough. A report always prints which profile ran and
+lists what that profile left out, on `PROF` lines.
 
 The other commands:
 
@@ -131,6 +150,8 @@ bun cli.ts validate path/to/spine                # re-gate artifacts already on
 bun cli.ts diff     candidate.json reference.json
 bun cli.ts check    --candidate path/to/spine --frames path/to/frames
 bun cli.ts bench    3 --candidate path/to/spine [--frames path/to/frames]
+bun cli.ts render   --candidate path/to/spine [--animation …] [--fps 12] [--max 256]
+bun cli.ts preview  --candidate path/to/spine [--animation …] [--out preview.html]
 ```
 
 - **`explain`** is the one to reach for when a rig compiles but looks wrong. It
@@ -144,12 +165,26 @@ bun cli.ts bench    3 --candidate path/to/spine [--frames path/to/frames]
   for opposite fixes. A measure with nothing to compare says `0/0` and says so.
 - **`check`** renders your candidate into the reference frames' own pixel grid and
   compares pixels — the only thing here that can see a wrong animation. **§9.**
-- **`bench <rung>`** runs one rung of [the benchmark ladder](LADDER.md): validate
+- **`bench <rung>`** runs one rung of [the benchmark ladder](https://github.com/firejune/rigc/blob/main/docs/LADDER.md): validate
   under `--profile spine`, then diff against that rung's reference export, and with
   `--frames` the `check` table as well. Unlike the three above it is a **finish
   line, not a loop**: it opens the reference export, so a run that consults it and
   then edits is no longer an authoring run. `check` carries no such restriction —
   see §9.
+- 🚨 **`render` and `preview` are how you LOOK at what you built**, and they are
+  the two that need no reference at all. Reach for them the moment a rig compiles
+  green, because green says nothing about the picture: a head that sits visibly
+  off its torso passes every assertion, loads in `spine-core` and steps
+  numerically clean — the offsets are the ones you asked for, and nothing in the
+  gate can know you did not mean them. `render` writes
+  `render/<animation>/f0000.png…` with a `contact.png` grid of **every** frame
+  beside them (open that one first — spacing is a comparison across frames) and a
+  `frames.json` sidecar naming the world box they are pictures of. `preview`
+  writes one self-contained `.html`: your skeleton, atlas and page PNGs are
+  embedded in it as data URIs and played by the official **Spine Web Player**, so
+  double-clicking it is also the interop proof — what plays there was played by
+  Esoteric Software's runtime, not by rigc's. The player is loaded from a CDN
+  rather than copied into the file, so the first open needs a network.
 
 ---
 
@@ -294,7 +329,7 @@ must be non-empty. `slots` must be present (it may be empty).
 payloads in this guide are written to illustrate a field, never copied out of a
 reference export — an example lifted from one would be handing an authoring agent an
 answer to the rung it is standing on, which is the rule §10.6 states and the honesty
-rule in [LADDER.md](LADDER.md) turns on. If a snippet here matches a reference file,
+rule in [LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) turns on. If a snippet here matches a reference file,
 that is a defect in this guide: report it. (It has happened — 2026-08-23; the incident
 is recorded in `bench/runs/README.md`, *What a run may read*.)
 
@@ -482,10 +517,10 @@ and takes every slot below it out of the frame. rigc refuses a name the rig does
 not declare. Omitting `end` entirely is the format's own way of saying "clip
 everything after this one", and is left alone.
 
-🚫 Under the default `spine-html` profile a clipping attachment is refused by
+🚫 Under `--profile spine-html` a clipping attachment is refused by
 `A11_NO_CLIPPING_ATTACHMENTS` — that renderer skips them silently, so a mask that
-was supposed to hide something would not. It is valid Spine and `--profile spine`
-accepts it; the refusal is policy, not validity.
+was supposed to hide something would not. It is valid Spine and the default
+`--profile spine` accepts it; the refusal is policy, not validity.
 
 ### 3.5 `constraints` — 4.3's single typed array
 
@@ -650,7 +685,7 @@ stepped.
   declared duration `6.5` never fired at all against an accumulated
   `6.499999999999994` — which read as a frame-change disagreement the pose series had
   already fixed, and cost that run three builds
-  ([`2026-08-26-rung5-1`](../bench/runs/2026-08-26-rung5-1/LOOP.md), §8). ⇒ **For a
+  ([`2026-08-26-rung5-1`](https://github.com/firejune/rigc/blob/main/bench/runs/2026-08-26-rung5-1/LOOP.md), §8). ⇒ **For a
   stepped timeline, write `T − 1e-6` rather than `T`.** One grid step early cannot
   reach the previous sample — 83,333 µs away at 12 fps — and is always seen by the
   sample it was written for; one ULP late loses the frame. This is the same asymmetry
@@ -867,7 +902,7 @@ The report prints one line per assertion:
 | `A16_SKELETON_VERSION_4_3` | both | the `skeleton.spine` label is not on the 4.3 line (`4.3`, `4.3.N`, `4.3.N-suffix`) |
 | `A17_ATLAS_PAGE_FILES_EXIST` | both | a page the atlas declares is not a file. Check `--images` and `--out` |
 | `A18_DETERMINISTIC_EMIT` | both | a second compile of the same inputs differed. That is a compiler bug, not a spec bug — report it |
-| `A19_OVERLAY_PNGS_HAVE_ALPHA` | renderer | an overlay page has a colour type with no alpha channel. Only the full-stage base plate may be opaque |
+| `A19_OVERLAY_PNGS_HAVE_ALPHA` | renderer | an overlay part image can never be transparent: no alpha channel (colour type 4 or 6) and no `tRNS` chunk either, so it would paint a solid rectangle over what is behind it. Re-export it as RGBA, or as an indexed / greyscale PNG that keeps its `tRNS`. Only the full-stage base plate may be opaque. Indexed-with-`tRNS` — the usual output of ImageMagick, "Export as PNG-8", GIMP's indexed mode, aseprite and pngquant — **passes**: it is transparent art |
 | `A20_MESH_WEIGHTS_COHERENT` | both ◑ | a weighted vertex with no bone, a negative weight, a bone index out of range, or weights that do not sum to 1. Under `spine-html` also: an unweighted mesh, or a binding at weight 0 |
 | `A21_MESH_RIM_PINNED` | archetype | a generated ring's rim, or a ribbon's entry row, is not pinned to its anchor bone at weight 1 |
 | `A22_MESH_UVS_IN_UNIT_RANGE` | both | a mesh UV outside its region, or a UV array that disagrees with the vertex count |
@@ -922,6 +957,8 @@ Two more limits that are not errors but will shape what you can attempt:
 ## 7. Before you call it done
 
 1. `build --profile <the one you meant>` exits 0 and the report has **no FAIL**.
+   Saying nothing means `spine`, so "the one you meant" is a decision either way —
+   the report's first line names the profile that judged it.
 2. Read the `SKIP` lines. Each one is a check that did *not* run — make sure none of
    them is a check you were relying on.
    ⚠️ Under `--profile spine` a foreign skeleton usually produces **no SKIP lines
@@ -1557,13 +1594,13 @@ that drew the reference frames, onto the same pixel grid, and reports what diffe
 you specifically: it means **you may run `check` as often as you like** without
 your run ceasing to be an honest authoring run. It is a loop, in the way `build` is
 a loop. `bench` and `diff` against a rung's export are not — they read the answer,
-and [the ladder's honesty rule](LADDER.md) makes them a finish line you reach once.
+and [the ladder's honesty rule](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) makes them a finish line you reach once.
 
 📌 **That is also why the MAE figures quoted through this section stay.** Every one of
 them is a candidate's own reading against rendered frames — the exam question, not the
 answer key — so none of them narrows a reference-side measure, and a guide that censored
 them would be teaching less for no gain in honesty. The criterion is under *The honesty
-rule* in [LADDER.md](LADDER.md) (issue #158); what it *does* seal is a score written
+rule* in [LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) (issue #158); what it *does* seal is a score written
 over a reference's own count, and no such figure appears here.
 
 🚨 **If you drive the runtime yourself, a bone's local transform lives on

package/docs/PROMPTING.md

@@ -0,0 +1,106 @@
+# Prompting an AI to author with rigc
+
+This page is for the person **operating** an AI agent — any AI agent — that will
+author a rig with rigc. It is not authoring guidance; that is
+[AUTHORING.md](AUTHORING.md), and the agent should read that file, not this one.
+This page tells you what to put in the prompt, and it earns its claims from a
+measured case: in August 2026 a deliberately small model — Gemini 3.7 Flash on
+the Antigravity harness — authored a benchmark rung unattended for three hours,
+and every stumble below is one it actually made, priced by the instruments in
+[PILOT.md](https://github.com/firejune/rigc/blob/main/docs/PILOT.md)'s protocol. A large model makes fewer of these mistakes
+unprompted; the clauses cost you three lines and make the small model's run
+land and the large model's run land cleaner.
+
+## The prompt skeleton
+
+For ordinary use (not a benchmark), the whole prompt is short:
+
+> Author a Spine rig with rigc for <what you want>. The images are in
+> `<dir>`. Read `docs/AUTHORING.md` in full before writing either spec —
+> sections 1–5 are the two file formats and the failure map, section 8 is how
+> to fit poses against picture references, section 10 is the editor's
+> conventions. Build with `rigc build`, keep going until `rigc validate` is
+> green, and treat every named failure as pointing at the file to change.
+
+Then add the clauses below. If you are running the **benchmark**, do not
+improvise a prompt at all — hand the agent
+[pilot/rung3-runner-prompt.md](https://github.com/firejune/rigc/blob/main/docs/pilot/rung3-runner-prompt.md) verbatim; it
+carries the honesty rule, and an improvised summary of that rule is how a run
+stops being scorable.
+
+## Five clauses the pilot paid for
+
+**1. Any search loop must print progress and carry a time-box.**
+The pilot wrote a pose-fitting script with no output and no bound, and its
+operator spent part of the evening deciding whether a silent 99 %-CPU process
+was working or hung. (It was working — but nobody could tell.) Say:
+
+> Long-running scripts must print one progress line per unit of work and state
+> an expected total up front. If a search would exceed ten minutes, stop and
+> narrow it instead.
+
+**2. Intermediate results go to files, not scrollback.**
+The pilot's first fitters printed results to stdout; a crashed step would have
+lost the lot. It later switched to JSON files on its own — start there. Say:
+
+> Write measured values (placements, angles, fitted poses) to files in the
+> working directory as you go. Treat your transcript as disposable.
+
+**3. Point the fitting method at AUTHORING §8, by number.**
+Given frames to match, the pilot's first instinct was a nested grid over every
+knob at once — tens of thousands of renders per frame. §8 describes the cheap
+loop (one knob at a time, render back, keep what the measurement keeps). The
+pilot had the file "in hand" and did not apply the section until it had burned
+hours. Say:
+
+> Fit poses the way AUTHORING §8 does — one variable at a time against a
+> render-back measurement. Do not grid-search several knobs jointly.
+
+**4. Keys are structure, not samples.**
+A fitter produces one pose per frame, and the pilot keyed nearly every one of
+them. The result *placed* its parts well — and still scored poorly on every
+timing measure, because animation data is sparse keys plus interpolation
+(AUTHORING §10.3–§10.4), and a key on every frame is a pixel transcription
+wearing a skeleton. Say:
+
+> Key extremes and contacts, then let curves carry the in-betweens, per
+> AUTHORING §10.3–10.4. If your fitted poses disagree with a curve, move the
+> curve, not key count. Also §4.4: when a bone's two axes need different
+> timing or easing, key the single-axis timelines, not the paired one.
+
+**5. Keep the loop log live.**
+The pilot wrote its `LOOP.md` at the end, from memory — two entries for a
+three-hour session, with eight generations of fitting scripts invisible
+between them. A log written afterwards records the story, not the work. Say:
+
+> Append to `LOOP.md` at the moment each build/measure/change step happens,
+> not at the end. One line per step is enough.
+
+**6. Make the agent typecheck its own helper scripts.**
+Bun strips types and runs, so an agent can call methods that do not exist and
+watch the script fail — or worse, silently misbehave — without ever learning
+the API was imagined. The pilot left behind a helper written against
+spine-core methods that were never real; the repository's `typecheck` gate
+caught it at landing, hours too late to help the run. Say:
+
+> After writing any helper script, run `bunx tsc --noEmit <file>` (or the
+> project's `typecheck` task) before trusting its output.
+
+## What you do not need to say
+
+The same pilot, unprompted, did all of this correctly: it looped
+`build → validate` until green and read the named failures as pointers; it ran
+the whole thing without a human answer for three hours; it killed its own
+stray processes; it recorded its model name honestly; and under the benchmark
+protocol it ran the scored diff exactly once, at the end, editing nothing
+after. The tool's own error surface carries that part of the conversation —
+prompt for the five clauses above and then let the agent work.
+
+## If you are scoring the run
+
+That is a different document: [PILOT.md](https://github.com/firejune/rigc/blob/main/docs/PILOT.md) is the protocol,
+`pilot/rung3-runner-prompt.md` is the exact prompt, and the evaluator sheet it
+names is for the judge only. The one rule that reaches this page: **never put
+baseline figures, reference structure, or previous runs' measures into the
+runner's prompt** — a number in the prompt is a target, and a run that aimed
+at a target measured nothing.

package/docs/SPEC_COVERAGE.md

@@ -5,18 +5,20 @@ what rigc emits today, and what the official example projects actually use — s
 ordered by what the benchmark ladder needs rather than by the spec's alphabet.
 
 Reproduce the measurements with `bun run fetch-examples && bun run bench:usage`
-([`bench/count_features.ts`](../bench/count_features.ts) → [`feature_matrix.csv`](feature_matrix.csv),
-[`feature_matrix.json`](feature_matrix.json)).
+([`bench/count_features.ts`](https://github.com/firejune/rigc/blob/main/bench/count_features.ts) → [`feature_matrix.csv`](https://github.com/firejune/rigc/blob/main/docs/feature_matrix.csv),
+[`feature_matrix.json`](https://github.com/firejune/rigc/blob/main/docs/feature_matrix.json)).
 
 > 🔼 **This note is dated and does not move; the measurements below are the corpus as it
 > stood on 2026-08-22 and stay as written. Its statements about what rigc *does* have gone
-> stale in five places, and the live ledger is [LADDER.md](LADDER.md):**
+> stale in five places, and the live ledger is [LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md):**
 >
 > - **B2 is fixed** — A16 accepts `4.3`, `4.3.N` and `4.3.N-<suffix>`, so all twelve example
 >   exports pass it.
-> - **The profile split exists** — `--profile spine | spine-html`, default `spine-html`, so the
->   nine renderer-policy assertions of §2.2 no longer apply to foreign data. That closes the
->   validator half of B3; the emitter half (no packer, no atlas importer) is untouched.
+> - **The profile split exists** — `--profile spine | spine-html`, **default `spine` since
+>   2026-08-29** (issue #221; it was `spine-html` when this survey was written), so the nine
+>   renderer-policy assertions of §2.2 no longer apply to foreign data, and no longer apply
+>   unasked. That closes the validator half of B3; the emitter half (no packer, no atlas
+>   importer) is untouched.
 > - **`walkTimelines` reaches all eleven groups** — §2.3 item 1 and §4.3 item 4 are done, so
 >   A05 is no longer blind to `ik` / `transform` / `path` / `slider` / `drawOrder` /
 >   `drawOrderFolder` / `events`.
@@ -25,7 +27,7 @@ Reproduce the measurements with `bun run fetch-examples && bun run bench:usage`
 >   attachments, the 4.3 typed constraint array and the invariants, all as data. So §2.4's
 >   "the bone tree is code, not data", §4.0's B1 row and executive-summary item 7 describe a
 >   state that no longer exists. Rung 3 transcribed into that format scores 1.000 on every
->   measure of every section — figures in [LADDER.md](LADDER.md).
+>   measure of every section — figures in [LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md).
 > - Since that change rigc also emits **ik and transform constraints**, the **single-axis bone
 >   timelines** (`translatex`/`translatey`/`scalex`/`scaley`/`shear`/`shearx`/`sheary`), bone
 >   `length`/`scale`/`shear`/`inherit`/`skin`/`color` setup fields, slot `dark`/`blend`, region
@@ -659,7 +661,7 @@ This is the split Part 4(c) needs. **Spine-validity** = the file is wrong for an
 | `A12_NO_DARK_COLOR` | **renderer-profile** | slot `dark`, `rgba2`/`rgb2` timelines — "parsed, then ignored" |
 | `A13_MESH_BUDGET` | **renderer-profile** | >4 mesh slots, >80 triangles per mesh |
 | `A14_NO_FULL_FRAME_MESH` | **renderer-profile** | a mesh spanning the whole stage |
-| `A19_OVERLAY_PNGS_HAVE_ALPHA` | **renderer-profile** | an overlay page with no alpha channel |
+| `A19_OVERLAY_PNGS_HAVE_ALPHA` | **renderer-profile** | an overlay page that can never be transparent — no alpha channel and no `tRNS` chunk |
 | `A20_MESH_WEIGHTS_COHERENT` | **renderer-profile / archetype** | **unweighted meshes**, weights not summing to 1, out-of-range bone indices |
 | `A21_MESH_RIM_PINNED` | archetype | ring/ribbon rim not pinned |
 | `A22_MESH_UVS_IN_UNIT_RANGE` | validity-ish | UVs outside 0..1 |
@@ -716,7 +718,7 @@ one.
 
 > 🔼 Both halves of that paragraph are now stale. The walker reaches all eleven groups and the
 > mutants that prove it exist; the suite runs on fixtures it **generates**, so it needs no
-> project's art. Current shape: [CLAUDE.md](../CLAUDE.md), *The selftest and its fixtures*.
+> project's art. Current shape: [CLAUDE.md](https://github.com/firejune/rigc/blob/main/CLAUDE.md), *The selftest and its fixtures*.
 
 ### 2.4 The input model — where the rig actually comes from
 
@@ -751,10 +753,10 @@ The manifest supplies *positions* for those bones (`anchors`), never their *name
 ## Part 3 — what the example ladder actually uses
 
 Corpus: the nine official example projects on branch `4.3`, fetched by
-[`scripts/fetch-examples.sh`](../scripts/fetch-examples.sh) into the gitignored `examples/<name>/`
+[`scripts/fetch-examples.sh`](https://github.com/firejune/rigc/blob/main/scripts/fetch-examples.sh) into the gitignored `examples/<name>/`
 (**12 skeleton JSON files** — some examples ship more than one — **10 `.atlas` files**, 8 `license.txt`).
-Counted by [`bench/count_features.ts`](../bench/count_features.ts); full output in
-[`feature_matrix.json`](feature_matrix.json) and [`feature_matrix.csv`](feature_matrix.csv)
+Counted by [`bench/count_features.ts`](https://github.com/firejune/rigc/blob/main/bench/count_features.ts); full output in
+[`feature_matrix.json`](https://github.com/firejune/rigc/blob/main/docs/feature_matrix.json) and [`feature_matrix.csv`](https://github.com/firejune/rigc/blob/main/docs/feature_matrix.csv)
 (12 rows × 135 columns), both regenerated by `bun run bench:usage`.
 
 > ⚠️ **Verification note.** The timeline columns below were re-derived independently from the raw JSON
@@ -913,7 +915,7 @@ Crossing Part 2 with Part 3. Categories, as requested:
 **(d) JSON-inexpressible** — things the format genuinely cannot hold.
 
 **Nothing below was implemented when this was written. This is a survey.** Three of its items
-have been built since — see the banner at the top of this document and [LADDER.md](LADDER.md) for
+have been built since — see the banner at the top of this document and [LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) for
 which; the requirement text itself is left exactly as surveyed.
 
 ### 4.0 Three blockers that precede rung 1
@@ -977,7 +979,7 @@ Nothing structurally new (attachment timeline, blend, inherit all arrived by run
 #### Rung 6 — `6-arcs`
 
 > ✅ **Measured, 2026-08-23.** The rows below were written as predictions; the
-> transcription in [`bench/transcriptions/6-arcs/`](../bench/transcriptions/6-arcs/)
+> transcription in [`bench/transcriptions/6-arcs/`](https://github.com/firejune/rigc/tree/main/bench/transcriptions/6-arcs/)
 > settled them. It compiles green under `--profile spine` and `bench 6` reports
 > **1.000 on all 44 measures in all six sections**, so the rig spec expresses this
 > skeleton — weighted meshes, `edges` and the 4.3 transform constraints alike. A

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "spine-rigc",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "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": {
-    "rigc": "./cli.ts"
+    "rigc": "./bin/rigc.cjs"
   },
   "engines": {
     "bun": ">=1.2.0"
@@ -31,12 +31,14 @@
     "cli"
   ],
   "files": [
+    "bin/rigc.cjs",
     "cli.ts",
     "src",
     "tools/plate.ts",
     "tools/font5x7.ts",
     "docs/AUTHORING.md",
     "docs/SPEC_COVERAGE.md",
+    "docs/PROMPTING.md",
     "NOTICE.md"
   ],
   "publishConfig": {