SHUKE-LABS/mat-site
Replace terminal logo and favicon with new four-agent My AI Team artwork
no human review
Evidence · public GitHub records · verified 2026-09-14
Orbi builds Orbi. The record is GitHub
Orbi is the delivery line that ships Orbi. Three public deliveries from orbi-build/orbi are below. Open an Issue to read the runner's comments; open a PR to see a merge with no human review. Each sample tells you what to look at. Click them.
PUBLIC RECORDS
Three deliveries you can open
Each row is a real object in the public orbi-build/orbi repository. Further tagged releases sit on the releases ledger.
-
v0.5.5
Issue #852, merged PR #854, Release v0.5.5
A PyPI trusted-publishing failure entered the public Orbi repository, the matching pull request merged, and the fix shipped in tagged release v0.5.5.
What to look for on the timeline. On the Issue, the runner posted four comments: started, plan ready, tests passed, merged. The merged comment includes a
review_roundsfield. PR #854 has no human review and still merged; the review ran in the runner's independent session, and the result is written on the Issue. The runner posts those comments with the maintainer's token, so the actor shows as xqliu. -
v0.5.4
Issue #842, merged PR #845, Release v0.5.4
An external-PR takeover that never claimed a ticket without a milestone entered the public Orbi repository, the matching pull request merged, and the fix shipped in tagged release v0.5.4.
What to look for on the timeline. On the Issue, the runner posted four comments: started, plan ready, tests passed, merged. The merged comment includes a
review_roundsfield. PR #845 has no human review and still merged; the review ran in the runner's independent session, and the result is written on the Issue. The runner posts those comments with the maintainer's token, so the actor shows as xqliu. -
v0.5.3
Issue #825, merged PR #830, Release v0.5.3
A stuck run after a 502 entered the public Orbi repository, the matching pull request merged, and the fix shipped in tagged release v0.5.3.
What to look for on the timeline. On the Issue, the runner posted four comments: started, plan ready, tests passed, merged. The merged comment includes a
review_roundsfield. PR #830 has no human review and still merged; the review ran in the runner's independent session, and the result is written on the Issue. The runner posts those comments with the maintainer's token, so the actor shows as xqliu.
THE LOOP IS THE PRODUCT
Inspect the record, then run the line
If the public timelines are the evidence you wanted, the next step is the same GitHub-native loop on your repository — self-hosted, or Cloud.