Skip to content

docs: use the scoped @rig-c/* names as the canonical package identities; keep convenience and legacy names as labelled compatibility entries - #110

Merged
firejune merged 1 commit into
mainfrom
naru/109-scoped-names
Oct 28, 2026
Merged

firejune merged 1 commit into
mainfrom
naru/109-scoped-names

Conversation

@firejune

Copy link
Copy Markdown
Contributor

Refs #109 (site part). The scoped @rig-c/* names become the canonical package identities across rig-c.org, its Markdown mirrors, llms.txt / llms-full.txt and structured data; rig-c stays the brand and Core's convenience install name; executables rigc / rig-parts / rig-pose unchanged; spine-* names move to a labelled compatibility mapping; the adapters row names the real host packages.

Historical captures, pinned commands, imports, manifests, lockfiles and demo/asset bytes are untouched. rig-pose (unscoped) is not on npm, so it is not recommended.

Check (pool) Result
site tests 73 pass
build / verify / links pass
real scoped install + CLI / skill / build / retarget pass
browser, 8 desktop/mobile viewports, exact artifact pass

Related-repo follow-ups: rig-c/core#1625, rig-c/parts#797, rig-c/play#222, rig-c/pose#457, rig-c/getting-started#30.

🤖 Generated with Claude Code

…es; keep convenience and legacy names as labelled compatibility entries

Per the owner's naming policy (#109): `@rig-c/core`, `@rig-c/parts`,
`@rig-c/pose`, `@rig-c/play`, `@rig-c/review` and the host adapters
(`@rig-c/pixi`, `@rig-c/phaser`, `@rig-c/three`) are the canonical package
names across the site, its Markdown mirrors, llms.txt / llms-full.txt and
the package structured data. `rig-c` stays the toolchain brand and Core's
convenience install name; the executables stay `rigc`, `rig-parts` and
`rig-pose`; the `spine-*` names move to a labelled legacy/compatibility
mapping. The adapters row names the three real host packages instead of the
private workspace label.

Not changed: historical captures, pinned reproduction commands, source
import paths, manifests and lockfiles, and every demo / asset byte. The
unscoped `rig-pose` package is not on npm (404 on 2026-10-28) — the
`rig-pose` executable ships inside `@rig-c/pose` — so the site does not
recommend the unscoped name.

Verified on the pool: 73 site tests, build, verify, links; a real scoped
install exercising the CLI, skill, build and retarget commands; 8
desktop/mobile viewport checks on the exact artifact.

Refs #109

Co-Authored-By: Naru <342599188+fj-naru[bot]@users.noreply.github.com>
Co-Authored-By: Roa <342598975+fj-roa[bot]@users.noreply.github.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-28T13:16:56.547969Z 4a5a540 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@firejune
firejune merged commit 87674dd into main Oct 28, 2026
3 checks passed
@firejune
firejune deleted the naru/109-scoped-names branch October 28, 2026 14:19
firejune added a commit that referenced this pull request Oct 28, 2026
…table (#111)

#110 replaced the single `@rig-c/adapters` label with the three real
packages, written as one comma-joined link — so the package cell went back
to the one-line form #75 had removed from the version cell beside it. Each
package is now its own link to the adapters page, separated by `<br>`, as
the version and install cells already are.

A build test now holds the HTML package cell to the three-line form; with
the content reverted it fails, alongside the Markdown-row test that keys
on the row's prefix. Measured: `bun run test` 73 pass; `build:ci` then
`verify` PASS.

Co-authored-by: Roa <342598975+fj-roa[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant