Regenerated Workshop's four registry views and digests with the published assembler 0.6.6 from openrig-world main 37592f8b (#78, the 0.7.9 Pi skill snapshot). Each view changes only its identity and provenance fields; review status, configuration ids, aliases and the assembler are unchanged. Four-configuration proof and the registry checks pass. One focused read MERGE-READY at d814adef.
Regenerated Workshop's four registry views and digests with the published assembler 0.6.6 from openrig-world main b7a71ddf (#76, the 0.7.8 Pi skill snapshot). Each view changes only its identity and provenance fields; review status, configuration ids, aliases and the assembler are unchanged. Four-configuration proof and the registry checks pass. One focused read MERGE-READY at 76008977.
Workshop's registry entry pins openrig-world `582084a7`, which carries OpenRig 0.7.5's public Pi skill snapshots (openrig-core 0.1.22). The four package digests were regenerated with the 0.6.6 assembler, and the behaviour views change only identity and provenance fields; review status, IDs and file names are unchanged.
Workshop now points at openrig-world 06827206, whose Pi seats carry OpenRig 0.7.4's skills (plugin 0.1.21). Its four configurations are regenerated at assembler 0.6.6: four new package digests, and in each behaviour view only the identity and provenance fields change. The review date, note, status, IDs and view names are unchanged. 5 files.
Workshop now points at openrig-world 44bfc87c, whose Pi seats carry OpenRig 0.7.3's skills (plugin 0.1.20). Its four configurations are regenerated at assembler 0.6.6: four new package digests, and in each behaviour view only the identity and provenance fields change. The review date, note, status, IDs and view names are unchanged. 5 files, +42 -42.
Workshop's registry entry now pins openrig-world d1d46383, which carries Workshop's Pi skill snapshots regenerated at OpenRig 0.7.2, so a team installed from the registry gets Pi seats that know 0.7.1's and 0.7.2's commands.
The four configurations' package digests and behaviour views are regenerated against that commit with the entry's recorded assembler, OpenRig 0.6.6: all four digests change, and each view changes only its identity and provenance fields. The review date, note, status, IDs, aliases, assembler version and view file names are unchanged. 5 files.
Repins the Workshop entry to openrig-world d139a0c8 (after #65 plugin selection and #66 Pi snapshots), regenerated with the published @openrig/cli 0.6.6 assembler: workshop.yaml and the four views/workshop/*.0.6.6.json, byte-equal to the regeneration evidence (workshop.yaml e6074e20, views cfa068cc, 64effe81, bff70da9, b7099019). The Claude Code and Codex views now write 21, 19 and 17 files instead of 85, 83 and 81, because seats no longer carry copied OpenRig skills; the openrig-core plugin adds its four hooks. The review date, note and status are unchanged. The mirror in openrig-world (#67) pins the same commit.
A person submitting a rig from a fork could wait without knowing why the checks hadn't started, and didn't know how to resubmit after the check found something. The submission guide now says both: on a first pull request here, GitHub waits for a maintainer to approve the checks before they run; and to fix a finding, push the fix to your own repository, set ref in the submission file to that new full commit SHA, and push it to the pull request, where the check runs again on the new commit (a maintainer may need to approve it again).
The check fetches whatever ref names on each run, and a new run starts with a push to the pull request, which updating ref provides. Nothing else in the guide changes.
The bundle check fetches the submitted ref anonymously, so a local-only or private repository can't be checked; the submission guide now says so before the three fields. Both READMEs now name the validator the check runs, the latest published OpenRig (@openrig/cli@latest, as since #16), and the guide says the job prints the version it used.
Repin the existing four-seat Workshop listing to openrig-world fa38c9b55e013e600a3472d2f7561df32df79ce8, which adds the clarified guidance for a person's request for a pull request arriving through their agent and operator. The four package digests and behaviour views are regenerated with the existing generator; only identity fields change in the views.
Public status is regenerated from the unchanged run records. The 18 October Linux team run stays bound to its original bundle digest and doesn't label the new bytes, so all four configurations are untested at this pin. The dated Linux and macOS harness checks are unchanged, and there's no evidence reuse.
The registry check now installs the latest published @openrig/cli (still with --ignore-scripts) and logs its exact rig --version, instead of a fixed 0.6.6. It also runs weekly (Monday 06:17 UTC) and on demand through workflow_dispatch over the current listings, so a release that breaks a listed team shows up without waiting for a registry change. Permissions stay contents: read with no secrets, actions stay pinned by SHA, and the deploy workflow still runs only after a successful push. A published release that breaks rig bundle check will now also fail registry pull requests until it's fixed.
Workshop's recommended default configuration is now recorded as tested on linux-x64 with OpenRig 0.6.11 (2026-10-18), bound to its listed package digest, with Linux PASS harness checks for Claude Code (2.1.299, updated to 2.1.302) and Codex (0.163.0). The run used an existing Ubuntu machine with signed-in harnesses, so it doesn't establish a fresh-machine path. The other three configurations, Pi, and macOS on 0.6.11 stay untested, and the 2026-10-06 macOS entries are unchanged.
The Workshop listing now pins openrig-world rigs/workshop at 2a5d93c8, so installs get the corrected QA sandbox guidance and the startup context's AGENTS.md clause. The four configurations' package digests and behaviour views are regenerated at the new commit; every non-identity view field is unchanged. The native macOS results stay dated 2026-10-06 and labelled historical; Linux, Pi and new-pin coverage with OpenRig 0.6.10 remain unverified.
Add workshop-review-pair to status/status.json: one configuration, no platforms run, no community reports, so the site lists it as not yet run as a team by OpenRig.
List the optional five-seat Workshop variant with a review pair (openrig-world rigs/workshop-review-pair at ec063e3d, package digest 60e9e59b, behaviour view for 0.6.7). The four-seat Workshop stays the recommended default.
A merged listing reached openrig.dev/rigs only when openrig.dev's own
scheduled rebuild ran, and GitHub has started those hours late. This asks
Vercel to rebuild the site once the Registry check passes on a push to main.
The site's build still fetches and validates the registry itself; this
workflow reads nothing here and needs only the deploy link as a secret.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* Pin workshop to openrig-world 52ca6128
Move the workshop listing and its four generated views to
openrig-world 52ca6128486219676dbe749f360e1d3539e6ab20, the merge of
mvschwarz/openrig-world#57. That change tells the workshop's agent to
open terminals the person can see: the README, the lead's guidance and
the using-the-tui-together bundle skill.
Only identity fields change: the source commit and canonical URLs, the
four package digests, and each view's stated provenance. Configuration
choices, behavior sections and the other declarations are unchanged.
* Date the workshop review 2026-10-07
The pinned commit 52ca6128 was made on 2026-10-07, so the listing page
should read "Reviewed for listing on 2026-10-07", not the previous
pin's date.
---------
Co-authored-by: OpenRig contributors <[email protected]>
* Submit share-journey-test, a labelled test listing of workshop at 52ca6128
A test submission that exercises the documented route end to end: submit a
bundle link, review and list it on openrig.dev/rigs, then install it from the
listing on a test machine. It points at workshop's current commit, which
changes its README, lead guidance and a bundle skill since the listed pin.
List it as a labelled test listing and remove it after the install check.
* List the share journey test with verified Workshop packages
---------
Co-authored-by: v-openrig-build <[email protected]>
* fix: retain withdrawn entries in the listing page index
* test: create an empty record directory for discovery fixtures
* test: list the checked Workshop package for scheduled discovery
* test: preserve the reviewed view across later Workshop repins
* Validate submitted bundle source in registry CI
* Remove the validated CI proof submission
* docs: state bundle check limits and validator upkeep
---------
Co-authored-by: OpenRig contributors <[email protected]>
* Move reviewed registry and status tooling from project world
* Exercise submission validation during catalog migration
* Remove the migration submission after its pull request checks pass
---------
Co-authored-by: OpenRig contributors <[email protected]>
Mike Schwarz