Repository navigation
adapters: say where a rig goes inside an engine — the org profile's package table and getting-started's next steps gain @rig-c/pixi · phaser · three #2
Description
Decision
The adapters are published (@rig-c/pixi, @rig-c/phaser, @rig-c/three, each 0.1.1 with provenance), and neither the org profile nor getting-started says so. Add them where a reader decides where the rig goes next:
- Org profile (
rig-c/.github/profile/README.md): one row in the package table for the adapters (repo link, the three install lines, one-sentence purpose: play a rig-c model inside the engine/renderer the game already uses, no Spine runtime), and the alias sentence unchanged. - getting-started (
README.md, the "Three places the rig can go from here" section): a fourth place — "inside a game engine or renderer you already use" — with the shortest working snippet for one host (Pixi), links to the other two, and the same "no Spine runtime" claim the play section makes. The section's count changes from three to four.
Bars
- Every install line and import shown is run: a script in getting-started's
scripts/installs the published package into an empty directory and executes the snippet against the step-10 build (headless browser; exit 0; one non-empty frame), and CI runs it. - Every link resolves (checked by the script, not by eye).
- The voice matches the surrounding text (getting-started is the human-facing guide — read its first screen before writing; try-first, reasons in links). No claims the packages do not make (status 0.x, API may change — say so).
- Nothing else in either file changes.
Activity
firejune commentedon Oct 15, 2026
Reserved implementation in isolated branches codex/adapters-onboarding-2 (getting-started, base 4715d20) and codex/adapters-profile-2 (.github, base 93be3f5e). Guide edits stay within Use what you made, replacing the stale not-built-yet adapter claim and adding the fourth destination. Profile edit is one package-table row; existing alias wording stays unchanged. Verification additions are limited to scripts and CI needed by the posted bars: execute the literal guide snippet against a fresh public step-10 build, install every displayed package command, measure native pixels and animation advancement, and automatically check links in both target documents. No private fixture, local adapter checkout or consumer-specific fallback is allowed. Published adapter 0.1.1 metadata was checked; actual installation/runtime evidence is still pending. The parts wave has not started editing.
firejune commentedon Oct 15, 2026
The first clean run with current published packages (
@rig-c/parts@1.25.0,rig-c@2.58.1,@rig-c/pose@0.20.4,@rig-c/play@1.10.1) reached the existing step 8 and failed withCONFIG_PART_ATTACHEDfor handwear/legwear andCONFIG_NAME_RESOLVESfor upperarm/forearm/thigh/shin. Step 7 drops the proposal'slimbsfield, which defines those cuts and generated regions.Scope amendment agreed with HQ: append
limbsto step 7'stakecommand in this issue. Acceptance includes the current-version failure, green after repair, and a real reverted-field-copy negative control under the same installed toolchain. The CI will execute the documented workflow through step 10 on current published packages using the documented no-Python keypoint route. Old-version pins will not replace this check.firejune commentedon Oct 15, 2026
The same current-package run now proves step 8 green and the reverted
limbscopy red with all 11 named refusals. Step 9 then exposed a second existing guide failure:POSE_NOT_CLEANED: wave.pose.json has no "cleaned" record; currentrig-pose retargetrequires the output ofrig-pose clean.HQ confirmed the scope as all guide defects that prevent the displayed steps 1–10 from running with current published versions. Repair step 9 by adding the published
cleancommand and retargeting its output. Each repair retains actual failure, repaired-positive, and reverted-negative evidence. Version pins, validation bypasses, and package behavior changes are outside this repair approach; package changes require a separate coordination decision.docs: list published engine adapter installs
firejune commentedon Oct 15, 2026
Profile half landed: rig-c/.github#1, squash
21163fec6f265e2cff39a35ee423dbff3d266851. Re-read the merged commit and confirmed the required Naru GitHub App co-author trailer. Three fresh adapter installs and all 16 profile links passed; independent source review accepted the one-row change. Its worktree/branch are cleaned up.The guide's default remote-profile input now contains the row. Guide native-browser acceptance and its final CI remain in progress; this does not close #2.
firejune commentedon Oct 15, 2026
Completed and landed:
21163fec6f265e2cff39a35ee423dbff3d266851.c37c1244b414c9e455c9d45814c30ab44c7b2e56.Final PR-head CI https://github.com/rig-c/getting-started/actions/runs/38708317224 passed against the merged public profile: all three fresh installs, current tutorial, both real reverted-guide controls, owned step-10 page, native moving/empty/frozen scenes, and 74 links. The native positive measured 51,154 → 51,742 painted pixels and 30,588 changed channels with advancing pose. Each merged commit was re-read and contains the required Naru GitHub App co-author trailer. Both owned worktrees and branches are cleaned up. No remaining gate for this issue.