chore(harnesses): sync public harnesses with deployed code - #417
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Public harness copies had drifted from the deployed miniapps (mobula-api dev, what Railway actually builds). Synced cmd/ + go.mod/go.sum/Dockerfile/railway.toml for 17 of 18 harnesses from miniapps:
hyperliquid-frontends deliberately NOT synced: the OCB copy is newer (ported today from the HL node server, the deployed truth for bench 030); the miniapp copy is the stale one there.
Safety
Follow-up
CI guard in mobula-api to fail when miniapps/ diverges from the public tree, so this drift doesn't rebuild silently.