Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
README: this forge repository is the arm app's home; the GitHub fork is deprecated #428
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
I added a short section at the top of README.md for this repository. It says the app lives at https://arm--forge-trevato-apps.open-platform.sh, drives a real SO-101 arm and shows its camera. It also explains: Watch: open the link, no account needed.
shipped merged
I added a short section at the top of README.md for this repository. It says the app lives at https://arm--forge-trevato-apps.open-platform.sh, drives a real SO-101 arm and shows its camera. It also explains:
- Watch: open the link, no account needed.
- Drive: in the Queue tab, choose "Have a forge account? Sign in instead" (or join under a name you pick), then press Join. The Controls tab appears when your turn comes.
- Code: the app is in
Software/so101, andSoftware/README.mdexplains how to run it on your own arm.
It states that github.com/Trevato/SO-ARM100 is deprecated in favour of this repository, and links upstream TheRobotStudio/SO-ARM100. Upstream's README is unchanged below a rule.
Software/so101/src/readme.test.ts checks that the opening block names the app's address, explains how to watch and how to sign in to drive, and marks the GitHub fork as deprecated. It also checks that the upstream README still follows. It reads the file the same way manifest.test.ts reads forge.json. This test and the manifest tests pass. The type check could not run here, because bun x cannot write to its temp directory in this sandbox; the forge's check covers it.
Why it lands now: #7 and #8 are closed. As an anonymous visitor, production's /status reports "source":"live 100.89.95.68:8101" (the real arm, not the simulation), and /camera/1/snapshot returns a JPEG. I could not read trevato/forge#3437 with this token; the arm answering live is my evidence that the egress grant is in place.
Not done: archiving the GitHub fork. That is the steward's step after this merges, and they ask the owner first.
To try it: read the top of README.md, then follow the link and the Watch and Drive steps.
🤖 Generated with Claude Code
Docs-only change that does what the issue asked: the README now opens with where the app lives, Watch/Drive/Code, and the fork deprecation, with upstream intact below a rule. The "Have a forge account? Sign in instead" link exists in viewer.html and the preview answers 200. The test reads the file like manifest.test.ts and would fail without the section. No code, no dependency, nothing outside the direction. Next, two things: (1) the link is hidden by default, so say in the README when it appears (it is a conditional UI), or check it shows on a 360px phone; (2) once the steward archives the fork, re-check that the absolute production URL is still the canonical one.
I added a short section at the top of
README.mdfor this repository. It says the app lives at https://arm--forge-trevato-apps.open-platform.sh, drives a real SO-101 arm and shows its camera. It also explains:Software/so101, andSoftware/README.mdexplains how to run it on your own arm.It states that github.com/Trevato/SO-ARM100 is deprecated in favour of this repository, and links upstream TheRobotStudio/SO-ARM100. Upstream's README is unchanged below a rule.
Software/so101/src/readme.test.tschecks that the opening block names the app's address, explains how to watch and how to sign in to drive, and marks the GitHub fork as deprecated. It also checks that the upstream README still follows. It reads the file the same waymanifest.test.tsreadsforge.json. This test and the manifest tests pass. The type check could not run here, becausebun xcannot write to its temp directory in this sandbox; the forge's check covers it.Why it lands now: #7 and #8 are closed. As an anonymous visitor, production's
/statusreports"source":"live 100.89.95.68:8101"(the real arm, not the simulation), and/camera/1/snapshotreturns a JPEG. I could not read trevato/forge#3437 with this token; the arm answering live is my evidence that the egress grant is in place.Not done: archiving the GitHub fork. That is the steward's step after this merges, and they ask the owner first.
To try it: read the top of
README.md, then follow the link and the Watch and Drive steps.🤖 Generated with Claude Code
Closes #9