Skip to content

chore(harnesses): sync public harnesses with deployed code - #417

Merged
Flotapponnier merged 3 commits into
devfrom
feat/per-chain-bench-pages
Jun 11, 2026
Merged

chore(harnesses): sync public harnesses with deployed code#417
Flotapponnier merged 3 commits into
devfrom
feat/per-chain-bench-pages

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

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:

  • loghub refactor of 2026-06-04 (log_buffer.go -> loghub.go everywhere)
  • bench-029 v3 (Pulse V2 WS rotation), solana-tx-landing prober/senders, wallet-labels anchors, network-coverage fetchers, l1-finality cardano/stellar/ton fixes

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

  • Secret scan on the full staged diff: only public blockchain addresses, all auth goes through os.Getenv
  • All 17 harnesses go build clean locally

Follow-up

CI guard in mobula-api to fail when miniapps/ diverges from the public tree, so this drift doesn't rebuild silently.

@Flotapponnier
Flotapponnier merged commit cd24ac7 into dev Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant