Skip to content

docs(onboarding): align the timing claim with what was measured and pin a reproducible recipe - #98

Merged
firejune merged 1 commit into
mainfrom
naru/87-onboarding-timing-recipe
Oct 27, 2026
Merged

firejune merged 1 commit into
mainfrom
naru/87-onboarding-timing-recipe

Conversation

@firejune

Copy link
Copy Markdown
Contributor

Closes #87. Two files: content/index.md, content/docs/getting-started.md.

The homepage said "about a minute on an Apple M4"; the guide measured 536–571 s on a loaded M4 for a different scope. The homepage now names the route and quotes the historical Apple figure with its scope and date; the guide pins a recipe (Parts 1.54.0, Core 2.65.1, Pose 0.38.0, Play 1.12.0, helper and exam commits, archive SHA-256 in the command) reproduced 2026-10-27 from an empty directory on a Linux x86_64 / WSL2 runner: 12/12 step groups exit 0, 27 quoted fragments identical, both pages exercised in a real browser. Rolling-latest stays a separate link (rig-c/getting-started#1 / PR #24, not duplicated).

Check Result
recipe, empty dir, pool 12/12 groups, 27/27 fragments, browser functional
targeted / full 21 pass / 68 pass (649 assertions)
build / verify 14 pages + 8 redirects / 0
1440 / 390 px no overflow (a 579 px raw-URL overflow found and fixed)

Rejected: an unmeasured Apple estimate; hidden overrides; upstream edits; #91's example.

@codex review

🤖 Generated with Claude Code

…in a reproducible recipe

The homepage advertised "about a minute of commands on an Apple M4" while
Getting Started recorded 536–571 s for steps 1–10 (9b/9c included) on a
loaded M4 — two different paths presented as one. The guide also installed
unversioned packages and cloned helpers from a moving branch.

The homepage now says what the route is (CPU-only, no Python, from prepared
example layers) and quotes the historical Apple figure as observed on
2026-10-21 with its scope (empty cache, downloads, the 41 MB example, load
20–95). Getting Started gains a pinned recipe — Parts 1.54.0, Core 2.65.1,
Pose 0.38.0, Play 1.12.0, helper and exam commits named, archive SHA-256
checked in the command — reproduced on 2026-10-27 from an empty directory on
the shared Linux x86_64 / WSL2 runner (Bun 1.4.4, npm 11.19.1, Node 24.22.1):
12 of 12 step groups exit 0, 27 quoted output fragments identical, both
documented pages exercised in a real browser (pose advances, pause/resume
and breeze operate, 28 rendered children, no errors). The rolling-latest
route stays linked separately; the historical step 10 (HTTP only) and the
new functional browser check are told apart; historical captions no longer
attribute old capture versions to today's pinned commands. No Apple
re-timing was claimed.

Measured for the site: targeted 21 pass; full 68 pass / 649 assertions;
build 14 pages + 8 redirects; verify 0; 1440 and 390 px without overflow
(a 579 px raw-URL overflow at 390 px was found and fixed by labelling the
URLs). Coordinated with rig-c/getting-started#1: its rolling-latest CI (PR
#24) is linked, not duplicated.

Rejected: an unmeasured Apple estimate; hidden overrides; an old-runtime
matrix; any upstream repository edit; #91's example.

Closes #87

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-27T04:59:07.494120Z f0c0eed 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. 🚀

Reviewed commit: f0c0eed407

ℹ️ 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 e1b39ca into main Oct 27, 2026
3 checks passed
@firejune
firejune deleted the naru/87-onboarding-timing-recipe branch October 27, 2026 05:18
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(onboarding): align timing claims and provide a reproducible walkthrough

1 participant