Skip to content

docs: reconcile released depth turns and unify current package versions - #93

Merged
firejune merged 1 commit into
mainfrom
naru/86-docs-reconcile-releases
Oct 27, 2026
Merged

firejune merged 1 commit into
mainfrom
naru/86-docs-reconcile-releases

Conversation

@firejune

Copy link
Copy Markdown
Contributor

Closes #86.

What was wrong. Examples called the head-turn producer unreleased; the Parts and Pose limits described older capabilities; documentation badges carried authored versions (Parts 1.41.0, Pose 0.35.0, Review 0.7.1) beside a homepage table that read npm.

What changes.

  • Examples distinguishes the standalone, precompiled head-turn demo from the producer @rig-c/parts 1.68.0 ships; the demo is not claimed to be rebuilt on it, and its mechanics are described from its own bundle.
  • Parts/Pose limits are restated at the published versions (1.68.0, 1.2.1): the per-pixel depth-sheet path beside the legacy ordering-depth turn; derived depth, depth-based draw order, foreshortening and foot handling as opt-in paths with their limits. Open gait cards (depth: in a gait, an arm's forward/back follows the opposite leg's step phase, not the arm's own foreshortening pose#444–#446) stay open in prose.
  • packageVersion front matter is removed: it had no defined historical baseline and fed current-looking badges, JSON-LD and the LLM mirrors. One npm map resolved at build feeds every current-version surface; a consistency test holds badges, homepage table, structured data, Markdown and LLM outputs to it. Historical recording, fixture and reproduction pins are untouched.
  • Also corrected: Pixi 0.1.2, Phaser/Three 0.1.1; Bun >= 1.4.0 as the packages declare.

Measurement.

Check Result
targeted 26 pass
bun run test 39 pass / 0 fail, 423 assertions
bun run build (isolated out) 12 pages, 8 redirects, 8 packages resolved
bun run verify 0 (HTML/Markdown/redirect/copy/digest + internal link targets)
consistency mutant: Parts badge → 999.0.0 in a copied fixture 1 fail by name (expected 200.1.3, received 999.0.0); restored 1 pass

The verifier checks root-relative internal HTML link targets; it does not check external availability, fragment ids or general Markdown links. No demo bundle, asset or runtime behaviour changes.

Rejected: relabelling the old literals as "documented at"; blanket latest replacement; rebuilding the demo on the producer; any demo/producer equivalence claim.

@codex review

🤖 Generated with Claude Code

The site still called the head-turn producer unreleased, described older
Parts/Pose limits, and displayed authored package versions beside a newer
homepage table.

Examples now distinguishes the standalone, precompiled head-turn demo from
the producer @rig-c/parts 1.68.0 ships (per-layer depth input, 2.5D turn with
grid surfaces and yaw/pitch dials); the demo is not claimed to be rebuilt on
it. Parts and Pose limits are stated at their published versions (1.68.0,
1.2.1): the per-pixel depth-sheet path beside the legacy ordering-depth turn,
derived depth and depth-based draw order as opt-in paths with their limits;
the open gait cards stay named as open.

`packageVersion` front matter is removed rather than relabelled: it had no
defined historical baseline and fed current-looking badges, structured data
and the LLM mirrors. Every current-version surface now reads the one npm map
resolved for that build; adapters keep individual badges and records.
Recording, fixture and reproduction versions stay pinned.

Measured: targeted checks 26 pass; `bun run test` 39 pass / 0 fail (423
assertions); `bun run build` 12 pages, 8 redirects, 8 packages resolved;
`bun run verify` 0. A rendered fixture with only the Parts badge changed to
999.0.0 fails the new consistency test by name (expected 200.1.3, received
999.0.0); restored, 1 pass. Also corrected while there: Pixi is 0.1.2,
Phaser/Three 0.1.1; Parts/Pose/Core declare Bun >= 1.4.0, not >= 1.2.

Rejected: calling the old literals "documented at"; a blanket latest
replacement; rebuilding the demo on the producer; any producer/demo
equivalence claim.

Closes #86

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 27, 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-27T01:58:27.110625Z 6969c06 Manual request
ℹ️ 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.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 6969c06852

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@firejune
firejune merged commit 39e2678 into main Oct 27, 2026
3 checks passed
@firejune
firejune deleted the naru/86-docs-reconcile-releases branch October 27, 2026 02:32
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.

docs: reconcile released depth/turn features, capability limits and package version badges

1 participant