Skip to content

bring bench 001 on dev up to what production runs - #2808

Merged
Flotapponnier merged 1 commit into
devfrom
sync/bench-001-to-dev
Oct 4, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
sync/bench-001-to-dev

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Prerequisite for the materialize worker rebuild: it clones dev at BUILD time, so until this lands a rebuild picks up a spec that still says OKX and Birdeye are measured on Base and Solana only.

Why this is a file port and not a fast-forward

Eight PRs of bench 001 work went straight to main this week, and the fast-forward back to dev that AGENTS.md prescribes after a hotfix was never done. The branches have since diverged in both directions, so a fast-forward is no longer available: dev carries its own merges of the same work under different SHAs (#2791, #2797, #2792) plus commits main lacks (#2803, #2793, #2796).

Rather than reconcile twenty commits, this ports one bench by file.

Every line it removes from dev is one main deliberately replaced

Checked before porting, not assumed:

removed from dev why
Timestamp string dev still types the OKX millis field as a string. That is the #2795 bug: the WebSocket sends a JSON number, and 136 of 136 frames were rejected in production because of it.
plain websocket.Dialer replaced by the pinned Chrome ClientHello in #2802. Without it Cloudflare 403s every Birdeye dial from Railway.
the 403 retry loop #2799 gave it a circuit breaker, after it hammered a third party from three regions.
TestOKXDoesNotCoverBNB re-derived as a coupling in #2805.

Nothing on dev is lost: no file in the port exists only there, and main is strictly ahead on all six.

Verified on dev's base, not main's

go build ./... and go test ./cmd/script/ -run 'Birdeye|OKX|Reference|Chain' pass; pnpm validate reports 235 specs valid.

Still open

The wider dev/main divergence is untouched and needs a decision: reconcile it, or accept that main leads and port by file each time.

🤖 Generated with Claude Code

Eight PRs of bench 001 work went straight to main this week on "mets live
now", and the fast-forward back to dev that AGENTS.md prescribes after a
hotfix was never done. The two branches have since diverged, so a
fast-forward is no longer possible: dev carries its own merges of the same
work under different SHAs plus commits main does not have.

This ports the one bench, by file, rather than reconciling twenty commits.
Every line it removes from dev is a line main deliberately replaced:

  Timestamp string           dev still types the OKX millis field as a
                             string, which is the bug #2795 fixed: the
                             WebSocket sends a JSON number and 136 of 136
                             frames were rejected
  plain websocket.Dialer     replaced by the pinned Chrome ClientHello in
                             #2802, without which Cloudflare 403s every
                             dial from Railway
  the 403 retry loop         #2799 gave it a circuit breaker after it
                             hammered a third party from three regions
  TestOKXDoesNotCoverBNB     re-derived as a coupling in #2805

The spec comes with it, which is the operational reason this cannot wait:
the materialize worker clones dev at BUILD time, so until this lands a
worker rebuild would pick up a spec that still says OKX and Birdeye are
measured on Base and Solana only.

Verified on dev's base, not main's: go build ./... and
go test ./cmd/script/ -run 'Birdeye|OKX|Reference|Chain' pass, pnpm validate
reports 235 specs valid.

The wider divergence is untouched and still needs a decision.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@Flotapponnier
Flotapponnier merged commit abf7716 into dev Oct 4, 2026
2 checks passed
Flotapponnier added a commit that referenced this pull request Oct 4, 2026
Same port as #2808, for the same reason: the materialize worker clones dev
at BUILD time, so the two new methodology bullets only reach the page from
here.

Carries the harness change with the spec, so dev does not end up describing
an eligibility rule its own race.go does not apply.

Verified on dev's base: go build ./..., the full go test ./cmd/script/
suite, and pnpm validate (235 specs valid).

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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