What the report build establishes
The stored October 3, 2026 run at commit 8f3d362 successfully installed dependencies and built the report app under hybrid_rollout/report_site/app. Installation took 27 seconds; the build took 10 seconds. These results concern the frontend, not robot control, simulator deployment, policy inference or model access. No new execution was performed for this correction.
The pinned README says the rebuild produces a self-contained HTML file without private experiment storage. It instructs readers to keep the report data, licenses and media alongside that file. It also documents a separate preview path. Our recorded build does not verify preview interactions or deployment.
Start with the official report and the repository's selected case metadata to decide whether the comparison answers your research question. The report link is supplied by the README; we did not test that preview.
What the authors report
GPT-as-Policy provides evaluation code and a bilingual report comparing direct GPT control with a hybrid policy that reviews π0.5 actions. The authors describe ten RoboDojo tasks with five aligned cases per task. They report 48% success for the hybrid policy and 26% for GPT 6 Astra Direct. Both success rates use all 50 selected cases.
These are author-reported results, not measurements from our sandbox. They describe the selected evaluation and do not establish performance on another robot or across an entire benchmark catalogue. The README identifies official-model comparisons as reweighted public references rather than same-seed reruns.
The frontend command executed zero tests
The test command returned exit code 0 after 8 seconds. Its parser summary records 0 passed, 0 failed and 0 total tests, and the raw TAP footer independently reports zero tests. That result provides no behavioral test coverage.
The app package script invokes node --test tests/*.test.mjs. The harness scan recorded no tests directory. That scan does not establish that the whole repository lacks tests: the README documents separate Python unittest and pytest commands, which our run did not execute.
The build log also reports protected-runtime verification. An integrity check and a behavioral test answer different questions. Neither that verification nor the frontend build validates the controller.
Dependency and advisory records disagree
The stored dependency summary records 260 packages and 147 MB. The raw install tail separately says 243 packages were added. These are different recorded counts; the supplied evidence does not explain their relationship.
The stored npm audit summary records zero advisories, while the install tail reports 3 high-severity vulnerabilities. Neither record should be silently substituted for the other. Audit coverage is unknown because scannedPackages is absent, and these outputs do not establish security clearance.
Before relying on the app in a release process, reconcile the dependency and advisory outputs in your own environment and establish behavioral tests. The dated command results cannot settle those questions for a current checkout.
What a new rollout requires
The README excludes simulator assets, model checkpoints, raw model sessions and original operations logs. RoboDojo uses Isaac Sim 5.1, matching RoboDojo source and assets, and its π0.5 OpenPI/JAX checkpoint. RoboLab has a separate environment.
A new evaluation also requires Codex CLI, authorized model access and explicit local configuration. The model is fixed to gpt-6-astra with xhigh reasoning. The source release notes say deployment-specific paths and endpoints were replaced with generic examples. Those examples require configuration before use.
For a frontend rebuild, follow the README's rebuild instructions. Do not use build.py merely to rebuild the frontend: the README says that evidence-extraction utility requires original, non-public trajectory archives. Before planning a robot evaluation, confirm that you can obtain the required upstream assets and authorized services. Our run supplies no latency, model-cost or robot-performance estimate.
Where OpenPI and Isaac Lab fit
OpenPI provides model checkpoints and examples for inference and fine-tuning. Choose OpenPI when your immediate task is running or adapting the underlying policies. It also complements the documented GPT-as-Policy rollout environment, which requires an OpenPI/JAX checkpoint. Its README warns that supplied checkpoints may not work on a particular robot.
Isaac Lab supports robot-learning workflows including reinforcement learning, imitation learning and post-training. Choose Isaac Lab when you need a framework for those workflows. Its supplied documentation describes multiple backends and version-specific Isaac Sim compatibility. Check that compatibility separately from GPT-as-Policy's Isaac Sim 5.1 requirement. Neither tool supplies this report's omitted experiment material.
How to read the ratings
The assessed dimensions use a five-point editorial scale: 1 means substantial documented obstacles, 2 means limited supporting evidence, 3 means usable within material constraints, 4 means strong evidence with smaller gaps, and 5 means unusually complete evidence for the stated dimension. These judgments concern the supplied snapshot, not measured adoption or production reliability.
Setup considers the successful report build alongside external rollout prerequisites. Documentation considers the supplied preview, rebuild, evaluation, provenance and boundary instructions. Maturity considers automation and reproducibility, including the zero-test frontend result and the harness's record of zero CI workflows.
Community is unassessed. The supplied primary extracts do not establish support activity, responsiveness or adoption, so this dimension has no numerical rating.

